xfs
[Top] [All Lists]

Re: XFS filesystem claims to be mounted after a disconnect

To: Mark Tinguely <tinguely@xxxxxxx>
Subject: Re: XFS filesystem claims to be mounted after a disconnect
From: Martin Papik <mp6058@xxxxxxxxx>
Date: Fri, 02 May 2014 19:26:28 +0300
Cc: xfs@xxxxxxxxxxx
Delivered-to: xfs@xxxxxxxxxxx
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=1FKqs2VZgt+W16QFKn+mr60aVTMNDh/6aAk7IQsrb1I=; b=xRX9kpUP7JGRyTH8P/fx0hP/bux/Vp217tz/kds0P3tw4u5wZn4GEFVCT4WVgrYzg+ tFRvLXkPZOnScv9n7qx6ps3sM2lrK3tq18S9EcheE1GThpeMDTtCi/firc5kTqMBHUPG rlEuGNXG7JqaYKN2AakT+ycJv0aOgj7TtVgAEwWpM3PsQBRsMnOe39VCFBIIxmP0jgaF WcZ963hh6fwXlj3s81hS04pFrXw9pxiycfLhv7jEEVJ8AIW99y63Cac8NnPn2xNRCgPt st20B1jgnA+TNVLN7WKvnyoq8pJUrlKwpuXs5KrnEufINCd5ZMRsoDi4QwkXx8NOv75P XwZA==
In-reply-to: <5363BD62.7050707@xxxxxxx>
References: <5363A1D8.2020402@xxxxxxxxx> <5363B4C9.4000900@xxxxxxxxxxx> <5363BD62.7050707@xxxxxxx>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 05/02/2014 06:44 PM, Mark Tinguely wrote:
> 
> Please do a "ps -ef" before umount to see if the unmount is hung.
> 
> --Mark.

Can't do that any more, I think I've figured out part of the problem
and "resolved" it. There's nothing in "ps -ef" any more, maybe there
was. What seemed to be the problem was that after the device got
disconnected the xfs module was still aware of the mount, even though
I could not see it in /proc/mounts or find any other trace of it
anywhere. After I went through all processes which had a working
directory on the mounted device and changed it to something else the
xfs was able to complete its job. But before then it wasn't allowing
me to do anything.

It's strange that I didn't see xfs mounted (/proc/mounts) or was able
to see any directories (find /proc -type l -ls | grep <mount-dir>)
used. Any idea why this is? Personally I think this is some kind of a
bug. IMHO the xfs driver should be able to inform the user/admin that
the filesystem is still in use.

Below is what appeared in the kernel log after the last process
stopped using the filesystem.

One more question, even though in this case it's moot now, is there
any possibility of telling xfs that device sdd104 is the new sdb104
and tell it to resume writing where it left off? I know there are
risks involved, especially if the USB device device doesn't report
write completion correctly (FUA). But I'd like to know. I believe that
in this case it would have been safe, the filesystem was idle for at
least an hour before the USB disconnected.

Martin

[352505.707397] XFS (sdb104): metadata I/O error: block 0x7470230c
("xlog_iodone") error 19 numblks 64
[352505.707415] XFS (sdb104): xfs_do_force_shutdown(0x2) called from
line 1115 of file
/build/buildd/linux-lts-raring-3.8.0/fs/xfs/xfs_log.c.  Return address
= 0xffffffffa07f4fd1
[352505.707445] XFS (sdb104): Log I/O Error Detected.  Shutting down
filesystem
[352505.707448] XFS (sdb104): Please umount the filesystem and rectify
the problem(s)
[352505.707452] XFS (sdb104): Unable to update superblock counters.
Freespace may not be correct on next mount.
[352505.707463] XFS (sdb104): xfs_log_force: error 5 returned.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBCgAGBQJTY8cfAAoJELsEaSRwbVYrOvoP/jaeYZ59qbqhZCauO6Lhir1i
zWKyfX6R3vNfQPmu0mWeVn/1+uqmufEbtK6gXoROJsta+7YaBDZtnRvuvN5JeE76
GR9ZxS7Jghffj+CbSwoI+q41K6dorD+fTpHm8uUbsYkNq1N4eVfrULP+7PcchjLx
mRDkeffHdESSLF3ZtXhMD/cd7Ok6ILG2PpJ5+yEVu2XKr6QLgOMY8cIUpoDNoKgh
/Mawcex1Bz6oItXPGTWth34harbnbOUOU3gRfd6pbXxvXlFfIihUkg6cpre55U0o
O6H+3KGZj9gGtxP+Atcb1dc4oJaT7J+SL6PTBNmRuP5oqqGWI2YPDiuQX3BnJMZv
VrV78rkJLjMNAmS9c47TkJe9No267dOFK+6pZXj+b3gsmg1/5PrhSJnt5IdVrU6+
kext/CGmtb80Q8O/K6WBb5VmQTD0ZhLV+UPEgllRn8QOu8RfGjp5NgGyeFcqLuWb
YgS2OMp1F+EZ/wnXf0LgQECq0FLj5UBmOmhri3fJ3pHlusOjq/VCNIPcCgTl4YaA
F7eiM/tYy7m42USyyT76N0g1lAqPq26INfFCiXdGdJGUfdHiK8/ucoGIvsEW8lY8
cfZFSOdfpWtqZLytr8tOVA8rs4c+7EZcnuxb9T49qcPvf9/lL2WRSOWShTdCz6cV
sE//zq0BJttX8VDTCp1G
=z+sB
-----END PGP SIGNATURE-----

<Prev in Thread] Current Thread [Next in Thread>