All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wang Yugui <wangyugui@e16-tech.com>
To: linux-nfs@vger.kernel.org
Subject: a 'Text file busy' case caused by nfs server
Date: Sat, 02 Oct 2021 11:14:19 +0800	[thread overview]
Message-ID: <20211002111419.2C83.409509F4@e16-tech.com> (raw)

Hi,

a 'Text file busy' case caused by nfs server.

nfs server: T7610, export /nfs 
	back-end filesystem: btrfs, xfs
nfs client1: T620, mount.nfs4 T7610:/nfs /nfs
nfs client2: T630, mount.nfs4 T7610:/nfs /nfs

linux kernel: 5.10.68, 5.15.0-rc3
	nfs server/client use the same kernel version

The steps to reproduce:
1, nfs client1
	cp /usr/bin/ls /nfs/ls.a
	cat /usr/bin/ls >/nfs/ls.b; chmod a+x /nfs/ls.b
	/nfs/ls.a >/dev/null
	/nfs/ls.b >/dev/null
	It works well.

2, nfs client2 
	/nfs/ls.a >/dev/null
	/nfs/ls.b >/dev/null
	it works well.

3, nfs server
	/nfs/ls.a >/dev/null
		-bash: /nfs/ls.a: Text file busy
		'Text file busy' happen
	/nfs/ls.b >/dev/null
		-bash: /nfs/ls.b: Text file busy
		'Text file busy' happen

	systemctl stop nfs-server.service
	/nfs/ls.a >/dev/null
	/nfs/ls.b >/dev/null
	it works well.

This 'Text file busy' happen when we exec/access the file through the
back-end filesystem directly, not through the nfs client/server.

so this is caused by some file handle(execute attr, and write mode?)
hold by nfs server?

Best Regards
Wang Yugui (wangyugui@e16-tech.com)
2021/10/02



                 reply	other threads:[~2021-10-02  3:14 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=20211002111419.2C83.409509F4@e16-tech.com \
    --to=wangyugui@e16-tech.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.