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/[EMAIL PROTECTED] - 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@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
