Hello Eric,
Wednesday, August 16, 2006, 4:48:46 PM, you wrote:
ES> What does 'zfs list -o name,mountpoint' and 'zfs mount' show after the
ES> import? My only guess is that you have some explicit mountpoint set
ES> that's confusing the DSl-orderered mounting code. If this is the case,
ES> this w
What does 'zfs list -o name,mountpoint' and 'zfs mount' show after the
import? My only guess is that you have some explicit mountpoint set
that's confusing the DSl-orderered mounting code. If this is the case,
this was fixed in build 46 (likely to be in S10u4) to always mount
datasets in mountpoi
Hello Mark,
Wednesday, August 16, 2006, 3:23:43 PM, you wrote:
MM> Robert,
MM> Are you sure that nfs-s5-p0/d5110 and nfs-s5-p0/d5111 are mounted
MM> following the import? These messages imply that the d5110 and d5111
MM> directories in the top-level filesystem of pool nfs-s5-p0 are not
MM> empt
Robert,
Are you sure that nfs-s5-p0/d5110 and nfs-s5-p0/d5111 are mounted
following the import? These messages imply that the d5110 and d5111
directories in the top-level filesystem of pool nfs-s5-p0 are not
empty. Could you verify that 'df /nfs-s5-p0/d5110' displays
nfs-s5-p0/d5110 as the "Fil
All pools were exported than I tried to import one-by-one and got this with
only a first pool.
bash-3.00# zpool export nfs-s5-p4 nfs-s5-s5 nfs-s5-s6 nfs-s5-s7 nfs-s5-s8
bash-3.00# zpool import nfs-s5-p4
cannot mount '/nfs-s5-p4/d5139': directory is not empty
cannot mount '/nfs-s5-p4/d5141': direc
