xfs
[Top] [All Lists]

Re: xfs i/O error

To: xfs@xxxxxxxxxxx
Subject: Re: xfs i/O error
From: rnb <neil.bell@xxxxxxxxx>
Date: Thu, 30 Jul 2009 14:45:12 -0700 (PDT)
In-reply-to: <24742623.post@xxxxxxxxxxxxxxx>
References: <24742623.post@xxxxxxxxxxxxxxx>
[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.

rnb wrote:
> 
> 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-tp24742623p24747808.html
Sent from the Xfs - General mailing list archive at Nabble.com.

<Prev in Thread] Current Thread [Next in Thread>