Add entity for reiserfs(5).
Fix filesystems to file systems. Editorial review of Linux File Systems. Sponsored by: iXsystems
This commit is contained in:
parent
c4f2efbabf
commit
cee3cf9230
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=44471
2 changed files with 38 additions and 51 deletions
|
@ -552,7 +552,7 @@ errors: No known data errors</screen>
|
|||
|
||||
<para>Quotas limit the amount of space that a dataset and its
|
||||
descendants can consume, and enforce a limit on the amount
|
||||
of space used by filesystems and snapshots for the
|
||||
of space used by file systems and snapshots for the
|
||||
descendants. Quotas are useful to limit the amount of space
|
||||
a particular user can use.</para>
|
||||
|
||||
|
@ -648,7 +648,7 @@ errors: No known data errors</screen>
|
|||
quotas for all groups.</para>
|
||||
|
||||
<para>To display the amount of space consumed by each user on
|
||||
the specified filesystem or snapshot, along with any
|
||||
the specified file system or snapshot, along with any
|
||||
specified quotas, use <command>zfs userspace</command>.
|
||||
For group information, use <command>zfs
|
||||
groupspace</command>. For more information about
|
||||
|
@ -721,15 +721,16 @@ errors: No known data errors</screen>
|
|||
</sect1>
|
||||
|
||||
<sect1 xml:id="filesystems-linux">
|
||||
<title>&linux; Filesystems</title>
|
||||
<title>&linux; File Systems</title>
|
||||
|
||||
<para>This section describes some of the &linux; filesystems
|
||||
supported by &os;.</para>
|
||||
<para>&os; provides built-in support for several &linux; file
|
||||
systems. This section demonstrates how to load support for and
|
||||
how to mount the supported &linux; file systems.</para>
|
||||
|
||||
<sect2>
|
||||
<title><acronym>ext2</acronym></title>
|
||||
|
||||
<para>The &man.ext2fs.5; file system kernel implementation has
|
||||
<para>Kernel support for ext2 file systems has
|
||||
been available since &os; 2.2. In &os; 8.x and
|
||||
earlier, the code is licensed under the
|
||||
<acronym>GPL</acronym>. Since &os; 9.0, the code has
|
||||
|
@ -737,85 +738,70 @@ errors: No known data errors</screen>
|
|||
licensed.</para>
|
||||
|
||||
<para>The &man.ext2fs.5; driver allows the &os; kernel to both
|
||||
read and write to <acronym>ext2</acronym> file systems.</para>
|
||||
read and write to ext2 file systems.</para>
|
||||
|
||||
<para>To access an <acronym>ext2</acronym> file system, first
|
||||
<note>
|
||||
<para>
|
||||
This driver can also be used to access ext3 and ext4 file
|
||||
systems. However, ext3 journaling, extended attributes, and
|
||||
inodes greater than 128-bytes are not supported. Support
|
||||
for ext4 is read-only.</para>
|
||||
</note>
|
||||
|
||||
<para>To access an ext file system, first
|
||||
load the kernel loadable module:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>kldload ext2fs</userinput></screen>
|
||||
|
||||
<para>Then, to mount an &man.ext2fs.5; volume located on
|
||||
<filename>/dev/ad1s1</filename>:</para>
|
||||
<para>Then, mount the ext volume by specifying its &os;
|
||||
partition name and an existing mount point. This example
|
||||
mounts <filename>/dev/ad1s1</filename> on
|
||||
<filename>/mnt</filename>:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>mount -t ext2fs /dev/ad1s1 /mnt</userinput></screen>
|
||||
<screen>&prompt.root; <userinput>mount -t ext2fs <replaceable>/dev/ad1s1</replaceable> <replaceable>/mnt</replaceable></userinput></screen>
|
||||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>XFS</title>
|
||||
|
||||
<para><acronym>XFS</acronym> was originally written by
|
||||
<acronym>SGI</acronym> for the <acronym>IRIX</acronym>
|
||||
operating system and was then ported to &linux; and
|
||||
released under the <acronym>GPL</acronym>. See
|
||||
<link xlink:href="http://oss.sgi.com/projects/xfs">this page</link>
|
||||
for more details. The &os; port was started by Russel
|
||||
Cattelan, &a.kan.email;, and &a.rodrigc.email;.</para>
|
||||
<para>&os; provides read-only support for <acronym>XFS</acronym>
|
||||
file systems.</para>
|
||||
|
||||
<para>To load <acronym>XFS</acronym> as a kernel-loadable
|
||||
module:</para>
|
||||
<para>To load the &man.xfs.5; driver:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>kldload xfs</userinput></screen>
|
||||
|
||||
<para>The &man.xfs.5; driver lets the &os; kernel access XFS
|
||||
filesystems. However, only read-only access is supported and
|
||||
writing to a volume is not possible.</para>
|
||||
|
||||
<para>To mount a &man.xfs.5; volume located on
|
||||
<para>To mount an <acronym>XFS</acronym> volume located on
|
||||
<filename>/dev/ad1s1</filename>:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>mount -t xfs /dev/ad1s1 /mnt</userinput></screen>
|
||||
<screen>&prompt.root; <userinput>mount -t xfs <replaceable>/dev/ad1s1</replaceable> <replaceable>/mnt</replaceable></userinput></screen>
|
||||
|
||||
<para>The <package>sysutils/xfsprogs</package>
|
||||
port includes the <command>mkfs.xfs</command> which enables
|
||||
the creation of <acronym>XFS</acronym> filesystems, plus
|
||||
utilities for analyzing and repairing them.</para>
|
||||
|
||||
<para>The <literal>-p</literal> flag to
|
||||
<command>mkfs.xfs</command> can be used to create an
|
||||
&man.xfs.5; filesystem which is populated with files and other
|
||||
metadata. This can be used to quickly create a read-only
|
||||
filesystem which can be tested on &os;.</para>
|
||||
<para>The <package>sysutils/xfsprogs</package> package or
|
||||
port includes <command>mkfs.xfs</command>, which enables
|
||||
the creation of read-only <acronym>XFS</acronym> file systems
|
||||
for testing purposes. Additional
|
||||
utilities are included for analyzing and repairing
|
||||
<acronym>XFS</acronym> file systems.</para>
|
||||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>ReiserFS</title>
|
||||
|
||||
<para>The Reiser file system, ReiserFS, was ported to
|
||||
&os; by &a.dumbbell.email;, and has been released under the
|
||||
<acronym>GPL</acronym> .</para>
|
||||
<para>&os; provides read-only support for The Reiser file
|
||||
system, ReiserFS.</para>
|
||||
|
||||
<para>The ReiserFS driver permits the &os; kernel to access
|
||||
ReiserFS file systems and read their contents, but not
|
||||
write to them.</para>
|
||||
|
||||
<para>First, the kernel-loadable module needs to be
|
||||
loaded:</para>
|
||||
<para>To load the &man.reiserfs.5; driver:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>kldload reiserfs</userinput></screen>
|
||||
|
||||
<para>Then, to mount a ReiserFS volume located on
|
||||
<filename>/dev/ad1s1</filename>:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>mount -t reiserfs /dev/ad1s1 /mnt</userinput></screen>
|
||||
<screen>&prompt.root; <userinput>mount -t reiserfs <replaceable>/dev/ad1s1</replaceable> <replaceable>/mnt</replaceable></userinput></screen>
|
||||
</sect2>
|
||||
</sect1>
|
||||
|
||||
<!--
|
||||
XXXTR: stub sections (added later, as needed, as desire,
|
||||
after I get opinions from -doc people):
|
||||
|
||||
Still need to discuss native and foreign file systems.
|
||||
|
||||
<sect1>
|
||||
<title>Device File System</title>
|
||||
</sect1>
|
||||
|
|
|
@ -4115,6 +4115,7 @@
|
|||
<!ENTITY man.ranlib.5 "<citerefentry xmlns='http://docbook.org/ns/docbook'><refentrytitle>ranlib</refentrytitle><manvolnum>5</manvolnum></citerefentry>">
|
||||
<!ENTITY man.rc.conf.5 "<citerefentry xmlns='http://docbook.org/ns/docbook'><refentrytitle>rc.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry>">
|
||||
<!ENTITY man.rcsfile.5 "<citerefentry xmlns='http://docbook.org/ns/docbook'><refentrytitle>rcsfile</refentrytitle><manvolnum>5</manvolnum></citerefentry>">
|
||||
<!ENTITY man.reiserfs.5 "<citerefentry xmlns='http://docbook.org/ns/docbook'><refentrytitle>reiserfs</refentrytitle><manvolnum>5</manvolnum></citerefentry>">
|
||||
<!ENTITY man.remote.5 "<citerefentry xmlns='http://docbook.org/ns/docbook'><refentrytitle>remote</refentrytitle><manvolnum>5</manvolnum></citerefentry>">
|
||||
<!ENTITY man.resolv.conf.5 "<citerefentry xmlns='http://docbook.org/ns/docbook'><refentrytitle>resolv.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry>">
|
||||
<!ENTITY man.resolver.5 "<citerefentry xmlns='http://docbook.org/ns/docbook'><refentrytitle>resolver</refentrytitle><manvolnum>5</manvolnum></citerefentry>">
|
||||
|
|
Loading…
Reference in a new issue