On Fri, Mar 21, 2008 at 8:10 PM, eric kustarz <[EMAIL PROTECTED]> wrote:
> > Also history only tells me what someone typed. It doesn't tell me
> > what other changes may have occurred.
>
> What other changes were you thinking about?
I don't know what Torrey was thinking of, but here's an example pool:
# zpool history
History for 'mail':
2008-01-16.17:22:36 zpool create mail mirror c0t11d0 c0t12d0
2008-01-22.14:30:43 zpool export mail
2008-03-13.18:00:22 zpool import mail
# zpool status
pool: mail
state: ONLINE
scrub: none requested
config:
NAME STATE READ WRITE CKSUM
mail ONLINE 0 0 0
mirror ONLINE 0 0 0
c2t3d0 ONLINE 0 0 0
c2t2d0 ONLINE 0 0 0
As you can see, it was created with one pair of device names, and now
it shows up as another pair. There's no way to tell what the new
device names are just from the zpool history. In the two-disk case,
this isn't really a problem, but if I had some disk shelves and moved
them to a different disk controller, for example, it might be a pain
to change all the names to recreate the pool in a failure situation.
Especially with FC-like device names that are a mile long.
So, I'll add an endorsement to the idea of 'zpool config' and request
that it display current device names, not the ones the pool was made
with. Perhaps it could display all child filesystems and their
non-default properties, as well? I don't know what to do about
snapshots, but the logical thing to do would probably be to ignore
them. In short, any information about the pool should be reported,
but information in the pool omitted.
Will
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
