i've seen a problem where periodically a 'zfs mount -a' and sometimes
a 'zpool import <pool>' can create what appears to be a race condition
on nested mounts .. that is .. let's say that i have:
FS mountpoint
pool /export
pool/fs1 /export/home
pool/fs2 /export/home/bob
pool/fs3 /export/home/bob/stuff
if "pool" is imported (or a mount -a is done) and somehow pool/fs3
mounts first - then it will create /export/home and /export/home/bob
and pool/fs1 and pool/fs2 will fail to mount .. this seems to be
happening on more recent builds, but not predictably - so i'm still
trying to track down what's going on
On Jun 10, 2009, at 1:01 PM, Richard Elling wrote:
Something is bothering me about this thread. It seems to me that
if the system provides an error message such as "cannot mount
'/tank/home': directory is not empty" then the first plan of action
should be to look and see what is there, no?
The issue of overlaying mounts has existed for about 30 years and
invariably one discovers that events which lead to different data in
overlapping directories is the result of some sort of procedural
issue.
Perhaps once again, ZFS is a singing canary?
-- richard
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
