public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: linux-xfs@vger.kernel.org
Subject: Shutdown preventing umount
Date: Sat, 14 Mar 2020 06:31:10 -0700	[thread overview]
Message-ID: <20200314133107.4rv25sp4bvhbjjsx@two.firstfloor.org> (raw)


Hi,

I had a cable problem on a USB connected XFS file system, triggering 
some IO errors, and the result was that any access to the mount point
resulted in EIO. This prevented unmounting the file system to recover
from the problem. 

I also tried xfs_io with shutdown -f, but it had the same problem
because xfs_io couldn't access anything on the file system.

How is that supposed to work? Having to reboot just to recover
from IO errors doesn't seem to be very available.

I don't think shutdown should prevent unmounting.

From googling I found some old RHEL bugzilla that such a problem
was fixed in some RHEL release. Is that a regression? 

This was on a 5.4.10 kernel.

I got lots of:

 XFS (...): metadata I/O error in "xfs_trans_read_buf_map" at daddr
 0x4a620288 len 8 error 5

Then some

XFS (...): writeback error on sector 7372099184

And finally:

XFS (...): log I/O error -5
 XFS (...): xfs_do_force_shutdown(0x2)
called from line 1250 of file fs/xfs/xfs_log.c. Return address =
00000000f7956130
XFS (...): Log I/O Error Detected.
Shutting down filesystem
XFS (...): Please unmount the filesystem
and rectify the problem(s)

(very funny XFS!)

XFS (...): log I/O error -5

scsi 7:0:0:0: rejecting I/O to dead device

-Andi

             reply	other threads:[~2020-03-15  3:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-14 13:31 Andi Kleen [this message]
2020-03-16  2:03 ` Shutdown preventing umount Dave Chinner
2020-03-16  3:37   ` Andi Kleen
2020-03-16  5:25     ` Dave Chinner

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=20200314133107.4rv25sp4bvhbjjsx@two.firstfloor.org \
    --to=andi@firstfloor.org \
    --cc=linux-xfs@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