[BACK]Return to porting_zfs.mdwn CVS log [TXT] [DIR] Up to [NetBSD Developer Wiki] / wikisrc / users / haad

Diff for /wikisrc/users/haad/Attic/porting_zfs.mdwn between versions 1.2 and 1.9

version 1.2, 2009/10/23 23:47:20 version 1.9, 2009/12/23 23:37:21
Line 2 Line 2
     
 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!!**  **ZFS currently works ony on i386 and amd64!!**
   
 ---  ---
 # 2. Using NetBSD ZFS port   # 2. Using NetBSD ZFS port 
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 {name} {type} {device}       zpool create {zpool name} {type} {device} 
   
 type:  where type is:
  * mirror  
  * raidz  * mirror
  * raidz2  * raidz
  * default is normal linear allocation  * raidz2
   * default is normal linear allocation
   
 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)
   
       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
   
 ## Show stoppers   ## Show stoppers 
   
 ### amd64  ### amd64
 * amd64 zio_root crash  
 Investigation   
 vdev_label_read_config -> zio_root calls zio_wait on a zio_root zio_t. Later zio_execute tries to generate                        
 checksum on zio->zio_data which is NULL for a zio_root. Is this ressurrection of andys zio_null problem ?   
 because zio_root is basicaly zio_null.  
                   
  Solution  
  What is difference between i386 and amd64 version why it is working on i386 and not on a amd64 that can be  
  solution.  
 ### i386   ### i386 
   
 ### Both   ### Both 
Line 69  because zio_root is basicaly zio_null. Line 75  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>
Removed from v.1.2  
changed lines
  Added in v.1.9

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