Apologies for any confusion, but I am now able to give more output
regarding the zpool fitz.

unknown# zfs list --> returns list of zfs file system fitz and related
snapshots

unknown# zpool status
pool: fitz
state: ONLINE
status: The pool is formatted using an older on-disk format. The pool
can still be used, but some features are unavailable.
action: Upgrade the pool using 'zpool upgrade'. Once this is done, the
pool will no longer be accessible on older software versions.
scrub: none requested
config:
NAME        SATE
fitz        ONLINE
c2d0s7      ONLINE
errors: No known data errors

unknown# zpool upgrade -v
This system is currently running ZFS version 3.

the following versions are supported:
......

unknown# zfs mount --> lists the zfs pool as mounted as it should be at
/fitz

but 'zfs unmount fitz' returns 'cannot unmount 'fitz' : not currently
mounted

zpool import --> no pools available to import
zpool import -d /fitz --> no pools available to import

thanks,

aric


================================================
I believe I am experiencing a similar, but more severe issue and I do
not know how to resolve it. I used liveupgrade from s10u2 to NV b46
(via solaris express release). My second disk is zfs with the file
system fitz. I did a 'zpool export fitz'

Reboot with init 6 into new environment, NV b46, I get the following
error:
cannot mount '/fitz' : directory is not empty
svc:/system/filesystem/local:default: WARNING: /usr/sbin/zfs mount -a
failed: exit status 1
svc.startd[7]: svc:/system/filesystem/local:default: Method
"/lib/svc/method/fs-local" failed with exit status 95.

zfs list = nothing listed.

There is already a /fitz directory filled with the zpool fitz files on
mounted. Since filesystem/local svc won't start, I cannot start X,
which is critical to using the computer. I now see that there was no
real need to export the pool fitz and that I should have just imported
it once in the new BE. How can I now solve this issue? (BTW, attempting
to boot back into s10u2, the original BE, results in a kernel panic, so
I cannot go back).

thanks,

aric


_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss

Reply via email to