Skip to contentSkip to conversation

forwarded message from Jan De Luyck

DISCUSSION Vitaly Fertman 3 participants 5 messages Dec 10, 2003 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

#1 lore raw

Hello,

Quoted 5 lines

Hello,

Today I discovered this in my syslogs, after something strange happening to XFree86 (hung at startup, then dumped me back to the console)

Quoted 7 lines

is_leaf: free space seems wrong: level=1, nr_items=41, free_space=65224 rdkey vs-5150: search_by_key: invalid format found in block 283191. Fsck?
vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [11 12795 0x0 SD] is_leaf: free space seems wrong: level=1, nr_items=41, free_space=65224 rdkey vs-5150: search_by_key: invalid format found in block 283191. Fsck? vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [11 12798 0x0 SD]

this all about fs corruptions. fsck is needed.

Quoted 8 lines

I've never seen these before, and I've been digging through my syslogs but am unable to find any other references of this.
Does this mean the disk is dying? Or just the filesystem is corrupt? Unfortunately, I'm not able to rebuild the tree at this time because I haven't got a 'rescue' disk with me and the errors are on my root partition...

Any other pointers?

reiserfsck from the 3.6.12-pre1 package is able to recover mounted ro partitions.

--
Thanks,
Vitaly Fertman

#2 lore raw
Quoted 2 lines · Vitaly Fertman

reiserfsck from the 3.6.12-pre1 package is able to recover mounted ro partitions.

Thanks. This worked great, system is back in mint condition ;p

Jan

Signature · 2 lines
All the men on my staff can type.
		-- Bella Abzug
#3 lore raw
In reply to Vitaly Fertman
Quoted 19 lines · Vitaly Fertman

Hello,

Quoted 5 lines

Hello,

Today I discovered this in my syslogs, after something strange happening to XFree86 (hung at startup, then dumped me back to the console)

Quoted 9 lines

is_leaf: free space seems wrong: level=1, nr_items=41, free_space=65224 rdkey vs-5150: search_by_key: invalid format found in block 283191. Fsck?
vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [11 12795 0x0 SD] is_leaf: free space seems wrong: level=1, nr_items=41, free_space=65224 rdkey vs-5150: search_by_key: invalid format found in block 283191. Fsck? vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [11 12798 0x0 SD]

Quoted 3 lines

this all about fs corruptions. fsck is needed.

is this a failure due to bad sector on the drive?

Quoted 27 lines
Quoted 12 lines

I've never seen these before, and I've been digging through my syslogs but am unable to find any other references of this.
Does this mean the disk is dying? Or just the filesystem is corrupt? Unfortunately, I'm not able to rebuild the tree at this time because I haven't got a 'rescue' disk with me and the errors are on my root partition...

Any other pointers?

reiserfsck from the 3.6.12-pre1 package is able to recover mounted ro partitions.

--
Thanks,
Vitaly Fertman
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Signature · 1 line
Hans
#4 lore raw
Quoted 18 lines · Hans Reiser
Quoted 17 lines · Vitaly Fertman

Hello,

Quoted 14 lines

Hello,

Today I discovered this in my syslogs, after something strange happening to XFree86 (hung at startup, then dumped me back to the console)

is_leaf: free space seems wrong: level=1, nr_items=41, free_space=65224 rdkey vs-5150: search_by_key: invalid format found in block 283191. Fsck?
vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [11 12795 0x0 SD] is_leaf: free space seems wrong: level=1, nr_items=41, free_space=65224 rdkey vs-5150: search_by_key: invalid format found in block 283191. Fsck? vs-13070:
reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [11 12798 0x0 SD]

Quoted 3 lines
Quoted 1 line

this all about fs corruptions. fsck is needed.

is this a failure due to bad sector on the drive?

No, we return EIO in many places if some data corruption is found even if the hardware has worked ok. A stat data has not been found here and EIO is returned.

--
Thanks,
Vitaly Fertman

#5 lore raw
Quoted 33 lines · Vitaly Fertman
Quoted 23 lines · Hans Reiser
Quoted 20 lines · Vitaly Fertman

Hello,

Quoted 16 lines

Hello,

Today I discovered this in my syslogs, after something strange happening to XFree86 (hung at startup, then dumped me back to the console)

is_leaf: free space seems wrong: level=1, nr_items=41, free_space=65224 rdkey vs-5150: search_by_key: invalid format found in block 283191. Fsck?
vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [11 12795 0x0 SD] is_leaf: free space seems wrong: level=1, nr_items=41, free_space=65224 rdkey vs-5150: search_by_key: invalid format found in block 283191. Fsck? vs-13070:
reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [11 12798 0x0 SD]

Quoted 6 lines
Quoted 3 lines

this all about fs corruptions. fsck is needed.

is this a failure due to bad sector on the drive?

Quoted 10 lines

No, we return EIO in many places if some data corruption is found even if the hardware has worked ok. A stat data has not been found here and EIO is returned.

--
Thanks,
Vitaly Fertman

fix the code to have a more accurate description. This is not what I would consider an IO error, and it should not describe itself to users that way.

Also, please attempt to determine if this is happening on a file system that has only had a recent kernel running on it. I am concerned that we might have a bug in recent V3.

Signature · 1 line
Hans