From: Namjae Jeon <linkinjeon@gmail.com>
To: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
Cc: akpm@linux-foundation.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org,
Namjae Jeon <namjae.jeon@samsung.com>,
Ravishankar N <ravi.n1@samsung.com>,
Amit Sahrawat <a.sahrawat@samsung.com>
Subject: Re: [PATCH v5 8/8] Documentation: update nfs option in filesystem/vfat.txt
Date: Tue, 4 Dec 2012 15:24:39 +0900 [thread overview]
Message-ID: <CAKYAXd9oqwcCVJkhO_bdfwUEuccWwE1NzmEtdpOeBPvV2JCHXw@mail.gmail.com> (raw)
In-Reply-To: <87d2yr5um2.fsf@devron.myhome.or.jp>
2012/12/3, OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>:
> Namjae Jeon <linkinjeon@gmail.com> writes:
>
>> From: Namjae Jeon <namjae.jeon@samsung.com>
>>
>> update nfs option in filesystem/vfat.txt
>>
>> Signed-off-by: Namjae Jeon <namjae.jeon@samsung.com>
>> Signed-off-by: Ravishankar N <ravi.n1@samsung.com>
>> Signed-off-by: Amit Sahrawat <a.sahrawat@samsung.com>
>> ---
>> Documentation/filesystems/vfat.txt | 23 ++++++++++++++++++-----
>> 1 file changed, 18 insertions(+), 5 deletions(-)
>>
>> diff --git a/Documentation/filesystems/vfat.txt
>> b/Documentation/filesystems/vfat.txt
>> index d230dd9..f663c70 100644
>> --- a/Documentation/filesystems/vfat.txt
>> +++ b/Documentation/filesystems/vfat.txt
>> @@ -150,13 +150,26 @@ discard -- If set, issues discard/TRIM
>> commands to the block
>> device when blocks are freed. This is useful for SSD devices
>> and sparse/thinly-provisoned LUNs.
>>
>> -nfs -- This option maintains an index (cache) of directory
>> - inodes by i_logstart which is used by the nfs-related code to
>> - improve look-ups.
>> -
>> - Enable this only if you want to export the FAT filesystem
>> +nfs= stale_rw|nostale_ro
>> + -- Enable this only if you want to export the FAT filesystem
>> over NFS
>>
>> + stale_rw:This option maintains an index (cache) of directory
>> + inodes by i_logstart which is used by the nfs-related code to
>> + improve look-ups.Full file operations (read/write) over NFS is
>> supported
>> + but with cache eviction at NFS server, this could result in ESTALE
>> issues.
>> +
>> + nostale_ro:This option bases the inode number and filehandle on the
>> on-disk
>> + location of a file in the MS-DOS directory entry.This ensures that
>> ESTALE
>> + will not be returned after a file is evicted from the inode cache.
>> However,
>> + it means that operations such as rename, create and unlink could
>> cause
>> + filehandles that previously pointed at one file to point at a
>> different file,
>> + potentially causing data corruption. For this reason, this option also
>> mounts
>> + the filesystem readonly.
>> +
>> + To maintain backward compatibility, '-o nfs' is also accepted,
>> defaulting to
>> + stale_rw
>
> Please add whitespace after ":" and ".". And please care 80 columns.
Okay, I will fix it.
Thanks.
> --
> OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
>
prev parent reply other threads:[~2012-12-04 6:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-21 13:25 [PATCH v5 8/8] Documentation: update nfs option in filesystem/vfat.txt Namjae Jeon
2012-12-03 9:54 ` OGAWA Hirofumi
2012-12-04 6:24 ` Namjae Jeon [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAKYAXd9oqwcCVJkhO_bdfwUEuccWwE1NzmEtdpOeBPvV2JCHXw@mail.gmail.com \
--to=linkinjeon@gmail.com \
--cc=a.sahrawat@samsung.com \
--cc=akpm@linux-foundation.org \
--cc=hirofumi@mail.parknet.co.jp \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=namjae.jeon@samsung.com \
--cc=ravi.n1@samsung.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).