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

개요

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

devchassis(4fs)

devchassis(4FS)                  File Systems                  devchassis(4FS)



NAME
       devchassis - device name file system

DESCRIPTION
       The chassis subdirectory of the /dev  devfs(4FS) file system provides a
       location-oriented name space. The /dev/chassis name space is maintained
       by  the  devchassisd(8)   smf  service.  The /dev/chassis name space is
       structured by chassis, receptacle, and  current  occupant.  Within  the
       chassis/receptacle  name space, the current occupant is maintained as a
       dynamic symlink into the /devices file system.

         /dev/chassis/
           <chassis-name>.<chassis-serial>[[/receptacle-name]*
              [/<occupant-type> -> /devices/...]]



       An empty receptacle is represented as an empty directory.


       If  an  fmadm(8)—managed  <alias-id>   exists,   then   the   <chassis-
       name>.<chassis-serial>  is  replaced by a managed <alias-id>. A managed
       <alias-id> can establish the  physical  location  of  chassis,  like  a
       building, lab, rack, and chassis U-number range inside the rack.


       There  is  always  one  well-known  <alias-id> associated with internal
       locations: SYS. This <alias-id> cannot be modified.


       A <receptacle-name> is associated with chassis silk-screen labeling  of
       receptacles  (like  disk  bays). Multiple <receptacle-name> directories
       can be used before coming to an occupant symlink.


       The /dev/chassis name space allows you to administer the machine  based
       on physical location.

         # format /dev/chassis/SYS/HD0/disk

         # zpool create tank mirror \
                 /dev/chassis/RACK29.U01-04/DISK_00/disk \
                 /dev/chassis/RACK29.U05-08/DISK_00/disk



       fmd(8) machine topology understanding is required to drive the creation
       and maintenance of the /dev/chassis name space. If  this  understanding
       is  lacking,  the  /dev/chassis  name space will be lacking. fmd(8) and
       devchassisd(8)  operation  is  coordinated  using   the   contents   of
       /etc/dev/cro_db.  This  same  data  file is also used by the croinfo(8)
       utility.

FILES
       /dev/chassis       Directory under the /dev  file  system  mount  point
                          that  provides,  when  possible, a location-oriented
                          device name space.


       /etc/dev/cro_db    Data file created by fmd(8) used to obtain  informa‐
                          tion about chassis, receptacles, and occupants.


SEE ALSO
       devfs(4FS), devices(5), croinfo(8), devchassisd(8), fmadm(8), fmd(8)

NOTES
       To  prevent  stale links, the entire /dev/chassis name space is removed
       during each boot and reestablished when both fmd(8) and  devchassisd(8)
       are  running.  If  devchassisd(8) is not running, the /dev/chassis name
       space does not exist.


       Gaps in fmd(8) topology representation result in gaps in the /dev/chas‐
       sis name space.



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