On Wed, Feb 17, 2010 at 17:44, Daniel Carosone <d...@geek.com.au> wrote:
> On Wed, Feb 17, 2010 at 04:48:23PM -0500, Ethan wrote:
> > It looks like using p0 is exactly what I want, actually. Are s2 and p0
> both
> > the entire disk?
>
> No. s2 depends on there being a solaris partition table (Sun or EFI),
> and if there's also an fdisk partition table (disk shared with other
> OS), s2 will only cover the solaris part of the disk. It also
> typically doesn't cover the last 2 cylinders, which solaris calls
> "reserved" for hysterical raisins.
>
> > The idea of symlinking to the full-disk devices from a directory and
> using
> > -d had crossed my mind, but I wasn't sure about it. I think that is
> > something worth trying.
>
> Note, I haven't tried it either..
>
> > I'm not too concerned about it not working at boot -
> > I just want to get something working at all, at the moment.
>
> Yup.
>
> --
> Dan.
Success!
I made a directory and symlinked p0's for all the disks:
et...@save:~/qdsk# ls -al
total 13
drwxr-xr-x 2 root root 7 Feb 17 23:06 .
drwxr-xr-x 21 ethan staff 31 Feb 17 14:16 ..
lrwxrwxrwx 1 root root 17 Feb 17 23:06 c9t0d0p0 ->
/dev/dsk/c9t0d0p0
lrwxrwxrwx 1 root root 17 Feb 17 23:06 c9t1d0p0 ->
/dev/dsk/c9t1d0p0
lrwxrwxrwx 1 root root 17 Feb 17 23:06 c9t2d0p0 ->
/dev/dsk/c9t2d0p0
lrwxrwxrwx 1 root root 17 Feb 17 23:06 c9t4d0p0 ->
/dev/dsk/c9t4d0p0
lrwxrwxrwx 1 root root 17 Feb 17 23:06 c9t5d0p0 ->
/dev/dsk/c9t5d0p0
I attempt to import using -d:
et...@save:~/qdsk# zpool import -d .
pool: q
id: 5055543090570728034
state: ONLINE
status: The pool is formatted using an older on-disk version.
action: The pool can be imported using its name or numeric identifier,
though
some features will not be available without an explicit 'zpool
upgrade'.
config:
q ONLINE
raidz1 ONLINE
/export/home/ethan/qdsk/c9t4d0p0 ONLINE
/export/home/ethan/qdsk/c9t5d0p0 ONLINE
/export/home/ethan/qdsk/c9t2d0p0 ONLINE
/export/home/ethan/qdsk/c9t1d0p0 ONLINE
/export/home/ethan/qdsk/c9t0d0p0 ONLINE
The pool is not imported. This does look promising though. I attempt to
import using the name:
et...@save:~/qdsk# zpool import -d . q
it sits there for a while. I worry that it's going to hang forever like it
did on linux.
but then it returns!
et...@save:~/qdsk# zpool status
pool: q
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: scrub in progress for 0h2m, 0.43% done, 8h57m to go
config:
NAME STATE READ WRITE CKSUM
q ONLINE 0 0 0
raidz1 ONLINE 0 0 0
/export/home/ethan/qdsk/c9t4d0p0 ONLINE 0 0 0
/export/home/ethan/qdsk/c9t5d0p0 ONLINE 0 0 0
/export/home/ethan/qdsk/c9t2d0p0 ONLINE 0 0 0
/export/home/ethan/qdsk/c9t1d0p0 ONLINE 0 0 0
/export/home/ethan/qdsk/c9t0d0p0 ONLINE 0 0 0
errors: No known data errors
All the filesystems are there, all the files are there. Life is good.
Thank you all so much.
-Ethan
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
