Today's Page Hits: 294
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/.
So last night I reinstalled Nevada b35 on wont. Of course, I didn't bother nuking my ZFS filesystem. And of course it did not show up after the system came up. But that is the same as a UFS filesystem. For UFS you need to add it to /etc/vfstab to get it mounted automatically upon a reboot.
What do I need to do with a ZFS filesystem?
# zpool import
pool: zoo
id: 6577446991347315550
state: ONLINE
action: The pool can be imported using its name or numeric identifier. The
pool may be active on on another system, but can be imported using
the '-f' flag.
config:
zoo ONLINE
mirror ONLINE
c0d1s0 ONLINE
c0d1s1 ONLINE
mirror ONLINE
c0d1s3 ONLINE
c0d1s4 ONLINE
# zpool import zoo cannot import 'zoo': pool may be in use from other system use '-f' to import anyway # zpool import -f zoo cannot mount 'zoo/home/nfsv2': mountpoint or dataset is busy
# df -h
Filesystem size used avail capacity Mounted on
/dev/dsk/c0d0s0 30G 4.3G 25G 15% /
/devices 0K 0K 0K 0% /devices
ctfs 0K 0K 0K 0% /system/contract
proc 0K 0K 0K 0% /proc
mnttab 0K 0K 0K 0% /etc/mnttab
swap 1.5G 716K 1.5G 1% /etc/svc/volatile
objfs 0K 0K 0K 0% /system/object
/usr/lib/libc/libc_hwcap2.so.1
30G 4.3G 25G 15% /lib/libc.so.1
fd 0K 0K 0K 0% /dev/fd
swap 1.5G 108K 1.5G 1% /tmp
swap 1.5G 44K 1.5G 1% /var/run
/dev/dsk/c0d0s7 5.7G 5.8M 5.6G 1% /export/home
/vol/dev/dsk/c1t0d0/"kanigixx86"
2.8G 2.8G 0K 100% /cdrom/"kanigixx86"
zoo 134G 100K 128G 1% /zoo
zoo/x86 134G 2.8G 128G 3% /zoo/x86
zoo/home 10G 100K 10.0G 1% /export/zfs
zoo/home/nfsv2 10G 98K 10.0G 1% /export/zfs/nfsv2
zoo/home/tdh 10G 98K 10.0G 1% /export/zfs/tdh
zoo/home/nfsv3 10G 98K 10.0G 1% /export/zfs/nfsv3
zoo/home/nfsv4 10G 108K 10.0G 1% /export/zfs/nfsv4
zoo/isos 134G 2.8G 128G 3% /zoo/isos
No idea why 'zfs import -f zoo' spit out a warning. Well, it might have to do with the fact that I didn't do a 'zfs export' before I did the reinstall.
And finally, lets make sure we can see the contents across the network on sandman:
# showmount -e wont export list for wont: /export/zfs (everyone) /export/zfs/tdh (everyone) /export/zfs/nfsv3 (everyone) /export/zfs/nfsv4 (everyone) /export/zfs/nfsv2 (everyone) # cd /net/wont/export # ls -la total 3 dr-xr-xr-x 2 root root 2 Mar 21 15:36 . dr-xr-xr-x 2 root root 2 Mar 21 15:36 .. dr-xr-xr-x 1 root root 1 Mar 21 15:36 zfs # cd zfs # ls -la total 7 drwxr-xr-x 6 root sys 6 Mar 20 23:12 . dr-xr-xr-x 2 root root 2 Mar 21 15:36 .. dr-xr-xr-x 3 root root 3 Mar 21 15:35 .zfs dr-xr-xr-x 1 root root 1 Mar 21 15:36 nfsv2 dr-xr-xr-x 1 root root 1 Mar 21 15:36 nfsv3 dr-xr-xr-x 1 root root 1 Mar 21 15:36 nfsv4 dr-xr-xr-x 1 root root 1 Mar 21 15:36 tdh # cd tdh # ls -la total 4 drwxr-xr-x 2 1066 staff 2 Mar 20 23:12 . drwxr-xr-x 6 root sys 6 Mar 20 23:12 .. dr-xr-xr-x 3 root root 3 Mar 21 15:36 .zfs
Obviously, the userid of 1066 has not been added to sandman. Notice that this is a NFSv4 mount and the ID mapping must be working correctly. I.e., if it were not, we would see nobody. A NFSv3 mount would show 1066 regardless of the ID domain settings.