Hi, I have just started to use Linux RAID1 (stock 2.4.17 with Promise TX200). Generally, my setup is working out OK but I have found a problem when trying to remove a disk from an active array using "mdctl --remove /dev/md9 /dev/hdg9". The remove fails with: Feb 21 10:39:10 rook kernel: md: trying to remove hdg9 from md9 ... Feb 21 10:39:10 rook kernel: md: bug in file md.c, line 2334 Feb 21 10:39:10 rook kernel: Feb 21 10:39:10 rook kernel: md:^I********************************** Feb 21 10:39:10 rook kernel: md:^I* <COMPLETE RAID STATE PRINTOUT> * Feb 21 10:39:10 rook kernel: md:^I********************************** Feb 21 10:39:10 rook kernel: md5: <hdg5><hde5> array superblock: Feb 21 10:39:10 rook kernel: md: SB: (V:0.90.0) ID:<84deeb4a.aa94cb7e.d5b2765a.b6dd2c70> CT:3c74cd45 Feb 21 10:39:10 rook kernel: md: L1 S01048704 ND:2 RD:2 md5 LO:0 CS:65536 Feb 21 10:39:10 rook kernel: md: UT:3c74cd46 ST:0 AD:2 WD:2 FD:0 SD:0 CSUM:a1b47748 E:00000001 Feb 21 10:39:10 rook kernel: D 0: DISK<N:0,hde5(33,5),R:0,S:6> Feb 21 10:39:10 rook kernel: D 1: DISK<N:1,hdg5(34,5),R:1,S:6> Feb 21 10:39:10 rook kernel: md: THIS: DISK<N:1,hdg5(34,5),R:1,S:6> Feb 21 10:39:10 rook kernel: md: rdev hdg5: O:hdg5, SZ:01048704 F:0 DN:1 <6>md: rdev superblock: Feb 21 10:39:10 rook kernel: md: SB: (V:0.90.0) ID:<84deeb4a.aa94cb7e.d5b2765a.b6dd2c70> CT:3c74cd45 Feb 21 10:39:10 rook kernel: md: L1 S01048704 ND:2 RD:2 md5 LO:0 CS:65536 Feb 21 10:39:10 rook kernel: md: UT:3c74cd46 ST:0 AD:2 WD:2 FD:0 SD:0 CSUM:de2944f3 E:00000001 Feb 21 10:39:10 rook kernel: D 0: DISK<N:0,hde5(33,5),R:0,S:6> Feb 21 10:39:10 rook kernel: D 1: DISK<N:1,hdg5(34,5),R:1,S:6> Feb 21 10:39:10 rook kernel: md: THIS: DISK<N:1,hdg5(34,5),R:1,S:6> Feb 21 10:39:10 rook kernel: md: rdev hde5: O:hde5, SZ:01048704 F:0 DN:0 <6>md: rdev superblock: Feb 21 10:39:10 rook kernel: md: SB: (V:0.90.0) ID:<84deeb4a.aa94cb7e.d5b2765a.b6dd2c70> CT:3c74cd45 Feb 21 10:39:10 rook kernel: md: L1 S01048704 ND:2 RD:2 md5 LO:0 CS:65536 Feb 21 10:39:10 rook kernel: md: UT:3c74cd46 ST:0 AD:2 WD:2 FD:0 SD:0 CSUM:de2944f0 E:00000001 Feb 21 10:39:10 rook kernel: D 0: DISK<N:0,hde5(33,5),R:0,S:6> Feb 21 10:39:10 rook kernel: D 1: DISK<N:1,hdg5(34,5),R:1,S:6> Feb 21 10:39:10 rook kernel: md: THIS: DISK<N:0,hde5(33,5),R:0,S:6> Feb 21 10:39:10 rook kernel: md9: <hde9><hdg9> array superblock: Feb 21 10:39:10 rook kernel: md: SB: (V:0.90.0) ID:<4e2f37f4.1e416f0a.65871fe9.19f6e481> CT:3c74c44b Feb 21 10:39:10 rook kernel: md: L1 S04194688 ND:2 RD:2 md9 LO:0 CS:65536 Feb 21 10:39:10 rook kernel: md: UT:3c74c637 ST:0 AD:2 WD:2 FD:0 SD:0 CSUM:0e44876c E:00000003 Feb 21 10:39:10 rook kernel: D 0: DISK<N:0,hde9(33,9),R:0,S:6> Feb 21 10:39:10 rook kernel: D 1: DISK<N:1,hdg9(34,9),R:1,S:6> Feb 21 10:39:10 rook kernel: md: THIS: DISK<N:0,hde9(33,9),R:0,S:6> Feb 21 10:39:10 rook kernel: md: rdev hde9: O:hde9, SZ:04194688 F:0 DN:0 <6>md: rdev superblock: Feb 21 10:39:10 rook kernel: md: SB: (V:0.90.0) ID:<4e2f37f4.1e416f0a.65871fe9.19f6e481> CT:3c74c44b Feb 21 10:39:10 rook kernel: md: L1 S04194688 ND:2 RD:2 md9 LO:0 CS:65536 Feb 21 10:39:10 rook kernel: md: UT:3c74c637 ST:0 AD:2 WD:2 FD:0 SD:0 CSUM:0e4487ce E:00000003 Feb 21 10:39:10 rook kernel: D 0: DISK<N:0,hde9(33,9),R:0,S:6> Feb 21 10:39:10 rook kernel: D 1: DISK<N:1,hdg9(34,9),R:1,S:6> Feb 21 10:39:10 rook kernel: md: THIS: DISK<N:0,hde9(33,9),R:0,S:6> Feb 21 10:39:10 rook kernel: md: rdev hdg9: O:hdg9, SZ:04194688 F:0 DN:1 <6>md: rdev superblock: Feb 21 10:39:10 rook kernel: md: SB: (V:0.90.0) ID:<4e2f37f4.1e416f0a.65871fe9.19f6e481> CT:3c74c44b Feb 21 10:39:10 rook kernel: md: L1 S04194688 ND:2 RD:2 md9 LO:0 CS:65536 Feb 21 10:39:10 rook kernel: md: UT:3c74c637 ST:0 AD:2 WD:2 FD:0 SD:0 CSUM:0e4487d1 E:00000003 Feb 21 10:39:10 rook kernel: D 0: DISK<N:0,hde9(33,9),R:0,S:6> Feb 21 10:39:10 rook kernel: D 1: DISK<N:1,hdg9(34,9),R:1,S:6> Feb 21 10:39:10 rook kernel: md: THIS: DISK<N:1,hdg9(34,9),R:1,S:6> Feb 21 10:39:10 rook kernel: md6: <hdg6><hde6> array superblock: Feb 21 10:39:10 rook kernel: md: SB: (V:0.90.0) ID:<f7a37bcb.eb75910e.240e2f77.5fc7636b> CT:3c73ac1d Feb 21 10:39:10 rook kernel: md: L1 S20971840 ND:2 RD:2 md6 LO:0 CS:4096 Feb 21 10:39:10 rook kernel: md: UT:3c73faff ST:0 AD:2 WD:2 FD:0 SD:0 CSUM:8a41a40e E:00000008 Feb 21 10:39:10 rook kernel: D 0: DISK<N:0,hde6(33,6),R:0,S:6> Feb 21 10:39:10 rook kernel: D 1: DISK<N:1,hdg6(34,6),R:1,S:6> Feb 21 10:39:10 rook kernel: md: THIS: DISK<N:1,hdg6(34,6),R:1,S:6> Feb 21 10:39:10 rook kernel: md: rdev hdg6: O:hdg6, SZ:20971840 F:0 DN:1 <6>md: rdev superblock: Feb 21 10:39:10 rook kernel: md: SB: (V:0.90.0) ID:<f7a37bcb.eb75910e.240e2f77.5fc7636b> CT:3c73ac1d Feb 21 10:39:10 rook kernel: md: L1 S20971840 ND:2 RD:2 md6 LO:0 CS:4096 Feb 21 10:39:10 rook kernel: md: UT:3c73faff ST:0 AD:2 WD:2 FD:0 SD:0 CSUM:8a41a878 E:00000008 Feb 21 10:39:10 rook kernel: D 0: DISK<N:0,hde6(33,6),R:0,S:6> Feb 21 10:39:10 rook kernel: D 1: DISK<N:1,hdg6(34,6),R:1,S:6> Feb 21 10:39:10 rook kernel: md: THIS: DISK<N:1,hdg6(34,6),R:1,S:6> Feb 21 10:39:10 rook kernel: md: rdev hde6: O:hde6, SZ:20971840 F:0 DN:0 <6>md: rdev superblock: Feb 21 10:39:10 rook kernel: md: SB: (V:0.90.0) ID:<f7a37bcb.eb75910e.240e2f77.5fc7636b> CT:3c73ac1d Feb 21 10:39:10 rook kernel: md: L1 S20971840 ND:2 RD:2 md6 LO:0 CS:4096 Feb 21 10:39:10 rook kernel: md: UT:3c73faff ST:0 AD:2 WD:2 FD:0 SD:0 CSUM:8a41a875 E:00000008 Feb 21 10:39:10 rook kernel: D 0: DISK<N:0,hde6(33,6),R:0,S:6> Feb 21 10:39:10 rook kernel: D 1: DISK<N:1,hdg6(34,6),R:1,S:6> Feb 21 10:39:10 rook kernel: md: THIS: DISK<N:0,hde6(33,6),R:0,S:6> Feb 21 10:39:10 rook kernel: md8: <hdg8><hde8> array superblock: Feb 21 10:39:10 rook kernel: md: SB: (V:0.90.0) ID:<e757cff8.ecb0eea2.2f35c388.563d2419> CT:3c73c9a6 Feb 21 10:39:10 rook kernel: md: L1 S04194688 ND:2 RD:2 md8 LO:0 CS:4096 Feb 21 10:39:10 rook kernel: md: UT:3c73faff ST:0 AD:2 WD:2 FD:0 SD:0 CSUM:7bcec861 E:0000000a Feb 21 10:39:10 rook kernel: D 0: DISK<N:0,hde8(33,8),R:0,S:6> Feb 21 10:39:10 rook kernel: D 1: DISK<N:1,hdg8(34,8),R:1,S:6> Feb 21 10:39:10 rook kernel: md: THIS: DISK<N:1,hdg8(34,8),R:1,S:6> Feb 21 10:39:10 rook kernel: md: rdev hdg8: O:hdg8, SZ:04194688 F:0 DN:1 <6>md: rdev superblock: Feb 21 10:39:10 rook kernel: md: SB: (V:0.90.0) ID:<e757cff8.ecb0eea2.2f35c388.563d2419> CT:3c73c9a6 Feb 21 10:39:10 rook kernel: md: L1 S04194688 ND:2 RD:2 md8 LO:0 CS:4096 Feb 21 10:39:10 rook kernel: md: UT:3c73faff ST:0 AD:2 WD:2 FD:0 SD:0 CSUM:7bcecccb E:0000000a Feb 21 10:39:10 rook kernel: D 0: DISK<N:0,hde8(33,8),R:0,S:6> Feb 21 10:39:10 rook kernel: D 1: DISK<N:1,hdg8(34,8),R:1,S:6> Feb 21 10:39:10 rook kernel: md: THIS: DISK<N:1,hdg8(34,8),R:1,S:6> Feb 21 10:39:10 rook kernel: md: rdev hde8: O:hde8, SZ:04194688 F:0 DN:0 <6>md: rdev superblock: Feb 21 10:39:10 rook kernel: md: SB: (V:0.90.0) ID:<e757cff8.ecb0eea2.2f35c388.563d2419> CT:3c73c9a6 Feb 21 10:39:10 rook kernel: md: L1 S04194688 ND:2 RD:2 md8 LO:0 CS:4096 Feb 21 10:39:10 rook kernel: md: UT:3c73faff ST:0 AD:2 WD:2 FD:0 SD:0 CSUM:7bceccc8 E:0000000a Feb 21 10:39:10 rook kernel: D 0: DISK<N:0,hde8(33,8),R:0,S:6> Feb 21 10:39:10 rook kernel: D 1: DISK<N:1,hdg8(34,8),R:1,S:6> Feb 21 10:39:10 rook kernel: md: THIS: DISK<N:0,hde8(33,8),R:0,S:6> Feb 21 10:39:10 rook kernel: md:^I********************************** Feb 21 10:39:10 rook kernel: Feb 21 10:39:10 rook kernel: md: cannot remove active disk hdg9 from md9 ... mdctl --detail shows: /dev/md9: Version : 00.90.00 Creation Time : Thu Feb 21 09:56:27 2002 Raid Level : raid1 Size : 4194688 Raid Disks : 2 Total Disks : 2 Preferred Minor : 9 Persistance : Superblock is persistant Update Time : Thu Feb 21 10:45:10 2002 State : dirty, no-errors Active Drives : 2 Working Drives : 2 Failed Drives : 0 Spare Drives : 0 Number Major Minor RaidDisk State 0 33 9 0 active sync /dev/hde9 1 34 9 1 active sync /dev/hdg9 UUID : 4e2f37f4:1e416f0a:65871fe9:19f6e481 Have I done something wrong, or is it a bug in md.c as the message suggests? One other thing, I noticed during my experimentation that if I crash the system then when it comes up again the mirrors are updated. Why does it do this when neither drive in the mirror is guaranteed to be more current than the other? I realise that making sure the mirrors are consistent is a good thing but I find it worrying that it is so keen to overwrite the mirrors with what it believes is the master copy. Maybe I don't understand the process here, perhaps someone could explain briefly what happens in this situation. Thanks, Mark - To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html