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

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

 



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.

I say "theory" because I have never really tested any of the read-only
stuff.  I have had a feeling for a long time that it really needs a
bit of thought and testing and documentation, but it never quite
seemed important enough to get that love-and-care....

NeilBrown
-
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