From: Jaegeuk Kim <jaegeuk.kim@samsung.com>
To: Namjae Jeon <linkinjeon@gmail.com>
Cc: linux-fsdevel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
Namjae Jeon <namjae.jeon@samsung.com>,
Amit Sahrawat <a.sahrawat@samsung.com>
Subject: Re: [PATCH 5/5] f2fs: Fix for parent inode information during server cache eviction
Date: Mon, 10 Dec 2012 09:43:55 +0900 [thread overview]
Message-ID: <1355100235.7291.52.camel@kjgkr> (raw)
In-Reply-To: <1354946143-7730-1-git-send-email-linkinjeon@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 822 bytes --]
2012-12-08 (토), 14:55 +0900, Namjae Jeon:
> From: Namjae Jeon <namjae.jeon@samsung.com>
>
> Test Case:
> [NFS Client]
> ls -lR .
>
> [NFS Server]
> while [ 1 ]
> do
> echo 3 > /proc/sys/vm/drop_caches
> done
>
> Error: "No such file or directory"
>
> When cache is dropped at the server, it results in lookup failure at the
> NFS client. Even though the file exists. Looking at the code to rebuild
> the inode in case of cache eviction. It tries to initiate a lookup operation
> for ".." to get the parent information using the on-disk inode number.
>
Could you describe why this patch resolves that bug?
Before applying this, we need to figure out why that bug is occurred.
IMO, from the viewpoint of functionality, ".." resolution should work
too.
Thanks,
--
Jaegeuk Kim
Samsung
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-12-10 0:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-08 5:55 [PATCH 5/5] f2fs: Fix for parent inode information during server cache eviction Namjae Jeon
2012-12-10 0:43 ` Jaegeuk Kim [this message]
2012-12-10 3:40 ` Namjae Jeon
2012-12-10 4:37 ` Jaegeuk Kim
2012-12-10 5:25 ` Namjae Jeon
2012-12-10 7:00 ` Jaegeuk Kim
2012-12-10 7:11 ` Namjae Jeon
2012-12-10 7:19 ` Jaegeuk Kim
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=1355100235.7291.52.camel@kjgkr \
--to=jaegeuk.kim@samsung.com \
--cc=a.sahrawat@samsung.com \
--cc=linkinjeon@gmail.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=namjae.jeon@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).