All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Papik <mp6058@gmail.com>
To: xfs@oss.sgi.com
Subject: XFS filesystem claims to be mounted after a disconnect
Date: Fri, 02 May 2014 16:47:04 +0300	[thread overview]
Message-ID: <5363A1D8.2020402@gmail.com> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512



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.


Please let me know what I can do short of zeroing the log, which I
believe would result in some data loss.

Martin


# xfs_repair /dev/sdd104
xfs_repair: /dev/sdd104 contains a mounted filesystem

fatal error -- couldn't initialize XFS library
# xfs_check /dev/sdd104
xfs_check: /dev/sdd104 contains a mounted and writable filesystem

fatal error -- couldn't initialize XFS library


partial dmesg output:

[346220.652432] Buffer I/O error on device sdb104, logical block
3906961152
[346220.652440] Buffer I/O error on device sdb104, logical block
3906961153
[346220.652443] Buffer I/O error on device sdb104, logical block
3906961154
[346220.652446] Buffer I/O error on device sdb104, logical block
3906961155
[346220.652449] Buffer I/O error on device sdb104, logical block
3906961156
[346220.652452] Buffer I/O error on device sdb104, logical block
3906961157
[346220.652455] Buffer I/O error on device sdb104, logical block
3906961158
[346220.652459] Buffer I/O error on device sdb104, logical block
3906961159
[346220.652473] Buffer I/O error on device sdb104, logical block
3906961352
[346220.652476] Buffer I/O error on device sdb104, logical block
3906961353
[346554.917502] quiet_error: 1924 callbacks suppressed
[346554.917510] Buffer I/O error on device sdb104, logical block 0
[346554.917518] Buffer I/O error on device sdb104, logical block 1
[346554.917522] Buffer I/O error on device sdb104, logical block 2
[346554.917525] Buffer I/O error on device sdb104, logical block 3
[346554.917529] Buffer I/O error on device sdb104, logical block 4
[346554.917532] Buffer I/O error on device sdb104, logical block 5
[346554.917536] Buffer I/O error on device sdb104, logical block 6
[346554.917539] Buffer I/O error on device sdb104, logical block 7
[346554.951030] Buffer I/O error on device sdb104, logical block
3906961152
[346554.951051] Buffer I/O error on device sdb104, logical block
3906961153

The current disk is /dev/sdd104 and sdb104 doesn't appear anywhere in
the kernel, despite the messages in dmesg.

# cat /proc/partitions
major minor  #blocks  name

   7        0     131072 loop0
   8        0  488386584 sda
   8        1     204800 sda1
   8        2  104384512 sda2
   8        3          1 sda3
   8        4   15471640 sda4
   8        5   30403584 sda5
   8        6     104391 sda6
   8        7  117187584 sda7
  11        0    1048575 sr0
   8       64 1953481728 sde
   8       75 1953480687 sde11
   8       80  312571224 sdf
   8       48 1953481728 sdd
 259        0 1953480687 sdd104


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

iQIcBAEBCgAGBQJTY6GrAAoJELsEaSRwbVYrTwcQAKNYds36X3wUssi1Zbcn+AXi
UJuvx3QYVY6OF7huitlM/m9Ih9gOfFVQEbVvHEqoHXwEx2y6a5/KzCGoSHSXsxUj
KLFgXxgbdTsGEIePfW3R1v3JyY9TmuDx/U39gMPuM2nRy2sFCXc6HpBJFfUJf4uo
GY1y+w+LzFE2bTQYG+F0sWhUnBWq9klGoTsZYsghEpLNnaLgdrHLqpJkgb8RIy2C
O1sCbRD+Crs/a5W2ijCNOTchU1yV8oJOK4D7HkyyFUMqG2XRUkeRMntA93r9byo9
kYlzNJUbSPB2onzRacq5ygMKp816+e7sQaBFuYTZQB6IQRk3NGf6PWKwLBO+pY3d
2lqbjkt12jtuth6xlxiUHps83D8X/tEWz0a8oQMfjIyAoZZJTCZdg/Hd9HyVUg5A
mWPu4UpvXDsTCY/rt3owJrL+VCCxPXumpgAnKc7EiMjbjZBMDIK9YwvEpWSrtt8H
Ak11w4bdCoML/oDIK8LV/SHGinSHAC/sOaEBSX5IfvQeIeohoK7cN400jYFzkMgu
p5ZsiEtRHwl2tnZ9bgm52TYUH6KMI1qGuTPJoOWfKe7XgXAzmx+ppnzuUtDGKi1y
NXNHuD18J8InFCI08mIKaCkIg9yA/6c7Mhq2EaS+QeURcUNyUsi3J2Q7+wv34JJ0
i8TsGzSUYkqrWwDLa1+c
=gR4I
-----END PGP SIGNATURE-----

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

             reply	other threads:[~2014-05-02 13:47 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-02 13:47 Martin Papik [this message]
2014-05-02 15:04 ` XFS filesystem claims to be mounted after a disconnect 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
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=5363A1D8.2020402@gmail.com \
    --to=mp6058@gmail.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 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.