From: Martin Papik <mp6058@gmail.com>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com
Subject: Re: XFS filesystem claims to be mounted after a disconnect
Date: Mon, 02 Jun 2014 14:22:15 +0300 [thread overview]
Message-ID: <538C5E67.6090005@gmail.com> (raw)
In-Reply-To: <20140503030221.GJ26353@dastard>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
>> How can I detect this situation? I mean I didn't see anything in
>> /proc/mounts or references to the mount point from /proc/<pid>/*,
>> so I only managed to correct it (chdir elsewhere) by chance on a
>> hunch. Would it not be desirable to know that there's a phantom
>> FS referenced by a number of processes?
>
> lsof.
No good. It happened again and the only thing showing up in lsof
that's even remotely a match is the kernel process associated with the
filesystem instance. "[xfs-data/sde103]". The mountpoint has been
removed by the automatic mounting facility (udev? systemd?). The
device is no longer id /dev (udev?). There's nothing useful in the
output of "find /proc -ls" either.
Any other suggestions to locate the processes that are holding up XFS?
Martin
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBCgAGBQJTjF5dAAoJELsEaSRwbVYrO7IP/016AVgVrdCQ2Vm95hFT5rdu
LH6Sz0mpnZn6mAliNLAa+wFpXArDb6VPyssmomzNLgnpA95qLcfJeBqs1wF88tiA
GO+aFSX3o3npAokbaq1N5c1dKz/g9lpsUPBkmiUEqcPLJMOKdJdSSd4T2nnnKrkD
uDGRmEPZGKXLt75Z0SajnG8oX22bSQdzREn2o4DXZy+RJF9G8wsc490b8TzijDul
AtL/2zlRL45LqbcaNNAOARUiTN4IAxy3xwYRU+xXKhqojPRc0x8K4wrjnGcsiw4x
Cz5HjJ6CdBLmjn69TRf+S5Y/UXtUcyFOIS0XIUwYg6KtwrI1BY+N+GpkSJNG/DcH
0lAN6n7UBTAADw54ZJdYhyw5aUt9OEXdDx2nIuTxq+X/6u4ydEDchJWPvyLG2nv9
Z2vObyh07X9n7h+zknK3yBxlHHNcpi1/d3njxRSa3GKQIPKNbrLNkrFqB4U4+isr
qrcldbcke5d6sUP/VdvjeOGTYWtymx8KqL1MDGPRXruOO1Y6N8DWTbseQCbeoQlS
k0L9md5FsZOPG/aUgXHvD4350sKqYpQk2pgoGW7Ia6F+5nwi1TdSd8R6mlGJ0GyW
hMymVeykhb19mVJzdc7UlmxyAUBUEd2zGEeO0uSenHt19yWc93vfEHG6GCtxFpu6
sxblWr9nRfPi6sOw7oUF
=xn+2
-----END PGP SIGNATURE-----
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2014-06-02 11:22 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-02 13:47 XFS filesystem claims to be mounted after a disconnect Martin Papik
2014-05-02 15:04 ` Eric Sandeen
2014-05-02 15:07 ` Eric Sandeen
2014-05-02 15:44 ` Mark Tinguely
2014-05-02 16:26 ` Martin Papik
2014-05-02 16:44 ` Martin Papik
2014-05-02 16:53 ` Eric Sandeen
2014-05-02 17:54 ` Martin Papik
2014-05-02 18:39 ` Eric Sandeen
2014-05-02 19:07 ` Martin Papik
2014-05-02 19:16 ` Eric Sandeen
2014-05-02 19:29 ` Martin Papik
2014-05-02 23:38 ` Dave Chinner
2014-05-02 23:35 ` Dave Chinner
2014-05-03 0:04 ` Martin Papik
2014-05-03 3:02 ` Dave Chinner
2014-06-02 11:22 ` Martin Papik [this message]
2014-06-02 23:41 ` Dave Chinner
2014-06-03 9:23 ` Martin Papik
2014-06-03 9:55 ` Stefan Ring
2014-06-03 10:48 ` Martin Papik
2014-06-03 21:28 ` Dave Chinner
2014-06-03 22:37 ` Martin Papik
2014-06-05 0:55 ` Dave Chinner
2014-06-05 1:38 ` Martin Papik
2014-06-05 19:39 ` Martin Papik
2014-06-05 22:41 ` Dave Chinner
2014-06-06 0:47 ` Martin Papik
2014-06-03 22:58 ` Martin Papik
2014-06-05 0:08 ` Dave Chinner
2014-06-05 1:07 ` Martin Papik
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=538C5E67.6090005@gmail.com \
--to=mp6058@gmail.com \
--cc=david@fromorbit.com \
--cc=xfs@oss.sgi.com \
/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).