From: "Steven J. Magnani" <steve@digidescorp.com>
To: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
Cc: Namjae Jeon <linkinjeon@gmail.com>,
Al Viro <viro@zeniv.linux.org.uk>,
akpm@linux-foundation.org, bfields@fieldses.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 v2 1/5] fat: allocate persistent inode numbers
Date: Mon, 10 Sep 2012 07:28:31 -0500 [thread overview]
Message-ID: <1347280111.2101.8.camel@iscandar.digidescorp.com> (raw)
In-Reply-To: <87oblfpmnb.fsf@devron.myhome.or.jp>
On Sun, 2012-09-09 at 18:32 +0900, OGAWA Hirofumi wrote:
> What is your use case?
What Neil Brown refers to as a "general file access protocol" -
basically making a flash disk available to a small embedded network for
random-access file I/O.
The flash disk is required to interoperate with Windoze, which forces us
into VFAT-backed NFS.
> I'm assuming current NFS support of FAT is still unstable behavior even with your
> patches. Is this true?
We use lookupcache=none, which I thought had stabilized things. Based on
what Namjae has found with ESTALE on rename/drop_caches I guess there is
a hole.
------------------------------------------------------------------------
Steven J. Magnani "I claim this network for MARS!
www.digidescorp.com Earthling, return my space modulator!"
#include <standard.disclaimer>
prev parent reply other threads:[~2012-09-10 12:28 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-04 15:57 Namjae Jeon
2012-09-04 16:17 ` Al Viro
2012-09-05 14:08 ` Namjae Jeon
2012-09-05 14:56 ` OGAWA Hirofumi
2012-09-06 6:46 ` Namjae Jeon
2012-09-06 12:19 ` OGAWA Hirofumi
2012-09-06 13:39 ` Namjae Jeon
2012-09-07 7:01 ` Namjae Jeon
2012-09-07 12:15 ` Steven J. Magnani
2012-09-09 9:32 ` OGAWA Hirofumi
2012-09-09 11:29 ` OGAWA Hirofumi
2012-09-10 12:03 ` Namjae Jeon
2012-09-10 14:00 ` OGAWA Hirofumi
2012-09-11 12:00 ` Namjae Jeon
2012-09-11 12:31 ` OGAWA Hirofumi
2012-09-11 15:13 ` Namjae Jeon
2012-09-11 15:47 ` OGAWA Hirofumi
2012-09-12 14:12 ` Namjae Jeon
2012-09-12 14:32 ` J. Bruce Fields
2012-09-12 17:03 ` OGAWA Hirofumi
2012-09-12 17:11 ` J. Bruce Fields
2012-09-12 17:38 ` OGAWA Hirofumi
2012-09-12 17:45 ` J. Bruce Fields
2012-09-12 18:49 ` OGAWA Hirofumi
2012-09-13 8:11 ` Namjae Jeon
2012-09-13 8:33 ` OGAWA Hirofumi
2012-09-13 11:20 ` J. Bruce Fields
2012-09-13 12:17 ` OGAWA Hirofumi
2012-09-13 14:24 ` Namjae Jeon
2012-09-13 14:46 ` J. Bruce Fields
2012-09-13 15:34 ` OGAWA Hirofumi
2012-09-14 8:51 ` Namjae Jeon
2012-09-10 12:28 ` Steven J. Magnani [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=1347280111.2101.8.camel@iscandar.digidescorp.com \
--to=steve@digidescorp.com \
--cc=a.sahrawat@samsung.com \
--cc=akpm@linux-foundation.org \
--cc=bfields@fieldses.org \
--cc=hirofumi@mail.parknet.co.jp \
--cc=linkinjeon@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=namjae.jeon@samsung.com \
--cc=ravi.n1@samsung.com \
--cc=viro@zeniv.linux.org.uk \
/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
all inboxes | Powered by JetHome®