> From: Ian Collins [mailto:i...@ianshome.com] > > 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!
Didn't miss any "not," but it may not have been written clearly. If you *intended* to set the destination filesystem readonly before, and you only discovered it's not readonly later, evident by the fact that something wrote to it and now you can't receive incremental zfs snapshots... Then you want to correct your mistake. Whatever was writing to the backup fileserver, it shouldn't have been. So set the filesystem readonly, rollback to the latest snapshot that corresponds to the primary server, so you can again start receiving incrementals. _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
