Yeah -F should probably work fine (I'm trying it as we speak, but it takes a little while), but it makes me a bit nervous. I mean, it should only be necessary if (as the error message suggests) something HAS actually changed, right?
So, here's what I tried - first of all, I set the backup FS to readonly. That resulted in the same error message. Strange, how could something have changed since the last snapshot if I CONSCIOUSLY didn't change anything or CD into it or anything AND it was set to readonly? Oh well, so I tried another idea - I had been setting compression to gzip-1 on my backup, but my source filesystem had compression=gzip-1 and recordsize=16k. So, I set both of those settings on my backup FS (and readonly OFF). Now the only difference between my backup and my backup source should be the fact that they have different FS names (datapool/shares and backup/shares), but they would kinda have to, wouldn't they? At any rate, I'm trying -F now, but that makes me a bit uncomfortable. Why does zfs think something has changed? Am I truly creating a backup that could be restored and won't have something screwed up either with some of the older snapshots or with the current, "promoted" version of the FS? If something really has changed between snapshots, or the incrementals aren't copied over just right, I could end up with my best backup being all corrupted. (My other backup methods, of course, contain only current data, not the whole series of snapshots.) -- This message posted from opensolaris.org _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
