What causes these messages? cannot create snapshot ''zones/rani/ROOT/zbe-2 at migration'': dataset is busy There are zones living in zones pool, but none of the zones are running or mounted. root@:~# zfs get -r mounted,zoned,mountpoint zones/rani NAME PROPERTY VALUE SOURCE zones/rani mounted yes - zones/rani zoned off default zones/rani mountpoint /zones/rani default zones/rani/ROOT mounted no - zones/rani/ROOT zoned on local zones/rani/ROOT mountpoint legacy local zones/rani/ROOT at original mounted - - zones/rani/ROOT at original zoned - - zones/rani/ROOT at original mountpoint - - zones/rani/ROOT/zbe-2 mounted no - zones/rani/ROOT/zbe-2 zoned on local zones/rani/ROOT/zbe-2 mountpoint legacy inherited from zones/rani/ROOT root@:~# This is on a very old OS now snv_134b? I am working to upgrade them soon!
2012-05-20 8:18, Anil Jangity wrote:> What causes these messages? > > cannot create snapshot ''zones/rani/ROOT/zbe-2 at migration'': dataset is busy > > ...This is on a very old OS now snv_134b? I am working to upgrade them soon! > There are zones living in zones pool, but none of the zones are running or mounted.I''ve had such problems a few times on snv_117 and/or older, blocking recursive snapshots and the zfs-auto-snap service, and liveupgrade (OpenSolaris SXCE) among other things, but I thought they were fixed in later releases before the last ones like yours. Essentially the workaround was to mount the "offending" dataset and unmount it again if it is not needed now - this clears some internal ZFS flags and allows snapshots to proceed. This could be tricky with "zoned=on" datasets and to an extent those with a legacy mountpoint, but those problems can be worked around (i.e. disable "zoned", mount, umount, reenable "zoned"). Hope this helps, //Jim Klimov
Yup, that''s exactly what I did last night... zoned=off mountpoint=/some/place mount unmount mountpoint=legacy zoned=on Thanks! On May 20, 2012, at 3:09 AM, Jim Klimov wrote:> 2012-05-20 8:18, Anil Jangity wrote: >> What causes these messages? >> >> cannot create snapshot ''zones/rani/ROOT/zbe-2 at migration'': dataset is busy >> >> ...This is on a very old OS now snv_134b? I am working to upgrade them soon! >> There are zones living in zones pool, but none of the zones are running or mounted. > > I''ve had such problems a few times on snv_117 and/or older, > blocking recursive snapshots and the zfs-auto-snap service, > and liveupgrade (OpenSolaris SXCE) among other things, but > I thought they were fixed in later releases before the last > ones like yours. > > Essentially the workaround was to mount the "offending" > dataset and unmount it again if it is not needed now - > this clears some internal ZFS flags and allows snapshots > to proceed. This could be tricky with "zoned=on" datasets > and to an extent those with a legacy mountpoint, but > those problems can be worked around (i.e. disable "zoned", > mount, umount, reenable "zoned"). > > Hope this helps, > //Jim Klimov > > _______________________________________________ > zfs-discuss mailing list > zfs-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss