On Sun, Nov 18, 2007 at 08:49:44PM +, [EMAIL PROTECTED] wrote:
> >>> On Sun, 18 Nov 2007 21:06:42 +0100, Bernd Schubert
> >>> <[EMAIL PROTECTED]> said:
>
> bernd-schubert> Hi, on raid-initialization or later on a re-sync
> bernd-schubert> our systems become unresponsive. [ ... ] Also,
> bernd-
>>> On Sun, 18 Nov 2007 21:06:42 +0100, Bernd Schubert
>>> <[EMAIL PROTECTED]> said:
bernd-schubert> Hi, on raid-initialization or later on a re-sync
bernd-schubert> our systems become unresponsive. [ ... ] Also,
bernd-schubert> the higher the stripe cache size, the higher the
bernd-schubert> prob
Hi,
on raid-initialization or later on a re-sync our systems become
unresponsive. Ping still works, ssh won't succeed until the re-sync has
finished, on a serial or local connection one can still type, as with ssh,
whatever you request from the system won't be done until the raid-sync is
done.
Neil Brown <[EMAIL PROTECTED]> writes:
> On Monday November 12, [EMAIL PROTECTED] wrote:
>> Neil Brown wrote:
>> >
>> > However there is value in regularly updating the bitmap, so add code
>> > to periodically pause while all pending sync requests complete, then
>> > update the bitmap. Doing this
Chris Eddington wrote:
> Key questions:
> - I assume ddrescue will do a much better job of correcting errors when
> imaging a disk? My colleague used ghost which is just a copy tool. I
> don't understand the capabilities of ddrescue on raid partitions that well.
ddrescue should do a *much* better
