Diff for /wikisrc/zfs.mdwn between versions 1.37 and 1.38

version 1.37, 2021/02/17 17:53:07 version 1.38, 2021/02/17 18:14:41
Line 177  fixed. Line 177  fixed.
 Within a ZFS pool, the standard approach is to have file systems, but  Within a ZFS pool, the standard approach is to have file systems, but
 one can also create a zvol, which is a block device of a certain size.  one can also create a zvol, which is a block device of a certain size.
   
 \todo The zvol will appear as /dev/???? and can be used in many  As an example, "zfs create -V 16G tank0/xen-netbsd-9-amd64" creates a
 respects like a slice.  However, the system will not read disklabels  zvol (intended to be a virtual disk for a domU).
 and gpt labels from a zvol; in this respect it is more like a disklabel  
 partition or wedge than a disk drive.  
   
 \todo Explain that one can export a zvol via iscsi.  The zvol in the example will appear as
   /dev/zvol/rdsk/tank0/xen-netbsd-9-amd64 and
   /dev/zvol/dsk/tank0/xen-netbsd-9-amd64 and can be used like a
   disklabel partition or wedge.  However, the system will not read
   disklabels and gpt labels from a zvol.
   
   Doing "swapctl -a" on a zvol device node fails.  \todo Is it really
   true that NetBSD can't swap on a zvol?
   
 \todo Explain if one can swap on a zvol.  \todo Explain that one can export a zvol via iscsi.
   
 \todo Explain that one can use ccd to create a normal-looking disk  One can use ccd to create a normal-looking disk from a zvol.  This
 from a zvol.  This allows reading a GPT label from the zvol, which is  allows reading a GPT label from the zvol, which is useful in case the
 useful in case the zvol had been exported via iscsi and some other  zvol had been exported via iscsi and some other system created a
 system created a label.  label.
   
 # Memory usage  # Memory usage
   

Removed from v.1.37  
changed lines
  Added in v.1.38


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