Re: [Patch] document ext3 requirements (was Re: [RFD] Incrementalfsck)

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Theodore Tso <tytso@...>
Cc: Bryan Henderson <hbryan@...>, Ric Wheeler <ric@...>, Al Boldi <a1426z@...>, Alan Cox <alan@...>, David Chinner <dgc@...>, <linux-kernel@...>, Pavel Machek <pavel@...>, Daniel Phillips <phillips@...>, Rik van Riel <riel@...>, Valerie Henson <val.henson@...>
Date: Friday, January 18, 2008 - 11:16 am

On Fri, 18 Jan 2008, Theodore Tso wrote:


I have a Seagate Barracuda 7200.9 80 Gbyte SATA drive that I
use for experiments. I can permanently destroy a EXT3 file-system
at least 50% of the time by disconnecting the data cable while
a `dd` write to a file is in progress. Something bad happens
making partition information invalid. I have to re-partition
to reuse the drive.

If I try the same experiment by disconnecting power to the drive
the file is no good (naturally), but the rest of the file-system
is fine.

My theory is that the destination offset is present in every
SATA access and some optimization code within the drive sets
the heads to track zero and writes before any CRC or checksum
is done to find out if it was the correct offset with the
correct data!

Cheers,
Dick Johnson
Penguin : Linux version 2.6.22.1 on an i686 machine (5588.29 BogoMips).
My book : http://www.AbominableFirebug.com/
_


****************************************************************
The information transmitted in this message is confidential and may be privileged.  Any review, retransmission, dissemination, or other use of this information by persons or entities other than the intended recipient is prohibited.  If you are not the intended recipient, please notify Analogic Corporation immediately - by replying to this message or by sending an email to DeliveryErrors@analogic.com - and destroy all copies of this information, including any attachments, without reading or disclosing them.

Thank you.
--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
[RFD] Incremental fsck, Al Boldi, (Tue Jan 8, 5:22 pm)
Re: [RFD] Incremental fsck, Alan, (Tue Jan 8, 5:31 pm)
Re: [RFD] Incremental fsck, Andreas Dilger, (Wed Jan 9, 5:16 am)
Re: [RFD] Incremental fsck, Daniel Phillips, (Sat Jan 12, 7:55 pm)
Re: [RFD] Incremental fsck, Rik van Riel, (Tue Jan 8, 5:41 pm)
Re: [RFD] Incremental fsck, Al Boldi, (Wed Jan 9, 12:40 am)
Re: [RFD] Incremental fsck, , (Wed Jan 9, 4:04 am)
Re: [RFD] Incremental fsck, Valerie Henson, (Wed Jan 9, 3:45 am)
Re: [RFD] Incremental fsck, Al Boldi, (Wed Jan 9, 7:52 am)
Re: [RFD] Incremental fsck, Theodore Tso, (Sat Jan 12, 10:51 am)
Re: [RFD] Incremental fsck, Daniel Phillips, (Sun Jan 13, 8:22 pm)
Re: [RFD] Incremental fsck, Pavel Machek, (Sun Jan 13, 1:19 pm)
Re: [RFD] Incremental fsck, Ric Wheeler, (Mon Jan 14, 9:04 pm)
Re: [RFD] Incremental fsck, Alan Cox, (Sun Jan 13, 1:41 pm)
Re: [Patch] document ext3 requirements (was Re: [RFD] Increm..., Szabolcs Szakacsits, (Thu Jan 17, 8:29 am)
Re: [Patch] document ext3 requirements (was Re: [RFD] Increm..., Christoph Hellwig, (Wed Jan 16, 12:38 pm)
Re: [Patch] document ext3 requirements (was Re: [RFD] Increm..., linux-os (Dick Johnson), (Fri Jan 18, 11:16 am)
Re: [RFD] Incremental fsck, Al Boldi, (Sun Jan 13, 7:05 am)
Re: [RFD] Incremental fsck, Rik van Riel, (Wed Jan 9, 10:44 am)
Re: [RFD] Incremental fsck, Al Boldi, (Thu Jan 10, 9:26 am)