On 23 Jan 2007, Neil Brown said:
On Tuesday January 23, [EMAIL PROTECTED] 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
3. mark the array read-only (mdadm -o)
You shouldn't be able to do this. It should only be possible to set
an array to read-only when it is not in use. The fact that you cannot
suggests something else if wrong.
Should I ? I assumed that mdadm -o could be run with a running used
array, and
On Tuesday January 23, [EMAIL PROTECTED] 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
On Thursday January 18, [EMAIL PROTECTED] wrote:
Hi all,
I've hit the following bug while unmounting a xfs partition
--- [cut here ] - [please bite here ] -
Kernel BUG at drivers/md/md.c:5035
Kernel : stock-kernel 2.6.18.6, x86_64
Setup : xfs on raid5, on 5
Hi all,
I've hit the following bug while unmounting a xfs partition
--- [cut here ] - [please bite here ] -
Kernel BUG at drivers/md/md.c:5035
invalid opcode: [1] SMP
CPU 0
Modules linked in: unionfs sbp2 ohci1394 ieee1394 raid456 xor
w83627ehf i2c_isa i2c_core
Pid:
