public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Balaji Rao <balajirrao@gmail.com>
Cc: linux-btrfs@vger.kernel.org, Chris Mason <chris.mason@oracle.com>
Subject: Re: [PATCH] NFS support for btrfs - v2
Date: Sun, 17 Aug 2008 12:53:22 +0100	[thread overview]
Message-ID: <1218974002.3184.278.camel@pmac.infradead.org> (raw)
In-Reply-To: <200807210201.56690.balajirrao@gmail.com>

On Mon, 2008-07-21 at 02:01 +0530, Balaji Rao wrote:
> Here's an implementation of NFS support for btrfs. It does not work in
> one particular case as described in 
> http://www.mail-archive.com/linux-btrfs@vger.kernel.org/msg00298.html.

I can't get it to work properly. The simple case of exporting and using
a file system works -- but that doesn't exercise the get_parent() or
dentry_to_fh() code paths. To test those, you need to clear the server's
dcache completely -- I prefer just rebooting the server.

Note that the first problem you'll hit is the lack of stable fsid --
because btrfs uses an anonymous superblock, it might cause stale file
handles after a reboot, unless your test setup mounts exactly the same
anonymous file systems each time. That bit me when I context switched
from something else and had debugfs mounted before btrfs, then rebooted
and didn't mount debugfs first. I'll deal with the fsid problem
separately; just be aware of it and avoid it for now.

The second problem is that btrfs_fh_to_dentry() fails -- it seems we
need to set the key type BTRFS_INODE_ITEM_KEY in btrfs_get_dentry(),
rather than BTRFS_INODE_REF_KEY. I still haven't learned enough to know
precisely what the implications of that are -- but unless I make that
change, btrfs_lookup_inode() fails and btrfs_read_locked_inode() marks
the resulting inode as bad.

You can test that by mounting the exported file system, then rebooting
the server, then running 'ls' in the NFS-mounted file system.

My next test was to make a deep directory path: mkdir -p a/b/c/d/e/f/g
and then change directory into it. Again reboot the server and run 'ls'.
This time, I see 'ls: cannot open directory .'. In this csse, it seems
to be because btrfs_get_parent() is failing. In my case, it seems to be
because the 'if (slot >= nritems)' check is triggering -- both are set
to 14. I'm now trying to work out precisely what that means...

-- 
David Woodhouse                            Open Source Technology Centre
David.Woodhouse@intel.com                              Intel Corporation




  reply	other threads:[~2008-08-17 11:53 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-20 20:31 [PATCH] NFS support for btrfs - v2 Balaji Rao
2008-08-17 11:53 ` David Woodhouse [this message]
2008-08-17 12:51   ` Balaji Rao
2008-08-17 12:56     ` David Woodhouse
2008-08-17 13:24       ` Balaji Rao
2008-08-17 13:30         ` David Woodhouse
2008-08-17 14:17           ` David Woodhouse
2008-08-17 16:10             ` [PATCH] rewrite btrfs_readdir() David Woodhouse
2008-08-18 18:46               ` Chris Mason
2008-08-18 19:08                 ` David Woodhouse
2008-08-18 19:24                   ` Chris Mason
2008-08-18 19:32                     ` David Woodhouse
2008-08-17 13:40         ` [PATCH] NFS support for btrfs - v2 David Woodhouse
2008-08-18 19:23           ` Chris Mason
2008-08-18 19:33             ` David Woodhouse
2008-08-18 19:47               ` Chris Mason
2008-08-18 20:20                 ` David Woodhouse
2008-08-18 20:32                   ` Chris Mason
2008-08-18 21:52                     ` David Woodhouse
2008-08-19 11:54                       ` Chris Mason
2008-08-19 14:49                         ` David Woodhouse
2008-08-19 21:34                           ` David Woodhouse
2008-08-19  0:16                   ` Christoph Hellwig
2008-08-19  0:21                     ` David Woodhouse
2008-08-18 11:51     ` David Woodhouse
2008-08-18 12:10       ` David Woodhouse
2008-08-18 19:15         ` Chris Mason

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=1218974002.3184.278.camel@pmac.infradead.org \
    --to=dwmw2@infradead.org \
    --cc=balajirrao@gmail.com \
    --cc=chris.mason@oracle.com \
    --cc=linux-btrfs@vger.kernel.org \
    /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