>>>>> "r" == Ross <[EMAIL PROTECTED]> writes:
r> I've just gotten a pool back online after the server booted
r> with it unavailable, but found that NFS shares were not
r> automatically restarted when the pool came online.
``me, too.'' in b44, in b71.
for workarounds, export/import can probably fix it iirc. You might
try 'zfs share -a'---I saw that in another email and will try it the
next time my box panics.
I also have problems, if I do as you did---boot with a pool
unavailable, then get it online somehow without exporting it---that
filesystems mount in the wrong order. I have a lot of datasets nested
inside each other. Some of the parent datasets will just silently not
mount, but their children will. Then after I notice it, issuing 'zfs
mount -a' will say something like can't mount blah/blah: directory not
empty. The workaround is to manually unmount all the child datasets,
rmdir the mountpoints, and then mount them by hand in the right
tree-traversal order.
pgpkB7Bw3YWAT.pgp
Description: PGP signature
_______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
