xfs i/O error

DISCUSSION rnb 4 participants 7 messages Jul 30, 2009 – Jul 31, 2009

Share & tools

rnb

author

2009-07-30 17:02 UTC #0 lore 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

Signature · 7 lines

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
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs

Eric Sandeen

2009-07-30 19:12 UTC #1 lore raw

Quoted 3 lines · rnb

Running Ubuntu 9.04 kernel 2.26.28.14 generic
Drive mounts fine.
xfs_repair shows no errors

...

Quoted 2 lines

xfs_check did move a few things around but finished fine

Actually xfs_check never changes anything ;)

Quoted 4 lines

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?

...

Quoted 1 line

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. :)

Quoted 6 lines

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
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs

rnb

author

2009-07-30 21:44 UTC #2 lore raw

In reply to rnb

[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
[70276.938405] sd 8:0:0:0: [sdg] Result: hostbyte=DID_OK

driverbyte=DRIVER_SENSE,SUGGEST_OK

running a defrag that last few hours so there are tonnes of those. Like i said it has no issues mounting, xfs_repair fails to see the problem. Bad sectors I hope not the drives are a few months old and this is a storage server to it isn't like it is getting a tonne of writing done to it. Being external though I can't rule out hardware failure and smartctl doesn't run over USB.

Quoted 80 lines · rnb

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

Signature · 7 lines

View this message in context: http://www.nabble.com/xfs-i-O-error-tp24742623p24747808.html
Sent from the Xfs - General mailing list archive at Nabble.com.

_______________________________________________
xfs mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs

Michael Monnerie

2009-07-30 23:48 UTC #3 lore raw

Quoted 4 lines · 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

Signature · 5 lines

// Michael Monnerie, Ing.BSc    -----      http://it-management.at
// Tel: 0660 / 415 65 31                      .network.your.ideas.
// PGP Key:         "curl -s http://zmi.at/zmi.asc | gpg --import"
// Fingerprint: AC19 F9D5 36ED CD8A EF38  500E CE14 91F7 1C12 09B4
// Keyserver: wwwkeys.eu.pgp.net                  Key-ID: 1C1209B4

_______________________________________________
xfs mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs

Eric Sandeen

2009-07-31 03:37 UTC #4 lore raw

Quoted 9 lines · Michael Monnerie

Quoted 4 lines · 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
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs

Michael Monnerie

2009-07-31 09:07 UTC #5 lore raw

Quoted 2 lines · On Freitag 31 Juli 2009 Eric Sandeen wrote:

Read errors can be somewhat recoverable, if you write to that sector it will remap if it can.

Yes, but I've never seen a disk who did not get other broken sectors later. When a disk starts to get bad sectors, others will come, just like a virus. Therefore: you get a bad sector -> replace disk. That's by far less pain and cheaper than the other scenario.

mfg zmi

Signature · 5 lines

// Michael Monnerie, Ing.BSc    -----      http://it-management.at
// Tel: 0660 / 415 65 31                      .network.your.ideas.
// PGP Key:         "curl -s http://zmi.at/zmi.asc | gpg --import"
// Fingerprint: AC19 F9D5 36ED CD8A EF38  500E CE14 91F7 1C12 09B4
// Keyserver: wwwkeys.eu.pgp.net                  Key-ID: 1C1209B4

_______________________________________________
xfs mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs

Emmanuel Florac

2009-07-31 20:36 UTC #6 lore raw

In reply to rnb

Le Thu, 30 Jul 2009 14:45:12 -0700 (PDT) vous écriviez:

Quoted 2 lines

said it has no issues mounting, xfs_repair fails to see the problem. Bad sectors I hope not

Hope lost. All these messages are absolutely clear, your drive is almost certainly dying.

Signature · 8 lines

--------------------------------------------------
Emmanuel Florac               www.intellique.com   
--------------------------------------------------

_______________________________________________
xfs mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs