zfs(4fs) 맨 페이지 - 윈디하나의 솔라나라

개요

섹션
맨 페이지 이름
검색(S)

zfs(4fs)

zfs(4FS)                         File Systems                         zfs(4FS)

NAME
       zfs - ZFS file system

SYNOPSIS
       #include <libzfs.h>

DESCRIPTION
       ZFS  is  the default root file system in the Oracle Solaris 11 release.
       ZFS is a disk based file system with the following features:

           o      Uses a pooled storage model where whole disks can  be  added
                  to  the pool so that all file systems use storage space from
                  the pool.


           o      A ZFS file system is not tied to a specific  disk  slice  or
                  volume,  so previous tasks, such as repartitioning a disk or
                  unmounting a file system to add disk space, are unnecessary.


           o      ZFS administration is simple and easy with  two  basic  com‐
                  mands: zpool(8) to manage storage pools and zfs(8) to manage
                  file systems. No need exists to learn complex volume manage‐
                  ment interfaces.


           o      All file system operations are copy-on-write transactions so
                  the  on-disk  state  is  always valid. Every block is check‐
                  summed to prevent silent data corruption.  In  a  replicated
                  RAID-Z or mirrored configuration, ZFS detects corrupted data
                  and uses another copy to repair it.


           o      A disk scrubbing feature reads all data to detect latent er‐
                  rors  while  the  errors are still correctable. A scrub tra‐
                  verses the entire storage pool to  read  every  data  block,
                  validates the data against its 256-bit checksum, and repairs
                  the data, if necessary.


           o      ZFS is a 128-bit file system, which means support for 64-bit
                  file  offsets  and timestamps, unlimited links and directory
                  entries, and so on.


           o      ZFS provides snapshots, a read-only point-in-time copy of  a
                  file system and cloning, which provides a writable copy of a
                  snapshot.


           o      ZFS  datasets  can  be encrypted at the filesystem level, as
                  described in zfs_encrypt(8).



       A ZFS storage pool and ZFS file system are created in two steps:

         # zpool create tank mirror c1t0d0 c1t1d0
         # zfs create tank/fs1



       A ZFS file system is mounted automatically when created  and  when  the
       system  is  rebooted  by  an  SMF  service.  No need exists to edit the
       /etc/vfstab file manually. If you need to mount a ZFS file system manu‐
       ally, use syntax similar to the following:

         # zfs mount tank/fs1



       For more information about managing ZFS file systems, see the  Managing
       ZFS File Systems in Oracle Solaris 11.4 book.

ATTRIBUTES
       See attributes(7) for a description of the following attributes:

       tab()  box; cw(2.75i) |cw(2.75i) lw(2.75i) |lw(2.75i) ATTRIBUTE TYPEAT‐
       TRIBUTE VALUE _ Availabilitysystem/file-system/zfs _ Interface Stabili‐
       tyUncommitted


SEE ALSO
       du(1),  attributes(7),  datasets(7),  fsattr(7),   sysattr(7),   df(8),
       zfs(8),    zfs_allow(8),    zfs_encrypt(8),   zfs_share(8),   zpool(8),
       zstreamdump(8)


       Managing ZFS File Systems in Oracle Solaris 11.4

NOTES
       ZFS does not have an fsck-like repair feature because the data  is  al‐
       ways  consistent  on disk. ZFS provides a pool scrubbing operation that
       can find and repair bad data. In addition, because hardware  can  fail,
       ZFS pool recovery features are also available.


       Use the zpool list and zfs list commands to identify ZFS space consump‐
       tion.  A  limitation  of  using the du(1) command to determine ZFS file
       system sizes is that it also reports ZFS  metadata  space  consumption.
       The  df(8)  command  does not account for space that is consumed by ZFS
       snapshots, clones, or quotas.


       A ZFS storage pool that is not used for booting should  be  created  by
       using  whole  disks.  When a ZFS storage pool is created by using whole
       disks, an EFI label is applied to the pool's  disks.  Due  to  a  long-
       standing  boot  limitation,  a ZFS root pool must be created with disks
       that contain a valid SMI (VTOC) label and a disk slice,  usually  slice
       0.

HISTORY
       ZFS was introduced in the Solaris 10 6/06 (Update 2) release.


       Support  for  booting  Solaris off of a ZFS filesystem was added in So‐
       laris 10 8/08 (Update 6).


       For a history of ZFS pool and file system versions, see Appendix A, Or‐
       acle Solaris ZFS Version Descriptions in Managing ZFS File  Systems  in
       Oracle Solaris 11.4.

Oracle Solaris 11.4               17 Mar 2025                         zfs(4FS)
맨 페이지 내용의 저작권은 맨 페이지 작성자에게 있습니다.
RSS ATOM XHTML 5 CSS3