On Saturday November 11, [email protected] wrote:
> I have a 8 disk 1.5 TB raid6 volume that won't mount in 2.6.19-rc5-mm1.
> Below the output of trying to mount the ext3 volume, which fails, and
> the very wrong output after mounting it as ext2. Also, mdstat details,
> .config and dmesg output.
>
> This volume works just fine in 2.6.18-mm3 or 2.6.19-rc2-mm2. I'm willing
> to test, but I'm not that willing to wreck my volume :-)
Can you try reverting this patch (patch -p1 -R) ?
It is the most likely candidate. Meanwhile I look to see if I can
see how this could be happening.
NeilBrown
--------------------------
Enable bypassing cache for reads.
From: "Raz Ben-Jehuda(caro)" <[email protected]>
Call the chunk_aligned_read where appropriate.
Signed-off-by: Neil Brown <[email protected]>
### Diffstat output
./drivers/md/raid5.c | 5 +++++
1 file changed, 5 insertions(+)
diff .prev/drivers/md/raid5.c ./drivers/md/raid5.c
--- .prev/drivers/md/raid5.c 2006-11-06 11:29:14.000000000 +1100
+++ ./drivers/md/raid5.c 2006-11-06 11:29:14.000000000 +1100
@@ -2798,6 +2798,11 @@ static int make_request(request_queue_t
disk_stat_inc(mddev->gendisk, ios[rw]);
disk_stat_add(mddev->gendisk, sectors[rw], bio_sectors(bi));
+ if ( bio_data_dir(bi) == READ &&
+ mddev->reshape_position == MaxSector &&
+ chunk_aligned_read(q,bi))
+ return 0;
+
logical_sector = bi->bi_sector & ~((sector_t)STRIPE_SECTORS-1);
last_sector = bi->bi_sector + (bi->bi_size>>9);
bi->bi_next = NULL;
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
