svcadm(8)을 검색하려면 섹션에서 8 을 선택하고, 맨 페이지 이름에 svcadm을 입력하고 검색을 누른다.
hsfs(4fs)
hsfs(4FS) File Systems hsfs(4FS)
NAME
hsfs - High Sierra & ISO 9660 file system
DESCRIPTION
HSFS is a file system type that allows users to access files on High
Sierra or ISO 9660 format disks or disk images from within the Oracle
Solaris operating system. Once mounted, a HSFS file system provides
standard Oracle Solaris read-only file system operations and semantics,
meaning that you can read and list files in a directory on a High
Sierra or ISO 9660 media and applications can use standard UNIX system
calls on these files and directories.
This file system contains support for Rock Ridge, ISO 9660 Version 2,
and Joliet extensions. These extensions provide support for file names
with a length of at least 207 bytes, but only Rock Ridge extensions
(with the exception of writability and hard links) can provide file
system semantics and file types as they are found in UFS. The presence
of Rock Ridge, ISO 9660 Version 2, and Joliet is autodetected and the
best-suitable available extension is used by the HSFS driver for file
name and attribute lookup.
If your /etc/vfstab file contains a line similar to the following:
/dev/dsk/c0t6d0s0 −/hsfs hsfs -no ro
and /hsfs exists, you can mount an HSFS file system with either of the
following commands:
mount -F hsfs -o ro device-special directory-name
or
mount /hsfs
By default, Rock Ridge extensions are used if available, otherwise ISO
9660 Version 2, then Joliet are used. If none of the extensions are
present HSFS defaults to the standard capabilities of ISO 9660. Since
so-called hybrid disks that contain multiple extensions are possible,
you can use the following mount options to deliberately disable the
search for a specific extension or to force the use of a specific ex‐
tension even if a preferred type is present:
mount -F hsfs -o ro,nrr device-special directory-name
Mount options for selecting ISO 9660 extensions are:
rr Request HSFS to use Rock Ridge extensions, if present. This
is the default behavior and does not need to be explicitly
specified.
nrr Disable detection and use of Rock Ridge extensions, even if
present.
vers2 Request HSFS to use ISO 9660 Version 2 extensions, even if
Rock Ridge is available.
novers2 Disable detection and use of ISO 9660 Version 2 extensions.
joliet Request HSFS to use Joliet extensions, even if Rock Ridge
or ISO 9660 Version 2 extensions are available.
nojoliet Disable detection and use of Joliet extensions.
Files on a High Sierra or ISO 9660 disk have names of the form file‐
name.ext;version, where filename and the optional ext consist of a se‐
quence of uppercase alphanumeric characters (including '_'), while the
version consists of a sequence of digits, representing the version num‐
ber of the file. HSFS converts all the uppercase characters in a file
name to lowercase, and truncates the ';' and version information. If
more than one version of a file is present on the disk, only the file
with the highest version number is accessible.
Conversion of uppercase to lowercase characters may be disabled by us‐
ing the -o nomaplcase option to mount(8). (See mount_hsfs(8)).
If the disk contains Rock Ridge, ISO 9660 version 2, or Joliet exten‐
sions, the file names and directory names may contain any character
supported under UFS. The names may also be uppercase and/or lowercase
and are case sensitive. File name lengths can be as long as those of
UFS.
Files accessed through HSFS have mode 555 (owner, group and world read‐
able and executable), uid 0 and gid 3. If a directory on the disk has
read permission, HSFS grants execute permission to the directory, al‐
lowing it to be searched.
With Rock Ridge extensions, files and directories can have any permis‐
sions that are supported on a UFS file system. However, under all write
permissions, the file system is read-only, with EROFS returned to any
write operations.
Like High Sierra and ISO 9660 disks, HSFS supports only regular files
and directories. A Rock Ridge disk can support regular files, directo‐
ries, and symbolic links, as well as device nodes, such as block, char‐
acter, and FIFO.
EXAMPLES
Example 1 Sample Display of File System Files
If there is a file BIG.BAR on a High Sierra or ISO 9660 format disk it
will show up as big.bar when listed on a HSFS file system.
If there are three files
BAR.BAZ;1
BAR.BAZ;2
and
BAR.BAZ;3
on a High Sierra or ISO 9660 format disk only the file BAR.BAZ;3 will
be accessible. It will be listed as bar.baz.
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/hsfs
SEE ALSO
vfstab(5), mkisofs(8), mount(8), mount_hsfs(8), zonecfg(8)
N. V. Phillips and Sony Corporation, System Description Compact Disc
Digital Audio, ("Red Book").
N. V. Phillips and Sony Corporation, System Description of Compact Disc
Read Only Memory, ("Yellow Book").
IR "Volume and File Structure of CD-ROM for Information Interchange",
ISO 9660:1988(E).
DIAGNOSTICS
hsfs: Warning: the file system...
does not conform to the ISO-9660 spec
The specific reason appears on the following line. You might be at‐
tempting to mount a disk containing a different file system, such
as UFS.
hsfs: Warning: the file system...
contains a file [with an] unsupported type
The hsfs file system does not support the format of some file or
directory on the disk, for example a record structured file.
hsfs: hsnode table full, %d nodes allocated
There are not enough HSFS internal data structure elements to han‐
dle all the files currently open. This problem may be overcome by
adding a line of the form set hsfs:nhsnode=number to the /etc/sys‐
tem system configuration file and rebooting. See system(5).
WARNINGS
Do not physically eject a CD-ROM, DVD, or other media while the device
is still mounted as a HSFS file system.
Under Microsoft operating systems (for which CD-ROM and DVD media are
frequently targeted), files with no extension may be represented either
as:
filename.
or
filename
that is, with or without a trailing period. These names are not equiva‐
lent under UNIX systems. For example, the names:
BAR.
and
BAR
are not names for the same file under the UNIX system. This may cause
confusion if you are consulting documentation for disks originally in‐
tended for Microsoft systems.
Use of the -o notraildot option to mount(8) makes it optional to spec‐
ify the trailing dot. (See mount_hsfs(8)).
NOTES
No translation of any sort is done on the contents of High Sierra or
ISO 9660 format media; only directory and file names are subject to in‐
terpretation by HSFS.
By default, zones can mount this file system.
Oracle Solaris 11.4 14 Jun 2024 hsfs(4FS)