Matt - The 'zpool status -v' output is guaranteed to be exactly the same as what ZFS sees.
The only exception to this is if you run the command as a non-root user, and the device paths have changed, then the path names may be incorrect. Running it once as root will correctly update the paths. You can also try running 'zdb -C', which will dump the cached nvlist configuration of the pool, but it is not guaranteed to be correct, unlike the 'zpool status -v' output. If you think there is a bug in zpool(1m), then you can also run 'mdb -k' and run '::spa -v' to show all pools and their configurations. Hope that helps, - Eric On Tue, Oct 24, 2006 at 12:12:10PM -0700, Matt Ingenthron wrote: > Hi all, > > Sorry for the newbie question, but I've looked at the docs and haven't > been able to find an answer for this. > > I'm working with a system where the pool has already been configured and > want to determine what the configuration is. I had thought that'd be > with zpool status -v <poolname>, but it doesn't seem to agree with the > configuration that was described to me. Is there another way of getting > the zpool config? This is with nevada build 47, so I can't use the new > zpool history. > > This is what the system is showing me (and looks like a single raidz1 > with 47 devices). Either that's correct and the config described to me > by the admin who set it up is incorrect, or there must be another way to > get the pool configuration: > > # zpool status -v > pool: maxPool > state: ONLINE > scrub: none requested > config: > > NAME STATE READ WRITE CKSUM > maxPool ONLINE 0 0 0 > raidz1 ONLINE 0 0 0 > c0t0d0 ONLINE 0 0 0 > c0t1d0 ONLINE 0 0 0 > c0t2d0 ONLINE 0 0 0 > c0t3d0 ONLINE 0 0 0 > c0t4d0 ONLINE 0 0 0 > c0t5d0 ONLINE 0 0 0 > c0t6d0 ONLINE 0 0 0 > c0t7d0 ONLINE 0 0 0 > c1t0d0 ONLINE 0 0 0 > c1t1d0 ONLINE 0 0 0 > c1t2d0 ONLINE 0 0 0 > c1t3d0 ONLINE 0 0 0 > c1t4d0 ONLINE 0 0 0 > c1t5d0 ONLINE 0 0 0 > c1t6d0 ONLINE 0 0 0 > c1t7d0 ONLINE 0 0 0 > c4t0d0 ONLINE 0 0 0 > c4t1d0 ONLINE 0 0 0 > c4t2d0 ONLINE 0 0 0 > c4t3d0 ONLINE 0 0 0 > c4t4d0 ONLINE 0 0 0 > c4t5d0 ONLINE 0 0 0 > c4t6d0 ONLINE 0 0 0 > c4t7d0 ONLINE 0 0 0 > c5t1d0 ONLINE 0 0 0 > c5t2d0 ONLINE 0 0 0 > c5t3d0 ONLINE 0 0 0 > c5t5d0 ONLINE 0 0 0 > c5t6d0 ONLINE 0 0 0 > c5t7d0 ONLINE 0 0 0 > c6t0d0 ONLINE 0 0 0 > c6t1d0 ONLINE 0 0 0 > c6t2d0 ONLINE 0 0 0 > c6t3d0 ONLINE 0 0 0 > c6t4d0 ONLINE 0 0 0 > c6t5d0 ONLINE 0 0 0 > c6t6d0 ONLINE 0 0 0 > c6t7d0 ONLINE 0 0 0 > c7t0d0 ONLINE 0 0 0 > c7t1d0 ONLINE 0 0 0 > c7t2d0 ONLINE 0 0 0 > c7t3d0 ONLINE 0 0 0 > c7t4d0 ONLINE 0 0 0 > c7t5d0 ONLINE 0 0 0 > c7t6d0 ONLINE 0 0 0 > c7t7d0 ONLINE 0 0 0 > > errors: No known data errors > > > Thanks in advance, > > - Matt > > -- > Matt Ingenthron - Web Infrastructure Solutions Architect > Sun Microsystems, Inc. - Systems Practice, Client Solutions > http://blogs.sun.com/mingenthron/ > email: [EMAIL PROTECTED] Phone: 310-242-6439 > > _______________________________________________ > zfs-discuss mailing list > zfs-discuss@opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss -- Eric Schrock, Solaris Kernel Development http://blogs.sun.com/eschrock _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
