Re: IDE hang, partition strangeness

From: Andrew Morton (akpm@zip.com.au)
Date: Fri Aug 02 2002 - 01:56:10 EST


Andrew Morton wrote:
>
> Seems that the partitioning code in 2.5.30 is sending illegal LBAs
> to the IDE driver, which responds by hanging the box:

I misread this backtrace:

> #0 __lock_page (page=0xc1994ff0) at /usr/src/25/include/asm/bitops.h:136
> #1 0xc012ca43 in lock_page (page=0xc3ff1960) at filemap.c:692
> #2 0xc012dba9 in read_cache_page (mapping=0xc2f6a144, index=20010815, filler=0xc01428c0 <blkdev_readpage>,
> data=0x0) at filemap.c:1756
> #3 0xc0162d16 in read_dev_sector (bdev=0xc2f0ef20, n=160086527, p=0xc3fd7d60) at check.c:539
> #4 0xc0166bae in read_lba (bdev=0xc2f0ef20, lba=160086528, buffer=0xc2f6d200 "", count=512) at efi.c:205
> #5 0xc0166ccf in alloc_read_gpt_header (bdev=0xc2f0ef20, lba=160086527) at efi.c:277

_this_ is the lba. 160086527. It is the very last sector on the disk.

block_read_full_page() has issued a read request for the 4k block
at index 20010815, which is LBA 160086520. So the device driver
is being asked to read exactly the final eight blocks on the device.

The partitioning code seems to be OK. There seems to be a problem
reading end-of-disk.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/



This archive was generated by hypermail 2b29 : Wed Aug 07 2002 - 22:00:18 EST