Messages in this thread | | | Date | Thu, 30 Sep 1999 02:39:51 +0200 (MET DST) | From | (Guest section DW) | Subject | Re: Possible inode.c problem for EXT2 |
| |
From sct@redhat.com Thu Sep 30 00:26:56 1999 From: "Stephen C. Tweedie" <sct@redhat.com>
On Tue, 28 Sep 1999 14:14:46 -0400, tytso@mit.edu said:
>> Well, that means the ext2 filesystem found ASCII data in either the >> inode table or an indirect metatdata block.
> I don't think so. > Look at what is printed...
The ll_rw_block has already converted the raw ascii text on disk (in block numbers) into a sector number, so the reverse transform in the printk just restores what was in the original corrupt indirect block.
So it _does_ mean that we found text in an indirect block after all.
Hmm. I quoted the code
count = bh->b_size >> 9; sector = bh->b_rsector; printk("%d", (sector + count)>>1);
Are you saying that (sector + count)>>1 was found on disk ? Or only sector>>1 ?
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |