lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 29 Mar 2007 16:25:04 +1000
From:	Neil Brown <>
To:	Justin Piszcz <>
Subject: Re: Software RAID (non-preempt) server blocking question. (

On Tuesday March 27, wrote:
> I ran a check on my SW RAID devices this morning.  However, when I did so, 
> I had a few lftp sessions open pulling files.  After I executed the check, 
> the lftp processes entered 'D' state and I could do 'nothing' in the 
> process until the check finished.  Is this normal?  Should a check block 
> all I/O to the device and put the processes writing to a particular device 
> in 'D' state until it is finished?

No, that shouldn't happen.  The 'check' should notice any other disk
activity and slow down if anything else is happening on the device.

Did the check run to completion?  And if so, did the 'lftp' start
working normally again?

Did you look at "cat /proc/mdstat" ?? What sort of speed was the check
running at?

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists