I'm currently running a Sun Fire V880 with snv_134, but would like to
upgrade the machine to a self-built snv_144. Unfortunately, boot
environment creation fails:
# beadm create snv_134-svr4
Unable to create snv_134-svr4.
Mount failed.
In truss output, I find
2514: mount("rpool", "/rpool", MS_OPTIONSTR, "zfs", 0x00000000, 0,
0xFFBFA170, 1024) Err#2 ENOENT
I can reproduce the failure with
# zfs mount rpool
cannot mount 'rpool': No such file or directory
but /rpool exists and is empty.
Non-default properties for the dataset are
# zfs get -s local all rpool
NAME PROPERTY VALUE SOURCE
rpool mountpoint /rpool local
rpool compression on local
rpool canmount noauto local
No defaulting of mountpoint and/or canmount did make a difference. This
very much looks like
6741948 ZFS pool root dataset sometimes fails to be mounted after "zpool import"
which was closed as not reproducible.
I've no idea how to avoid/fix this issue. Suggestions?
Thanks.
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
