On 08/28/10 12:45 PM, Edward Ned Harvey wrote:
Another specific example ...
Suppose you "zfs send" from a primary server to a backup server. You want
the filesystems to be readonly on the backup fileserver, in order to receive
incrementals. If you make a mistake, and start writing to the backup server
filesystem, you want to be able to correct your mistake. Make it readonly,
stop anything from writing to it, rollback to the unmodified snapshot, so
you're able to receive incrementals again.
I think you have lost a "not" in there somewhere!
I always set all the backup filesystems on our staging sever read-only
(and atime=off, it that makes any difference to a read-only
filesystem). You can still receive to a read-only filesystem and
there's -F to force roll-backs. The exception is when adding a new
nested filesystem; the mount will fail unless the parent is read/write.
--
Ian.
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
