Is your raid0 ontop of a raid1 ???
If so, this patch is needed.
NeilBrown
--------------------------------------------------------
Set BH_Locked when accessing MD superblocks
Some silly drivers (like raid1 !!) want BH_Locked to be set on all IO,
so we humour them by setting the bit when doing superblock IO.
----------- Diffstat output ------------
./drivers/md/md.c | 2 +-
1 files changed, 1 insertion(+), 1 deletion(-)
diff ./drivers/md/md.c~current~ ./drivers/md/md.c
--- ./drivers/md/md.c~current~ 2002-12-17 15:20:57.000000000 +1100
+++ ./drivers/md/md.c 2003-01-02 11:05:20.000000000 +1100
@@ -489,7 +489,7 @@ static int sync_page_io(kdev_t dev, unsi
init_buffer(&bh, bh_complete, &event);
bh.b_rdev = dev;
bh.b_rsector = sector;
- bh.b_state = (1 << BH_Req) | (1 << BH_Mapped);
+ bh.b_state = (1 << BH_Req) | (1 << BH_Mapped) | (1 << BH_Locked);
bh.b_size = size;
bh.b_page = page;
bh.b_reqnext = NULL;
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/