Skip to content

Commit

Permalink
xfs: Update mount options documentation
Browse files Browse the repository at this point in the history
Once inode64 is the default allocation mode now, kernel documentation should be
updated to match this behaviour.

Signed-off-by: Carlos Maiolino <cmaiolino@redhat.com>
Reviewed-by: Mark Tinguely <tinguely@sgi.com>
Signed-off-by: Ben Myers <bpm@sgi.com>
  • Loading branch information
Carlos Maiolino authored and Ben Myers committed Nov 2, 2012
1 parent cd856db commit c99abb8
Showing 1 changed file with 9 additions and 2 deletions.
11 changes: 9 additions & 2 deletions Documentation/filesystems/xfs.txt
Original file line number Diff line number Diff line change
Expand Up @@ -72,8 +72,15 @@ When mounting an XFS filesystem, the following options are accepted.
Indicates that XFS is allowed to create inodes at any location
in the filesystem, including those which will result in inode
numbers occupying more than 32 bits of significance. This is
provided for backwards compatibility, but causes problems for
backup applications that cannot handle large inode numbers.
the default allocation option. Applications which do not handle
inode numbers bigger than 32 bits, should use inode32 option.

inode32
Indicates that XFS is limited to create inodes at locations which
will not result in inode numbers with more than 32 bits of
significance. This is provided for backwards compatibility, since
64 bits inode numbers might cause problems for some applications
that cannot handle large inode numbers.

largeio/nolargeio
If "nolargeio" is specified, the optimal I/O reported in
Expand Down

0 comments on commit c99abb8

Please sign in to comment.