From: Eric Sandeen <sandeen@sandeen.net>
To: Michael Monnerie <michael.monnerie@is.it-management.at>
Cc: rnb <neil.bell@gmail.com>, xfs@oss.sgi.com
Subject: Re: xfs i/O error
Date: Thu, 30 Jul 2009 22:37:53 -0500 [thread overview]
Message-ID: <4A726711.5050402@sandeen.net> (raw)
In-Reply-To: <200907310148.52085@zmi.at>
Michael Monnerie wrote:
> On Donnerstag 30 Juli 2009 rnb wrote:
>> [70273.864305] sd 8:0:0:0: [sdg] Sense Key : Medium Error [current]
>> [70273.864314] Info fld=0x0
>> [70273.864318] sd 8:0:0:0: [sdg] Add. Sense: Unrecovered read error
>> [70273.864327] end_request: I/O error, dev sdg, sector 378206415
>
> Disk is bad, replace it.
>
> mfg zmi
More or less, yep.
Read errors can be somewhat recoverable, if you write to that sector it
will remap if it can.
But anyway yeah, it's not an xfs I/O error, it's a disk IO error, and
xfs is bringing you the bad news.
repair may not have seen it because repair only looks at metadata, bad
sectors may be data in blocks, found when you try to copy data around.
-eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-07-31 3:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-30 17:03 xfs i/O error rnb
2009-07-30 19:13 ` Eric Sandeen
2009-07-30 21:45 ` rnb
2009-07-30 23:48 ` Michael Monnerie
2009-07-31 3:37 ` Eric Sandeen [this message]
2009-07-31 9:08 ` Michael Monnerie
2009-07-31 20:36 ` Emmanuel Florac
-- strict thread matches above, loose matches on Subject: below --
2008-02-23 21:46 xfs I/O error Rekrutacja119
2008-02-23 22:08 ` Iustin Pop
2008-02-23 22:14 ` Rekrutacja119
2008-02-24 9:01 ` Iustin Pop
2008-02-24 11:52 ` Rekrutacja119
2008-02-24 12:31 ` Iustin Pop
2008-02-25 16:40 ` Rekrutacja119
2008-02-25 17:17 ` Eric Sandeen
2008-02-24 3:53 ` Eric Sandeen
2008-02-24 12:17 ` Ragnar Kjørstad
[not found] ` <2db2c6b80802250847m2d161f5n276026dae396d3cc@mail.gmail.com>
[not found] ` <20080225211055.GK29277@vestdata.no>
2008-02-26 20:13 ` Rekrutacja119
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=4A726711.5050402@sandeen.net \
--to=sandeen@sandeen.net \
--cc=michael.monnerie@is.it-management.at \
--cc=neil.bell@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox