Re: raid1 critical sections not protected in 2.4.x?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 2003-10-09T10:41:59,
   Steven Dake <sdake@mvista.com> said:

> I have been looking at the raid1.c code.  There is a kernel thread
> raid1d that could be scheduled on processor A.  Then on processor B,
> other raid code could be scheduled as per each block I/O request.

Did you follow the recent locking fixes to md I discussed with Neil? I
think this fixes some of these; at least we have a confirmation from IBM
that some raid1 races (not resyncing after a hotadd, no progress during
resync etc) went away with it.


Sincerely,
    Lars Marowsky-Brée <lmb@suse.de>

-- 
High Availability & Clustering		ever tried. ever failed. no matter.
SuSE Labs				try again. fail again. fail better.
Research & Development, SUSE LINUX AG		-- Samuel Beckett

-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux