[Top] [All Lists]

Re: failed to read root inode

To: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Subject: Re: failed to read root inode
From: Emmanuel Florac <eflorac@xxxxxxxxxxxxxx>
Date: Sun, 9 May 2010 17:34:07 +0200
Cc: xfs@xxxxxxxxxxx
In-reply-to: <4BE6CC83.5070305@xxxxxxxxxxxxxxxxx>
Organization: Intellique
References: <4BE55A63.8070203@xxxxxxxxxxxxx> <4BE5EB5D.5020702@xxxxxxxxxxxxxxxxx> <20100509152818.7481c1e1@xxxxxxxxxxxxxx> <4BE6CC83.5070305@xxxxxxxxxxxxxxxxx>
Le Sun, 09 May 2010 09:53:55 -0500 vous écriviez:

> Oh, btw, when it comes to SATA drives, there is no difference between
> "desktop" and "enterprise" class drives.  They're all the same. 

Yes I know that, however there's an important  difference : the default
firmware setting of desktop drives makes them retry, retry, retry an
retry on error, effectively freezing the array; while "enterprise
drives" simply fails almost instantly at the slightest error (and work
fine 5 minutes later usually).

So a desktop drive failure in a raid array may actually block all IO
for a very long time (like in minutes), and everything goes west if you
then decide that the system must have crashed and pull the plug, if
your RAID controller hasn't any backup battery.

That's why you shouldn't ever use desktop drives in RAID arrays unless
you know how to painfully configure them, one by one, with a friggin
DOS utility ;)

Emmanuel Florac     |   Direction technique
                    |   Intellique
                    |   <eflorac@xxxxxxxxxxxxxx>
                    |   +33 1 78 94 84 02

<Prev in Thread] Current Thread [Next in Thread>