version 1.3, 2009/10/23 23:55:51
|
version 1.6, 2009/10/26 23:19:05
|
Line 15 Use any -current build from i386 or amd6
|
Line 15 Use any -current build from i386 or amd6
|
|
|
User need to |
User need to |
|
|
modload solaris |
modload solaris |
modload zfs |
modload zfs |
|
|
After loading modules user can create zpool(zfs version of volume manager) and manage zfs file systems on it. |
After loading modules user can create zpool(zfs version of volume manager) and manage zfs file systems on it. |
|
|
zpool create {zpool name} {type} {device} |
zpool create {zpool name} {type} {device} |
|
|
where type is: |
where type is: |
|
|
Line 31 where type is:
|
Line 31 where type is:
|
|
|
device is blod device on netbsd /dev/sd0a for example. |
device is blod device on netbsd /dev/sd0a for example. |
|
|
zpool create tank mirror /dev/sd0a /dev/sd1a creates mirrored zpool between 2 disk partitions. |
zpool create tank mirror /dev/sd0a /dev/sd1a creates mirrored zpool between 2 disk partitions. |
|
|
With zpool created we can create zfs filesystems or zvols(zfs logical volume disks) |
With zpool created we can create zfs filesystems or zvols(zfs logical volume disks) |
|
|
zfs create -V {size} tank/{zvol name} creates zvol with {zvol name} from ZPOOL called tank |
zfs create -V {size} tank/{zvol name} creates zvol with {zvol name} from ZPOOL called tank |
|
|
Logical disk is created in |
Logical disk is created in |
|
|
/dev/zvol/rdsk/{zpool name}/{zvol name} |
/dev/zvol/rdsk/{zpool name}/{zvol name} |
/dev/zvol/dsk/{zpool name}/{zvol name} |
|
|
|
zfs create tank/{zfs name} create zfs filesystem on a zpool called tank |
/dev/zvol/dsk/{zpool name}/{zvol name} |
|
|
|
zfs create tank/{zfs name} create zfs filesystem on a zpool called tank |
|
|
## Administration |
## Administration |
|
|
|
After creating ZVOLS and filesystem they are saved in a /etc/zfs/zpool.cache file and loaded after nextzfs module load. |
|
|
--- |
--- |
# 3. Known Bugs |
# 3. Known Bugs |
|
|
Line 80 because zio_root is basicaly zio_null.
|
Line 83 because zio_root is basicaly zio_null.
|
|
|
zfs umount panic is caused by using FreeBSD approach in zfs_reclaim. |
zfs umount panic is caused by using FreeBSD approach in zfs_reclaim. |
|
|
|
* vnode fsync bug |
|
|
|
I think that we are hitting this bug, too. I have some patches in the tree which fixes deadlod in vnode reclaim but after that I'm getting another deadlock in VOP_FSYNC. |
|
|
## Functional bugs |
## Functional bugs |
* Snapshots |
* Snapshots |
* Permissions |
* Permissions |
* Old code, we should update NetBSD zfs port to new code |
* Old code, we should update NetBSD zfs port to new code |
|
* More tasks can be found at [http://nxr.netbsd.org/xref/src/external/cddl/osnet/TODO] |
|
|
|
# External Documentation links |
|
Nice zfs howto written for zfs + mac os x [http://code.google.com/p/maczfs/wiki/GettingStarted] |