On Wed, Apr 7, 2010 at 17:51, Brandon High <bh...@freaks.com> wrote: > On Wed, Apr 7, 2010 at 1:32 PM, Will Murnane <will.murn...@gmail.com> wrote: >> This process took about 12 hours to do, so it's frustrating that >> (apparently) snapshots disappearing causes the replication to fail. >> Perhaps some sort of locking should be implemented to prevent >> snapshots that will be needed from being destroyed. > > What release of opensolaris are you using? Recent versions have the > ability to place holds on snapshots, and doing a send will > automatically place holds on the snapshots. This is on b134: $ pfexec pkg image-update No updates available for this image.
There is a "zfs hold" command available, but checking for holds on the snapshot I'm trying to send (I started it again, to see if disabling automatic snapshots helped) doesn't show anything: $ zfs holds -r h...@next $ echo $? 0 and applying a recursive hold to that snapshot doesn't seem to hold all its children: $ pfexec zfs hold -r keep h...@next $ zfs holds -r h...@next NAME TAG TIMESTAMP huge/homes/d...@next keep Wed Apr 7 18:02:09 2010 h...@next keep Wed Apr 7 18:02:09 2010 $ zfs list -r -t all huge | grep next h...@next 204K - 2.80T - huge/back...@next 0 - 42.0K - huge/ho...@next 0 - 42.9M - huge/homes/cnl...@next 59.9K - 165G - huge/homes/d...@next 0 - 42.0K - huge/homes/svnb...@next 0 - 46.4M - huge/homes/w...@next 23.9M - 95.7G - Suggestions? Comments? Will _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
