Message-ID: <43F3B07C.8040803@cfl.rr.com>
Date: Wed, 15 Feb 2006 17:51:40 -0500
From: Phillip Susi <psusi@cfl.rr.com>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: Michael Tokarev <mjt@tls.msk.ru>
CC: "linux-os (Dick Johnson)" <linux-os@analogic.com>,
       Linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: readahead logic and I/O errors
References: <43F39089.2050302@tls.msk.ru> <Pine.LNX.4.61.0602151549190.10849@chaos.analogic.com> <43F3A4EA.3040000@tls.msk.ru>
In-Reply-To: <43F3A4EA.3040000@tls.msk.ru>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 2228
Lines: 46

Michael Tokarev wrote:
> I opened the drive after BIOS didn't detect it on reboot (after
> power-off).  There's one fired (burned? perished? how's that in

I think you mean "fried", which is what happens when something is heated 
to excess.  "fired" is what happens to you when your boss catches you 
stealing office supplies or sleeping with his daughter.  It is also what 
happens to the bullet when you pull the trigger.

> english?) chip on the plate, wich smells like fired silicone.
>  It looks like a ~5mm pit in the center of square chip, full of
> ache, and there's a crack across it.  The drive is dead.
> 
> I think it's a chip which controls one of the motors of the drive,
> most probably the one which moves the head, because the head
> motor connector is right near the chip.
> 
> When I turned off power, the drive was *hot*, and it started
> "trembling" (or chattering) when I turned power off.
> 
> It was a dvd-cd combo (read dvd, read-write cd) Teac drive, I
> don't remember the model (there's no label on the drive, and
> I can't send inquiry/identify command to it anymore, obviously).
> 
> Yest it looks like a problem in the drive *too*, as it should
> not behave like that in the first place.  But the thing is, I
> did know something's bad going on, I saw it, but I wasn't able
> to stop it from linux, only poweroff stopped things from going.
> 
> /mjt

I assume the drive was no longer under warranty?  It certainly should 
not have burned itself out like that, but yea, the kernel should not 
keep trying to readahead on error.  I ran into a similar problem where I 
mounted a filesystem on a cdrw read/write and wrote some files to it. 
When I went to unmount it all the writes failed because the media was 
not properly formatted to be writable.  The kernel kept trying to write 
each sector though, and blocked the umount process in the unkillable D 
state for a good 20 minutes and kept the drive door locked.  Needless to 
say, I was very annoyed.

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