From: Lutz Vieweg <lvml@5t9.de>
To: linux-btrfs@vger.kernel.org
Subject: fuser fails to list processes that have a directory on a btrfs filesystem as their current working directory
Date: Fri, 26 Jun 2015 18:23:37 +0200 [thread overview]
Message-ID: <mmjua9$bjp$1@ger.gmane.org> (raw)
JFYI: Not a btrfs bug, but a btrfs-specific misbehaviour of "fuser" that
might easily be misinterpreted as a btrfs bug:
http://bugzilla.centos.org/view.php?id=8966
> /usr/sbin/fuser (from psmisc-22.20-8.el7.x86_64) does not list any processes that have a directory on a btrfs file system as their current working directory.
>
> (For file systems other than btrfs, this works.)
> Steps To Reproduce:
> mkdir /some/btrfs/testdir
> cd /some/btrfs/testdir
> fuser -v -m /some/btrfs
>
> This should list your current shell as one of the processes using the /some/btrfs file system, but it doesn't
>
> The same on /some/xfs/testdir works fine.
> This bug is not present in upstream "psmisc" sources as of current master in
> git://git.code.sf.net/p/psmisc/code
>
> An fuser executable compiled from the current upstream sources works fine also for btrfs.
Regards,
Lutz Vieweg
reply other threads:[~2015-06-26 16:23 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='mmjua9$bjp$1@ger.gmane.org' \
--to=lvml@5t9.de \
--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