From: Eric Sandeen <sandeen@sandeen.net>
To: rnb <neil.bell@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: xfs i/O error
Date: Thu, 30 Jul 2009 14:13:21 -0500 [thread overview]
Message-ID: <4A71F0D1.1020005@sandeen.net> (raw)
In-Reply-To: <24742623.post@talk.nabble.com>
rnb wrote:
> Running Ubuntu 9.04 kernel 2.26.28.14 generic
> Drive mounts fine.
> xfs_repair shows no errors
...
>
> xfs_check did move a few things around but finished fine
Actually xfs_check never changes anything ;)
> sudo xfs_fsr -v /dev/sdg1 <== This is just so far it is still running.
> /media/Films start inode=0
> ino=140
> bad read of 0 bytes from ino=140: Input/output error
Anything in dmesg when this happens?
...
> Now my issue is how do I fix it if xfs_repair doesn't see a problem.
It must not be a problem on-disk. At least, hopefully not. :)
> Anything getting copied to the drive works fine in place wasn't until i
> tried to move it off I noticed the issue. Some things copy fine from it
> several others fail. Then i get Input/output error. It is a full 1tb drive .
> WD mybook it lost power which I think is what caused this issue. How can I
> correct the issue. Everything I try takes a hell of a long time and doesn't
> yield a positive result
Oh, so it's not just fsr that does it? cp too?
Anyway, look at dmesg when you get the error and see if there are
messages logged from the kernel when this happens.
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-07-30 19:12 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 [this message]
2009-07-30 21:45 ` rnb
2009-07-30 23:48 ` Michael Monnerie
2009-07-31 3:37 ` Eric Sandeen
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=4A71F0D1.1020005@sandeen.net \
--to=sandeen@sandeen.net \
--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