Annoying problem with snapshots and replication

tom__w

Explorer
Joined
Mar 26, 2013
Messages
87
I have a primary 11.U6 box creating snapshots every hour. I then replicate to my backup box. The problem I have is that the backup box keeps reporting that a file or directory does not exist. I am sure it's something dumb but I don't know what I did to create this issue.

Here is the storage config from my main box:
Storage main.JPG


Here is the snapshot setup on the main box (I have another one for Fast_Z2):
Snaphot config.JPG


I am getting the snapshots that I want on the primary server (not sure why I have 0 used):
snaps.JPG


And replicating to backup:
replicate.JPG



This is the storage config on my backup:
backup storage.JPG


But on my backup box, I am regularly getting this error on replication (I assume it's replication causing this):
1550190509082.png


What meathead configuration did I screw up?

Much appreciated!
 

DrKK

FreeNAS Generalissimo
Joined
Oct 15, 2013
Messages
3,630
OK, it's kind of hard to tell what's going on, but given that statvfs is failing, I suspect you have quotas in place on the backup system, or something, which is not giving enough room to do the replication. Release all your quotas, and see if that solves the problem. Then take it from there.
 

Redcoat

MVP
Joined
Feb 18, 2014
Messages
2,925
I think you're into this same issue that's been around for some time see https://redmine.ixsystems.com/issues/15355 for starters. Search Redmine on "statvfs" for others.

I have a cron job built on the example in that report running on my backup server at a time after I expect the transfer of snapshots from the primary to be complete in order to cut off the messages that otherwise clog the log...
 

tom__w

Explorer
Joined
Mar 26, 2013
Messages
87
Oddly enough, I JUST started seeing the same error but this time it was reporting the jails were not found.
 

DrKK

FreeNAS Generalissimo
Joined
Oct 15, 2013
Messages
3,630
Oh well, @Redcoat's answer is way better than mine. Go with that.
 

Apollo

Wizard
Joined
Jun 13, 2013
Messages
1,458
It would normally happen when "zpool readonly=ON" or "zfs readonly=on", not sure which one realy.
For this to be fixed, I think, would be to set it to readlony=OFF, detach then attach back or simply not detaching anything and restart Freenas.
 
Top