Re: I/O errors on Hammer volume

[Matthew Dillon <dillon@xxxxxxxxxxxxxxxxxxxx>]

: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% {
:
:BM   NODE 800000268eb0e000 cnt=32 p=800000268eb02000 type=L depth=4 mirror
:0000000148774380 fill=z8:19741=60% {
:
:BM   NODE 800000268eb19000 cnt=32 p=800000268eb02000 type=L depth=4 mirror
:0000000139b6e840 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.

    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?  If this
    is the case it should be possible to remove them with 'rm'.

					-Matt
					Matthew Dillon 
					<dillon@backplane.com>