Re: kernel panic (2.6.36) after file system corruption (?)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, 21 Dec 2010 18:35:55 +0100, Jan Misiak wrote:
> On 21 December 2010 03:55, Ryusuke Konishi
> <konishi.ryusuke@xxxxxxxxxxxxx> wrote:
> > Could you get device size information in a few ways?
> 
> Certainly.
> 
> > 1) sysfs reported sizes
> >  # cat /sys/block/sdb/size
> 31506432
> 
> >  # cat /sys/block/sdb/sdb1/size
> 31504384
> 
> > 2) Sizes on the partition table
> >  # fdisk -lu /dev/sdb
> Disk /dev/sdb: 16.1 GB, 16131293184 bytes
> 25 heads, 25 sectors/track, 50410 cylinders, total 31506432 sectors
> Units = sectors of 1 * 512 = 512 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disk identifier: 0x04030201
> 
> Device Boot      Start         End      Blocks   Id  System
> /dev/sdb1            2048    31506431    15752192    7  HPFS/NTFS
> 
> > 3) Dump of the first super block (it has the layout information)
> >  # dd if=/dev/sdb1 bs=1k count=1 skip=1 2>/dev/null | hd
> #dd if=/dev/sdb1 bs=1k count=1 skip=1 2>/dev/null | hexdump
> 0000000 0002 0000 0000 3434 0100 0000 e5da ead2
> 0000010 e644 38c1 0002 0000 0782 0000 0000 0000
> 0000020 0000 c170 0003 0000 0001 0000 0000 0000
> 0000030 0800 0000 0005 0000 92c7 0002 0000 0000
> 0000040 f800 0013 0000 0000 f1e3 0001 0000 0000
> 0000050 6000 0007 0000 0000 8836 4c69 0000 0000
> 0000060 f119 4cf0 0000 0000 f119 4cf0 0000 0000
> 0000070 002f 0032 0000 0001 8836 4c69 0000 0000
> 0000080 4e00 00ed 0000 0000 0000 0000 000b 0000
> 0000090 0080 0020 00c0 0010 2be3 b1ef 799b cb4b
> 00000a0 d0a5 5ae1 9892 80a8 0000 0000 0000 0000
> 00000b0 0000 0000 0000 0000 0000 0000 0000 0000
> *
> 0000400
> 
> Hope that helps. Please let me know if you need anything else.
> 
> Regards,
> Jan

All of the information looks sane including the device sizes.

By the way, did you separate the block layer problem from filesystem
problem ?

If not yet, could you try the following tests ?

1) quick device write test

 # dd if=/dev/zero of=/dev/sdb1 bs=1k count=1 skip=2

 This zero-fills an unused block in the partition.

2) backup and recovery test

 # dd if=/dev/sdb1 of=/path-to-large-disk/backup.img bs=4k
 # dd if=/path-to-large-disk/backup.img of=/dev/sdb1 bs=4k


With regards,
Ryusuke Konishi
--
To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Filesystem Development]     [Linux BTRFS]     [Linux CIFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux SCSI]

  Powered by Linux