Diff for /wikisrc/users/haad/Attic/porting_zfs.mdwn between versions 1.1 and 1.5

version 1.1, 2009/10/22 04:28:54 version 1.5, 2009/10/24 00:04:44
Line 1 Line 1
 # 1. Status of NetBSD zfs port  # 1. Status of NetBSD zfs port
     
 NetBSD zfs port is work in progress and can easily panic your system.  NetBSD zfs port is work in progress and can easily panic your system.
   
   **ZFS currently works ony on i386!!**
   
 ---  ---
 # 2. Using NetBSD ZFS port   # 2. Using NetBSD ZFS port 
   
   
 ## Instalation   ## Instalation 
   
   Use any -current build from i386 or amd64 architecture. All tools and modules should be built by default, now. There are 2 modules used for ZFS solaris.kmod and zfs.kmod. Solaris module provides solaris like interfaces to zfs on NetBSD. The second module is zfs and provides zfs file system functions.
   
 ## Configuration  ## Configuration
   
   User need to
   
       modload solaris
       modload zfs
   
   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} 
   
   where type is:
   
   * mirror
   * raidz
   * raidz2
   * default is normal linear allocation
   
   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.
   
   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
   
   Logical disk is created in 
   
       /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 
   
 ## 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 45  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]

Removed from v.1.1  
changed lines
  Added in v.1.5


CVSweb for NetBSD wikisrc <wikimaster@NetBSD.org> software: FreeBSD-CVSweb