From: rnb <neil.bell@gmail.com>
To: xfs@oss.sgi.com
Subject: xfs i/O error
Date: Thu, 30 Jul 2009 10:03:28 -0700 (PDT) [thread overview]
Message-ID: <24742623.post@talk.nabble.com> (raw)
Running Ubuntu 9.04 kernel 2.26.28.14 generic
Drive mounts fine.
xfs_repair shows no errors
sudo xfs_repair /dev/sdg1
Phase 1 - find and verify superblock...
Phase 2 - using internal log
- zero log...
- scan filesystem freespace and inode maps...
- found root inode chunk
Phase 3 - for each AG...
- scan and clear agi unlinked lists...
- process known inodes and perform inode discovery...
- agno = 0
- agno = 1
- agno = 2
- agno = 3
- process newly discovered inodes...
Phase 4 - check for duplicate blocks...
- setting up duplicate extent list...
- check for inodes claiming duplicate blocks...
- agno = 0
- agno = 1
- agno = 2
- agno = 3
Phase 5 - rebuild AG headers and trees...
- reset superblock...
Phase 6 - check inode connectivity...
- resetting contents of realtime bitmap and summary inodes
- traversing filesystem ...
- traversal finished ...
- moving disconnected inodes to lost+found ...
Phase 7 - verify and correct link counts...
done
xfs_check did move a few things around but finished fine
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
ino=139
extents before:66 after:8 ino=139
ino=145
extents before:42 after:7 ino=145
ino=146
extents before:40 after:8 ino=146
ino=143
bad read of 0 bytes from ino=143: Input/output error
ino=144
extents before:27 after:8 ino=144
ino=8763008
bad read of 0 bytes from ino=8763008: Input/output error
ino=8763059
bad read of 0 bytes from ino=8763059: Input/output error
ino=8763057
extents before:307 after:12 ino=8763057
ino=8763058
extents before:259 after:11 ino=8763058
ino=8763024
bad read of 0 bytes from ino=8763024: Input/output error
ino=8763055
kk
extents before:125 after:10 ino=8763055
ino=8763030
bad read of 0 bytes from ino=8763030: Input/output error
ino=8763060
bad read of 0 bytes from ino=8763060: Input/output error
ino=8763056
extents before:62 after:13 ino=8763056
ino=8763066
Now my issue is how do I fix it if xfs_repair doesn't see a problem.
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
--
View this message in context: http://www.nabble.com/xfs-i-O-error-tp24742623p24742623.html
Sent from the Xfs - General mailing list archive at Nabble.com.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2009-07-30 17:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-30 17:03 rnb [this message]
2009-07-30 19:13 ` xfs i/O error Eric Sandeen
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=24742623.post@talk.nabble.com \
--to=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 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.