On 5 Jul 2002, Daniel Egger wrote:
> Though the timespan makes me curious: Why is there a magnitude
> difference in runtime between the first problem on a fresh drive
> and after a lowlevel format?
Can be anything. The disk's administration parts getting messed up with
crap, and already having got messed up by some test run right after
production. Or maybe the drives were padded with maintainer data before
they were shipped (means, after production).
Imagine it thermodynamically. A half-ordered system keeps getting messed
up. Somewhen it's messed up. If you order your system it will take longer
for the drive to get messed up.
Maybe the part which failed in the old firmware was some garbage
collection code? Something that removes the crap?
Regards,
Thunder
-- (Use http://www.ebb.org/ungeek if you can't decode) ------BEGIN GEEK CODE BLOCK------ Version: 3.12 GCS/E/G/S/AT d- s++:-- a? C++$ ULAVHI++++$ P++$ L++++(+++++)$ E W-$ N--- o? K? w-- O- M V$ PS+ PE- Y- PGP+ t+ 5+ X+ R- !tv b++ DI? !D G e++++ h* r--- y- ------END GEEK CODE BLOCK------- 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/