Today's Page Hits: 3267
I have more hair and it isn't so grey. :->
This page validates as XHTML 1.0, and will look much better in a browser that supports web standards, but it is accessible to any browser or Internet device. It was created using techniques detailed at glish.com/css/.
With the OpenSolaris pnfs binary drops, things are still pretty raw. (Hey, we could hold onto the code until it is fully baked!) A common problem is telling which machines plays which role - i.e., I've got a pNFS community set up, I've done some testing, and I've rebooted the machines. How do I remember which machine is which?
The dservadm command will help you. If it shows nothing, you have either a client or the MDS:
# dservadm listpools zpools:
Okay, we find the DS:
# dservadm listpools
zpools:
train
# uname -a
SunOS silent 5.11 pnfs-curr i86pc i386 i86pc
Now, how do I tell which of the remaining two are the MDS and client? Well, dservadm can tell me a bit more:
# dservadm listmds
mds:
192.168.2.119.8.1
# host 192.168.2.119
119.2.168.192.in-addr.arpa domain name pointer stealth
Don't worry about the extra numbers at the end of the mds identifier - just realize the first four are octets. Okay, we can now start back up with our testing.