From 09614331ddef07b3b73a6ddef8f1b8bc95655bff Mon Sep 17 00:00:00 2001 From: Carlos Maiolino Date: Thu, 18 Oct 2012 12:28:58 -0300 Subject: [PATCH] --- yaml --- r: 339391 b: refs/heads/master c: c99abb8f560798625323c7b21d5636259017825d h: refs/heads/master i: 339389: a5fbfc7004d76b217a672591c46633a7f3f06304 339387: 3a4463405f558af30e6039c2b7f5676df6dfba49 339383: 16ec45a897d267c3307d79f94ff299287b87c1a0 339375: ec947125fcb7cb1aded3ab608b9a9255a433d256 339359: 674ebc62930dd5fbb99935ce9185f33e17ca220e 339327: 03f752cf0bbd1a86c612368f05a76eb40cb19f87 v: v3 --- [refs] | 2 +- trunk/Documentation/filesystems/xfs.txt | 11 +++++++++-- 2 files changed, 10 insertions(+), 3 deletions(-) diff --git a/[refs] b/[refs] index 94e0a9cb88c1..09e19a52021d 100644 --- a/[refs] +++ b/[refs] @@ -1,2 +1,2 @@ --- -refs/heads/master: cd856db69c88db438215244571957d812bdc6813 +refs/heads/master: c99abb8f560798625323c7b21d5636259017825d diff --git a/trunk/Documentation/filesystems/xfs.txt b/trunk/Documentation/filesystems/xfs.txt index 3fc0c31a6f5d..17187750270a 100644 --- a/trunk/Documentation/filesystems/xfs.txt +++ b/trunk/Documentation/filesystems/xfs.txt @@ -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