Multi-boot system (s10u3, s10u4, and nevada84) having problems mounting ZFS filesystems at boot time. The pool is s10u3 are are most of the filesystems. A few of the filesystems are nevada83. # zfs mount -a cannot mount ''/pandora'': directory is not empty # zfs list -o name,mountpoint NAME MOUNTPOINT pandora /pandora pandora/domains /pandora/domains pandora/domains/fedora8 /pandora/domains/fedora8 pandora/domains/nv83a /pandora/domains/nv83a pandora/domains/s10u5 /pandora/domains/s10u5 pandora/domains/ub710 /pandora/domains/ub710 pandora/domains/winxp /pandora/domains/winxp pandora/export /export pandora/home /export/home pandora/home-restore legacy pandora/home-restore at initial_restore - pandora/iso /export/iso All of the filesystems except the legacy and snapshots are mounted. The error return code is making filesystem/local really fussy, which makes booting really fussy, etc :-) I do notice that zfs umount is leaving the mountpoints behind. The other thing is more of a question. I understand why the ZFS filesystems created in nevada don''t mount on s10. But should those cause mountall (and filesystem/local) to fail ? I guess I could do legacy mounts for all my xVM domains, but that seems un-ZFS like. Bob
Bob, Are you sure that /pandora is mounted? I hazard a guess that the error message is caused by mounting zpool:pandora when /pandora is not empty. I notice that snv81 started mounting zfs in level-order whereas my snv73 did not. On Sun, Mar 9, 2008 at 10:16 AM, Bob Netherton <Bob.Netherton at sun.com> wrote:> Multi-boot system (s10u3, s10u4, and nevada84) having problems > mounting ZFS filesystems at boot time. The pool is s10u3 > are are most of the filesystems. A few of the filesystems > are nevada83. > > # zfs mount -a > cannot mount ''/pandora'': directory is not empty > > # zfs list -o name,mountpoint > NAME MOUNTPOINT > pandora /pandora > pandora/domains /pandora/domains > pandora/domains/fedora8 /pandora/domains/fedora8 > pandora/domains/nv83a /pandora/domains/nv83a > pandora/domains/s10u5 /pandora/domains/s10u5 > pandora/domains/ub710 /pandora/domains/ub710 > pandora/domains/winxp /pandora/domains/winxp > pandora/export /export > pandora/home /export/home > pandora/home-restore legacy > pandora/home-restore at initial_restore - > pandora/iso /export/iso > > > All of the filesystems except the legacy and snapshots are > mounted. The error return code is making filesystem/local > really fussy, which makes booting really fussy, etc :-) > > I do notice that zfs umount is leaving the mountpoints behind. > > > The other thing is more of a question. I understand why the > ZFS filesystems created in nevada don''t mount on s10. But > should those cause mountall (and filesystem/local) to fail ? > I guess I could do legacy mounts for all my xVM domains, but > that seems un-ZFS like. > > > Bob > > _______________________________________________ > zfs-discuss mailing list > zfs-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss >-- Just me, Wire ... Blog: <prstat.blogspot.com>
On Mon, 2008-03-10 at 15:19 +0800, Wee Yeh Tan wrote:> Bob, > > Are you sure that /pandora is mounted?Now that you ask, not sure. It shows as mounted but there is no data in there other than the mountpoints for the other children filesystems.> zpool:pandora when /pandora is not empty. I notice that snv81 started > mounting zfs in level-order whereas my snv73 did not.This was working just fine on nv83a until I started renaming a bunch of filesystems. That seemed to upset everything. I went back to s10u3, recreated all of the filesystems and all is work working again. Wish I could have kept things around for more diagnostics, but I had to get the system where it could actually boot without some manual intervention. Bob