From: Mark Tinguely <tinguely@sgi.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Martin Papik <mp6058@gmail.com>, xfs@oss.sgi.com
Subject: Re: XFS filesystem claims to be mounted after a disconnect
Date: Fri, 02 May 2014 10:44:34 -0500 [thread overview]
Message-ID: <5363BD62.7050707@sgi.com> (raw)
In-Reply-To: <5363B4C9.4000900@sandeen.net>
Please do a "ps -ef" before umount to see if the unmount is hung.
--Mark.
On 05/02/14 10:07, Eric Sandeen wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 5/2/14, 8:47 AM, Martin Papik wrote:
>>
>>
>> I ran into a problem using XFS. The USB device on which I have an XFS
>> file system got disconnected and xfs_repair and xfs_check fail with a
>> message saying the file system is mounted writable. There is no entry
>> in /etc/mtab or /proc/mounts. However I see messages in the kernel log
>> (dmesg) about write failures to the disconnected drive.
>
> platform_check_iswritable() and platform_check_ismounted() in xfsprogs check
> these things.
>
> platform_check_ismounted() does a ustat() of the block device,
> "ustat() returns information about a mounted file system"
> and it knows if it's mounted or not,
> "EINVAL: dev does not refer to a device containing a mounted file system."
>
> so something, somewhere thinks it's mounted. Check /proc/mounts?
>
>> Please let me know what I can do short of zeroing the log, which I
>> believe would result in some data loss.
>
> Hate to say it, but a reboot may be simplest. Zeroing the log won't
> help. OTOH, if you lost USB connectivity, you already lost some data.
>
> - -Eric
>
>
>
>> Martin
>>
<deletes>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2014-05-02 15:44 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 [this message]
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
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=5363BD62.7050707@sgi.com \
--to=tinguely@sgi.com \
--cc=mp6058@gmail.com \
--cc=sandeen@sandeen.net \
--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).