Re: I/O errors on Hammer volume

[Francois Tigeot <ftigeot@xxxxxxxxxxxx>]

On Tue, Apr 13, 2010 at 11:02:05PM -0700, Matthew Dillon wrote:
> :BM   NODE 800000268ea27000 cnt=33 p=800000268ea12000 type=L depth=4 mirror
> :000000013a77e4d0 fill=z8:19741=60% {
> :
> :BM   NODE 800000268ea31000 cnt=33 p=800000268ea12000 type=L depth=4 mirror
> :0000000139b6e140 fill=z8:19741=60% {
> :
> :-- 
> :Francois Tigeot
> 
>     If the only flag after B is 'M' then it is ok, it's the mirror-tid
>     bug which was fixed in 2.6 but only effects incremental mirroring.
>     This is self-correcting so it isn't a concern.
> 
>     If other flags are present then we have a real problem.

Ok. I'm creating a complete log of the hammer show output. I'll grep for the
answer when it's done.

>     If the broken inodes are localized it could be stuff left dangling
>     from a crash recovery.  That's my hope.  Did you have any crashes
>     while work was occuring on any of the related directories?

Nope. The errors appeared out of the blue.
At one time I suddenly found garbled contents in mails I was reading with
mutt. I later found out /usr/share/i18n/iconv/iconv.dir had become unreadable.

>     If this is the case it should be possible to remove them with 'rm'.

This is not possible :
# rm iconv.dir
rm: iconv.dir: Input/output error

-- 
Francois Tigeot