linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ulrich Gemkow <ulrich.gemkow@ikr.uni-stuttgart.de>
To: linux-nfs@vger.kernel.org
Subject: NFSv3-mounting of BTRFS-FS fails, gives ESTALE
Date: Sat, 23 May 2015 19:58:11 +0200	[thread overview]
Message-ID: <201505231958.13619.ulrich.gemkow@ikr.uni-stuttgart.de> (raw)

Hello,

[sent this to linux-btrfs mailing list but got no answer,
maybe this is the better list].

we export a BTRFS-filesystem via NFSv3 and tried to mount
this share on a client (also NFSv3). The mount program on the
client hangs and the mount fails.

Server and client use vanilla Linux kernel 4.0.3, the distro
is Ubuntu 14.04.02, btrfs-progs are version 4.0.

Exporting of other filesystems (ext4) and mounting them in
the exactly same setup works, so this seems to be BTRFS-related.

strace-ing the mount-call on the client shows that the mount
syscall returns ESTALE errors and mount enters a loop which
leads to the hang of the mount-program in user land.

I applied the patch of Neil Brown (which should help with
NFS v2) in [1]. The behaviour without and with this patch
is the same.

This seems to be a regression because from the lists I
saw that NFS-exporting of BTRFS is supposed to work
(but NFSv3 is not explicitely mentioned there).

Is this a bug? I am more than willing to help with more
diagnosis.

Thank you and best regards

Ulrich



[1] https://lkml.org/lkml/2015/5/7/1013

-- 
|-----------------------------------------------------------------------
| Ulrich Gemkow
| University of Stuttgart
| Institute of Communication Networks and Computer Engineering (IKR)
|-----------------------------------------------------------------------

                 reply	other threads:[~2015-05-23 18:03 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=201505231958.13619.ulrich.gemkow@ikr.uni-stuttgart.de \
    --to=ulrich.gemkow@ikr.uni-stuttgart.de \
    --cc=linux-nfs@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;
as well as URLs for NNTP newsgroup(s).