Hi, I read in zfs admin guide and could not try this (on amd64 r196047): - Rolling Back a Dataset Without Unmounting - Solaris Express Community Edition, build 80: This release provides the ability to rollback a dataset without unmounting it first. This feature means that zfs rollback -f option is no longer needed to force an umount operation. The -f option is no longer supported, and is ignored if specified. # zfs create tank/rollback-test # echo 1 > /rollback-test/file # zfs snapshot tank/rollback-test_at_snapshot1 # echo 2 >> /rollback-test/file # zfs rollback tank/rollback-test_at_snapshot1 # cat /rollback-test/file # zfs destroy tank/rollback-test works great, because file system is not busy, but if I open some file before rollback: # vim /rollback-test/file ^Z # fstat | grep '/rollback-test' root vim 1254 4 /rollback-test 7 -rw-r--r-- 4096 rw # zfs rollback tank/rollback-test_at_snapshot1 # fg vim offer me to load file because it has changed, and works great, but after rollback I can not list /rollback-test directory and all zfs commands lock up. Reboot also hangs in unkillable processes. After reset I can destroy dataset. Fanny part is that I can even rollback root file system from which I boot. I know it's crazy to "force"-rollback live file system, just interesting why they made such change. -- Artis Caune Everything should be made as simple as possible, but not simpler.Received on Fri Aug 14 2009 - 07:18:53 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:53 UTC