After crash old deleted files appear again and new files and other changes are missin

[rstumbaum]

Hi,

we experienced a power failure yesterday. After this crash we restartet the FreeNAS and now, even when zpool status reports no error we are missing files, see older already deleted files and have errors on the filesystem permissions.

What happened here?

Thanks
Rainer

zpool status tank01
pool: tank01
state: ONLINE
scrub: none requested
config:

NAME STATE READ WRITE CKSUM
tank01 ONLINE 0 0 0
raidz1 ONLINE 0 0 0
mfid0 ONLINE 0 0 0
mfid1 ONLINE 0 0 0
mfid2 ONLINE 0 0 0
mfid3 ONLINE 0 0 0
mfid4 ONLINE 0 0 0
mfid5 ONLINE 0 0 0

errors: No known data errors

 

[rstumbaum]

Ok, so we found what the problem is.

We also started yesterday again making backups from the FreeNAS 7 Server to the already upgraded FreeNAS 8 Server.

But stupidly(!!!) from the FreeNAS Developers the way rsync client vs. rsync daemon acts changed from Version 7 to Version 8.

In Version 7 the rsync server module on the backup client would be set to readonly and the rsync client on the backup server would pull the data.

In Version 8 the backup client should run the rsync client pushing the data to a read/write rsync server module running on the backup server.

In our case now we pulled the data from the backup server to the client adding already deleted files and folders, overwriting changed files but leaving newer files untouched.

WTF!!!
And there is nowhere in the log that shows the command line of the rsync task...

 

[William Grzybowski]

Don't blame FreeNAS 8 for your stupidity, RTFM

 

[rstumbaum]

Mmmh, still could be discussing why the to-be-backed-up-client should send the data, rather than the backup-server pulling it from a read-only configured module on the client...

And such a change from one version to the next should be documented in the manual section with exclamation marks! The guy who configured the new FreeNAS 8 backup server was a different guy to who configured the FreeNAS 7 backup server.

 

[rstumbaum]

So then, how to configure a rsync backup from FreeNAS 7 to FreeNAS 8?

 

[William Grzybowski]

Its pretty clear: http://doc.freenas.org/index.php/Rsync_Tasks

Nobody is stopping you from using cronjobs

 

[rstumbaum]

So what is the best practise here?
Start the rsyncd daemon read/write to receive the Files on the FreeNAS 8 backup server and create an extra manual cronjob on FreeNAS 7 to now push the files?
Or:
Start the rsyncd daemon readonly to send the files on the FreeNAS 7 backup client and create an extra manual cronjob on freeNAS 8 backup server to pull the files?

I have to say I prefer the bottom option because if the FreeNAS Developers decide on changing the way how it works again the readonly rsyncd daemon is not able to overwrite the current data... :-(

 

[William Grzybowski]

Whatever works best for you...

On 8.2 you will be able to choose between pull or push for rsync client

 

[rstumbaum]

So - Analysis of our damage is finished:

The backup we copied over was from August. That was around the time we upgraded to FreeNAS 8 on the backup server and then had to fiddle around with the time machine backup and PAM again.

We copied tonight around 1 TeraByte of files from that backup over the current data - the ladies in marketing and accounting lost about 3 month work...

The biggest file-copied-list of just one samba share is 37 MByte.

People using Outlook PST files on their home drives lost 3 months of mail.

And on FreeNAS 7 we did not use snapshots :-(

 

[rstumbaum]

Whatever works best for you...

On 8.2 you will be able to choose between pull or push for rsync client

And maybe ist is a good idea to use as description for the UI
"Destination Share" instead of "Local share"
and
"Source Rsync Server" instead of "Remote Rsync Server"
and
"Source module name" instead of "Remote module name"

And when you change again it should be easy identifiable what the data source and what the data destination is...