version 1.3, 2009/10/23 23:55:51
|
version 1.4, 2009/10/23 23:58:32
|
Line 40 zfs create -V {size} tank/{zvol name} cr
|
Line 40 zfs create -V {size} tank/{zvol name} cr
|
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} |
/dev/zvol/dsk/{zpool name}/{zvol name} |
|
|
zfs create tank/{zfs name} create zfs filesystem on a zpool called tank |
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 |