Thanks Phoenix for the info! Actually I have used the "scrub" in my opensolaris box and it is very impressive how fast it works on 2X250 GB drives with 50% utilization and running heavy disk I/O apps during.
Now you mentioned earlier that:
Quote:
|
To make things simple, as well, you should use glabel to label the disks/slices/partitions, and then reference the labels when creating the vdevs (zpool create storage mirror label/disk0slice0 label/disk1slice0, for example). That way, if you change disks, or change controllers, or whatever, ZFS will continue to work right away, without any manual intervention to get the device names sync'd.
|
I am currently experimenting in a ZFS boot environment with FreeBSD 8.0 in Vmware server. My question is mainly regarding the mount points. In Opensolaris the system is configured like this:
Code:
gkontos@hp:~# cat /etc/vfstab
#device device mount FS fsck mount mount
#to mount to fsck point type pass at boot options
#
/devices - /devices devfs - no -
/proc - /proc proc - no -
ctfs - /system/contract ctfs - no -
objfs - /system/object objfs - no -
sharefs - /etc/dfs/sharetab sharefs - no -
fd - /dev/fd fd - no -
swap - /tmp tmpfs - yes -
/dev/zvol/dsk/rpool/swap - - swap - no -
However, I haven't found any way to avoid using a traditional fstab in FreeBSD:
Code:
zfsroot# cat /etc/fstab
/dev/gpt/swap0 none swap sw 0 0
/dev/gpt/swap3 none swap sw 0 0
tank/usr /usr zfs rw 0 0
tank/var /var zfs rw 0 0
tank/tmp /tmp zfs rw 0 0
The problem with that is that every time I issue a command like:
Code:
zfs create tank/usr/ports
I have to specify a mount point as well unlike in OpenSolaris where the similar command would create the directory and mount it.
On the other hand if I issue:
Code:
mkdir /usr/ports
zfs create tank/usr/ports
Seems to overcome the problem. I am sure that I do something wrong!
Your help will be much appreciated
George