Re: [PATCH 1/1] filesystem: Disk Errors at boot-time caused by probe of partitions

On 2/1/07, Andrew Morton <[email protected]> wrote:

Also, from reading the replies I think we'd like to see some more
explanation of why this is necessary: are you really really sure that those
disks were incorrectly handling illegal sector numbers?  Knowing the IBM
and Maxtor model numbers might be useful.


I'd like to know the model numbers (and firmware revisions) too.

The drive knows how many LBAs it has, and making sure the span of the
command is within the valid LBA space is one of the first things
checked.

Another possibility of for clunking is if the drive is damaged and
cannot track follow in a region, the drive will go to the latch and
push off repeatedly attempting to reacquire servo information.  That
can be scary sounding if you haven't heard it before.

Not saying the bug is impossible, but I'd like to know more.

--eric
-
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/

References:
- [PATCH 1/1] filesystem: Disk Errors at boot-time caused by probe of partitions
  - From: TJ <[email protected]>
- Re: [PATCH 1/1] filesystem: Disk Errors at boot-time caused by probe of partitions
  - From: Andrew Morton <[email protected]>

Prev by Date: Re: [PATCH] mm: fix page_mkclean_one
Next by Date: Re: [PATCH] CELL PPU Oprofile cleanup patch
Previous by thread: Re: [PATCH 1/1] filesystem: Disk Errors at boot-time caused by probe of partitions
Next by thread: Re: [PATCH 1/1] filesystem: Disk Errors at boot-time caused by probe of partitions
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]