linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Kirby <sim@hostway.ca>
To: linux-nfs@vger.kernel.org
Subject: [3.6-rc3] rdirplus broken? (EBUSY)
Date: Mon, 27 Aug 2012 14:55:10 -0700	[thread overview]
Message-ID: <20120827215510.GL24761@hostway.ca> (raw)

Hello!

Something seems broiken in 3.6-rc[123] which was fine in 3.5 and earlier.
This is a 3.4.1 knfsd server with ext3 and XFS-based NFS exports:

/	192.168.13.0/24(rw,no_root_squash,no_subtree_check,async)
/pics	192.168.13.0/24(rw,no_root_squash,no_subtree_check,async)
/raid	192.168.13.0/24(rw,no_root_squash,no_subtree_check,async)

and a 3.6-rc3 client with this in fstab:

flick:/		/flick		nfs	rw,vers=3
flick:/raid	/flick/raid	nfs	rw,vers=3
flick:/pics	/flick/pics	nfs	rw,vers=3

This seems to fail now as follows:

[sroot@oof:/]# mount flick
[sroot@oof:/]# mount flick/raid
[sroot@oof:/]# mount flick/pics
[sroot@oof:/]# ls -l flick
ls: cannot access flick/pics: Device or resource busy
ls: cannot access flick/raid: Device or resource busy
total 2180
drwxr-xr-x  45 root root    4096 Jun 18 14:19 ./
drwxr-xr-x  58 root root    4096 Jul  3 22:24 ../
...
??????????   ? ?    ?          ?            ? pics
??????????   ? ?    ?          ?            ? raid
...
[sroot@oof:/]# cd flick/pics
flick/pics: Device or resource busy.

These mount points are now stuck and cannot be unmounted until
I reboot (umount -l fails with EBUSY).

If I mount with "nordirplus", I can't seem to get it to break. However,
sometimes it will work regardless. I can bisect this if it would help..

Simon-

             reply	other threads:[~2012-08-27 22:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-27 21:55 Simon Kirby [this message]
2012-09-11 19:25 ` [3.6-rc3] rdirplus broken? (EBUSY) Simon Kirby
2012-09-12 12:16   ` J. Bruce Fields
2012-09-12 21:20     ` Simon Kirby
2012-09-20  0:13       ` Simon Kirby
2012-10-03  1:17         ` Simon Kirby
2013-08-27 15:33           ` J. Bruce Fields

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=20120827215510.GL24761@hostway.ca \
    --to=sim@hostway.ca \
    --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).