Re: Ooops on read-only raid5 while unmounting as xfs

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

 



On 23 Jan 2007, Neil Brown said:

> On Tuesday January 23, francois.barre@xxxxxxxxx wrote:
>> 
>> My question is then : what prevents the upper layer to open the array
>> read-write, submit a write and make the md code BUG_ON() ?
>
> The theory is that when you tell an md array to become read-only, it
> tells the block layer that it is read-only, and then if some process
> tries to open it read/write, it gets an array.

Um. Do you mean it gets an *error*? ;}

-- 
`The serial comma, however, is correct and proper, and abandoning it will
surely lead to chaos, anarchy, rioting in the streets, the Terrorists
taking over, and possibly the complete collapse of Human Civilization.'
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
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