October 2002 - WLUG - wlug.mailman3.com

Re: duplicate entry in mdstat with RAID-5
by Neil Brown 18 Oct '02

18 Oct '02

On Thursday October 17, karl(a)mail.accusense.com wrote: > > Can someone please help me fix this problem? I don't know if my data is > safe at the moment. > > > I have double entries for hde1 and hde in /proc/mdstat. The problem arose > when i did a raidhotadd for /dev/hde then again for /dev/hde1. Doh. Is > this a problem? How do i fix it? I would like to be using hde1, hdf1, > hdc1 > > The problem arose when the 60GB /dev/hde failed. I replaced it with an > 80GB drive. > > I am running redhat 7.2 with their kernel 2.4.9-31 > > > # cat /proc/mdstat > Personalities : [raid5] > read_ahead 1024 sectors > md0 : active raid5 hde1[3] hde[2] hdf1[1] hdc1[0] > 120102912 blocks level 5, 64k chunk, algorithm 0 [3/3] [UUU] > > unused devices: <none> So the raid is made of hdc1 hdf1 hde, with hde1 as a hot spare.. Not what you want. raidhotremove /dev/md0 /dev/hde1 raidsetfaulty /dev/md0 /dev/hde raidhotremove /dev/md0 /dev/hde Repartition hde correctly, the partition table will have been corrupted. raidhotadd /dev/md0 /dev/hde1 and don't make a typo this time :-) NeilBrown > > ---- > # fdisk -l /dev/hde > > Disk /dev/hde: 16 heads, 63 sectors, 155061 cylinders > Units = cylinders of 1008 * 512 bytes > > Disk /dev/hde doesn't contain a valid partition table > ----- > > # fdisk -l /dev/hdc > Disk /dev/hdc: 16 heads, 63 sectors, 119150 cylinders > Units = cylinders of 1008 * 512 bytes > > Device Boot Start End Blocks Id System > /dev/hdc1 * 1 119150 60051568+ fd Linux raid autodetect > > ---- > # fdisk -l /dev/hdf > Disk /dev/hdf: 16 heads, 63 sectors, 119150 cylinders > Units = cylinders of 1008 * 512 bytes > > Device Boot Start End Blocks Id System > /dev/hdf1 1 119150 60051568+ fd Linux raid autodetect > > > -- > /var/log/messages file > when i tried to remove /dev/hde with raidhotremove > > > Oct 17 22:17:15 data kernel: md: trying to remove hde from md0 ... > Oct 17 22:17:15 data kernel: md: bug in file md.c, line 2344 > Oct 17 22:17:15 data kernel: > Oct 17 22:17:15 data kernel: md:^I********************************** > Oct 17 22:17:15 data kernel: md:^I* <COMPLETE RAID STATE PRINTOUT> * > Oct 17 22:17:15 data kernel: md:^I********************************** > Oct 17 22:17:15 data kernel: md0: <hde1><hde><hdf1><hdc1> array > superblock: > Oct 17 22:17:15 data kernel: md: SB: (V:0.90.0) > ID:<a595074f.25e94a64.bec4b48a.e946a7b6> CT:3bdeb7e7 > Oct 17 22:17:15 data kernel: md: L5 S60051456 ND:4 RD:3 md0 LO:0 > CS:65536 > Oct 17 22:17:15 data kernel: md: UT:3daf6d69 ST:0 AD:3 WD:4 FD:0 SD:1 > CSUM:99d87466 E:0000009c > Oct 17 22:17:15 data kernel: D 0: DISK<N:0,hdc1(22,1),R:0,S:6> > Oct 17 22:17:15 data kernel: D 1: DISK<N:1,hdf1(33,65),R:1,S:6> > Oct 17 22:17:15 data kernel: D 2: DISK<N:2,hde(33,0),R:2,S:6> > Oct 17 22:17:15 data kernel: D 3: DISK<N:3,hde1(33,1),R:3,S:0> > Oct 17 22:17:15 data kernel: md: THIS: DISK<N:3,hde1(33,1),R:3,S:0> > Oct 17 22:17:15 data kernel: md: rdev hde1: O:hde1, SZ:60051456 F:0 DN:3 > md: rdev superblock: > Oct 17 22:17:15 data kernel: md: SB: (V:0.90.0) > ID:<a595074f.25e94a64.bec4b48a.e946a7b6> CT:3bdeb7e7 > Oct 17 22:17:15 data kernel: md: L5 S60051456 ND:4 RD:3 md0 LO:0 > CS:65536 > Oct 17 22:17:15 data kernel: md: UT:3daf6d69 ST:0 AD:3 WD:4 FD:0 SD:1 > CSUM:99d874aa E:0000009c > Oct 17 22:17:15 data kernel: D 0: DISK<N:0,hdc1(22,1),R:0,S:6> > Oct 17 22:17:15 data kernel: D 1: DISK<N:1,hdf1(33,65),R:1,S:6> > Oct 17 22:17:15 data kernel: D 2: DISK<N:2,hde(33,0),R:2,S:6> > Oct 17 22:17:15 data kernel: D 3: DISK<N:3,hde1(33,1),R:3,S:0> > Oct 17 22:17:15 data kernel: md: THIS: DISK<N:3,hde1(33,1),R:3,S:0> > Oct 17 22:17:15 data kernel: md: rdev hde: O:hde, SZ:78150656 F:0 DN:2 md: > rdev superblock: > Oct 17 22:17:15 data kernel: md: SB: (V:0.90.0) > ID:<a595074f.25e94a64.bec4b48a.e946a7b6> CT:3bdeb7e7 > Oct 17 22:17:15 data kernel: md: L5 S60051456 ND:4 RD:3 md0 LO:0 > CS:65536 > Oct 17 22:17:15 data kernel: md: UT:3daf6d69 ST:0 AD:3 WD:4 FD:0 SD:1 > CSUM:99d874ad E:0000009c > > Oct 17 22:17:15 data kernel: D 0: DISK<N:0,hdc1(22,1),R:0,S:6> > Oct 17 22:17:15 data kernel: D 1: DISK<N:1,hdf1(33,65),R:1,S:6> > Oct 17 22:17:15 data kernel: D 2: DISK<N:2,hde(33,0),R:2,S:6> > Oct 17 22:17:15 data kernel: D 3: DISK<N:3,hde1(33,1),R:3,S:0> > Oct 17 22:17:15 data kernel: md: THIS: DISK<N:2,hde(33,0),R:2,S:6> > Oct 17 22:17:15 data kernel: md: rdev hdf1: O:hdf1, SZ:60051456 F:0 DN:1 > md: rdev superblock: > Oct 17 22:17:15 data kernel: md: SB: (V:0.90.0) > ID:<a595074f.25e94a64.bec4b48a.e946a7b6> CT:3bdeb7e7 > Oct 17 22:17:15 data kernel: md: L5 S60051456 ND:4 RD:3 md0 LO:0 > CS:65536 > Oct 17 22:17:15 data kernel: md: UT:3daf6d69 ST:0 AD:3 WD:4 FD:0 SD:1 > CSUM:99d874ec E:0000009c > Oct 17 22:17:15 data kernel: D 0: DISK<N:0,hdc1(22,1),R:0,S:6> > Oct 17 22:17:15 data kernel: D 1: DISK<N:1,hdf1(33,65),R:1,S:6> > Oct 17 22:17:15 data kernel: D 2: DISK<N:2,hde(33,0),R:2,S:6> > Oct 17 22:17:15 data kernel: D 3: DISK<N:3,hde1(33,1),R:3,S:0> > Oct 17 22:17:15 data kernel: md: THIS: DISK<N:1,hdf1(33,65),R:1,S:6> > Oct 17 22:17:15 data kernel: md: rdev hdc1: O:hdc1, SZ:60051456 F:0 DN:0 > md: rdev superblock: > Oct 17 22:17:15 data kernel: md: SB: (V:0.90.0) > ID:<a595074f.25e94a64.bec4b48a.e946a7b6> CT:3bdeb7e7 > Oct 17 22:17:15 data kernel: md: L5 S60051456 ND:4 RD:3 md0 LO:0 > CS:65536 > Oct 17 22:17:15 data kernel: md: UT:3daf6d69 ST:0 AD:3 WD:4 FD:0 SD:1 > CSUM:99d8749f E:0000009c > Oct 17 22:17:15 data kernel: D 0: DISK<N:0,hdc1(22,1),R:0,S:6> > Oct 17 22:17:15 data kernel: D 1: DISK<N:1,hdf1(33,65),R:1,S:6> > Oct 17 22:17:15 data kernel: D 2: DISK<N:2,hde(33,0),R:2,S:6> > Oct 17 22:17:15 data kernel: D 3: DISK<N:3,hde1(33,1),R:3,S:0> > Oct 17 22:17:15 data kernel: md: THIS: DISK<N:0,hdc1(22,1),R:0,S:6> > Oct 17 22:17:15 data kernel: md:^I********************************** > Oct 17 22:17:15 data kernel: > Oct 17 22:17:15 data kernel: md: cannot remove active disk hde from md0 > ... > Oct 17 22:23:11 data kernel: md: interrupting MD-thread pid 130 > Oct 17 22:23:11 data kernel: md: raid5d(130) flushing signals. > Oct 17 22:23:11 data kernel: md: marking sb clean... > Oct 17 22:23:11 data kernel: md: updating md0 RAID superblock on device > Oct 17 22:23:11 data kernel: md: hde1 [events: 0000009d](write) hde1's sb > offset: 60051456 > Oct 17 22:23:11 data kernel: md: hde [events: 0000009d](write) hde's sb > offset: 78150656 > Oct 17 22:23:11 data kernel: md: hdf1 [events: 0000009d](write) hdf1's sb > offset: 60051456 > Oct 17 22:23:11 data kernel: md: hdc1 [events: 0000009d](write) hdc1's sb > offset: 60051456 > Oct 17 22:23:11 data kernel: md: md0 stopped. > Oct 17 22:23:11 data kernel: md: unbind<hde1,3> > Oct 17 22:23:11 data kernel: md: export_rdev(hde1) > Oct 17 22:23:11 data kernel: md: unbind<hde,2> > Oct 17 22:23:11 data kernel: md: export_rdev(hde) > Oct 17 22:23:11 data kernel: md: unbind<hdf1,1> > Oct 17 22:23:11 data kernel: md: export_rdev(hdf1) > Oct 17 22:23:11 data kernel: md: unbind<hdc1,0> > Oct 17 22:23:11 data kernel: md: export_rdev(hdc1) > Oct 17 22:28:12 data dhcpd: DHCPREQUEST for 192.168.2.113 from > 00:50:fc:21:77:64 via eth0 > Oct 17 22:29:48 data kernel: (read) hdc1's sb offset: 60051456 [events: > 0000009d] > Oct 17 22:29:48 data kernel: (read) hdf1's sb offset: 60051456 [events: > 0000009d] > Oct 17 22:29:48 data kernel: (read) hde's sb offset: 78150656 [events: > 0000009d] > Oct 17 22:29:49 data kernel: (read) hde1's sb offset: 60051456 [events: > 0000009d] > Oct 17 22:29:49 data kernel: md: autorun ... > Oct 17 22:29:49 data kernel: md: considering hde1 ... > Oct 17 22:29:49 data kernel: md: adding hde1 ... > Oct 17 22:29:49 data kernel: md: adding hde ... > Oct 17 22:29:49 data kernel: md: adding hdf1 ... > Oct 17 22:29:49 data kernel: md: adding hdc1 ... > Oct 17 22:29:49 data kernel: md: created md0 > Oct 17 22:29:49 data kernel: md: bind<hdc1,1> > Oct 17 22:29:49 data kernel: md: bind<hdf1,2> > Oct 17 22:29:49 data kernel: md: bind<hde,3> > Oct 17 22:29:49 data kernel: md0: WARNING: hde1 appears to be on the same > physical disk as hde. True > Oct 17 22:29:49 data kernel: protection against single-disk failure > might be compromised. > Oct 17 22:29:49 data kernel: md: bind<hde1,4> > Oct 17 22:29:49 data kernel: md: running: <hde1><hde><hdf1><hdc1> > Oct 17 22:29:49 data kernel: md: hde1's event counter: 0000009d > Oct 17 22:29:49 data kernel: md: hde's event counter: 0000009d > Oct 17 22:29:49 data kernel: md: hdf1's event counter: 0000009d > Oct 17 22:29:49 data kernel: md: hdc1's event counter: 0000009d > Oct 17 22:29:49 data kernel: md0: max total readahead window set to 512k > Oct 17 22:29:49 data kernel: md0: 2 data-disks, max readahead per > data-disk: 256k > Oct 17 22:29:49 data kernel: raid5: spare disk hde1 > Oct 17 22:29:49 data kernel: raid5: device hde operational as raid disk 2 > Oct 17 22:29:49 data kernel: raid5: device hdf1 operational as raid disk 1 > Oct 17 22:29:49 data kernel: raid5: device hdc1 operational as raid disk 0 > Oct 17 22:29:49 data kernel: raid5: allocated 3291kB for md0 > Oct 17 22:29:49 data kernel: raid5: raid level 5 set md0 active with 3 out > of 3 devices, algorithm 0 > Oct 17 22:29:49 data kernel: RAID5 conf printout: > Oct 17 22:29:49 data kernel: --- rd:3 wd:3 fd:0 > Oct 17 22:29:49 data kernel: disk 0, s:0, o:1, n:0 rd:0 us:1 dev:hdc1 > Oct 17 22:29:49 data kernel: disk 1, s:0, o:1, n:1 rd:1 us:1 dev:hdf1 > Oct 17 22:29:49 data kernel: disk 2, s:0, o:1, n:2 rd:2 us:1 dev:hde > Oct 17 22:29:49 data kernel: RAID5 conf printout: > Oct 17 22:29:49 data kernel: --- rd:3 wd:3 fd:0 > Oct 17 22:29:49 data kernel: disk 0, s:0, o:1, n:0 rd:0 us:1 dev:hdc1 > Oct 17 22:29:49 data kernel: disk 1, s:0, o:1, n:1 rd:1 us:1 dev:hdf1 > Oct 17 22:29:49 data kernel: disk 2, s:0, o:1, n:2 rd:2 us:1 dev:hde > Oct 17 22:29:49 data kernel: md: updating md0 RAID superblock on device > Oct 17 22:29:49 data kernel: md: hde1 [events: 0000009e](write) hde1's sb > offset: 60051456 > Oct 17 22:29:49 data kernel: md: hde [events: 0000009e](write) hde's sb > offset: 78150656 > Oct 17 22:29:49 data kernel: md: hdf1 [events: 0000009e](write) hdf1's sb > offset: 60051456 > Oct 17 22:29:49 data kernel: md: hdc1 [events: 0000009e](write) hdc1's sb > offset: 60051456 > Oct 17 22:29:49 data kernel: md: ... autorun DONE. > > > > > > Thanks, > > > -------------------------------------------------------------------- > Karl Hiramoto - Design Engineer > Cambridge Accusense > www.accusense.com > Tel: 978-425-2090 > Toll Free in US: 1-800-313-9271 > Fax: 978-425-4062 > > - > To unsubscribe from this list: send the line "unsubscribe linux-raid" in > the body of a message to majordomo(a)vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html

1 0

duplicate entry in mdstat with RAID-5 (fwd)
by Karl Hiramoto 18 Oct '02

18 Oct '02

Can someone please help me fix this problem? I don't know if my data is safe at the moment. I have double entries for hde1 and hde in /proc/mdstat. The problem arose when i did a raidhotadd for /dev/hde then again for /dev/hde1. Doh. Is this a problem? How do i fix it? I would like to be using hde1, hdf1, hdc1 The problem arose when the 60GB /dev/hde failed. I replaced it with an 80GB drive. I am running redhat 7.2 with their kernel 2.4.9-31 # cat /proc/mdstat Personalities : [raid5] read_ahead 1024 sectors md0 : active raid5 hde1[3] hde[2] hdf1[1] hdc1[0] 120102912 blocks level 5, 64k chunk, algorithm 0 [3/3] [UUU] unused devices: <none> ---- # fdisk -l /dev/hde Disk /dev/hde: 16 heads, 63 sectors, 155061 cylinders Units = cylinders of 1008 * 512 bytes Disk /dev/hde doesn't contain a valid partition table ----- # fdisk -l /dev/hdc Disk /dev/hdc: 16 heads, 63 sectors, 119150 cylinders Units = cylinders of 1008 * 512 bytes Device Boot Start End Blocks Id System /dev/hdc1 * 1 119150 60051568+ fd Linux raid autodetect ---- # fdisk -l /dev/hdf Disk /dev/hdf: 16 heads, 63 sectors, 119150 cylinders Units = cylinders of 1008 * 512 bytes Device Boot Start End Blocks Id System /dev/hdf1 1 119150 60051568+ fd Linux raid autodetect -- /var/log/messages file when i tried to remove /dev/hde with raidhotremove Oct 17 22:17:15 data kernel: md: trying to remove hde from md0 ... Oct 17 22:17:15 data kernel: md: bug in file md.c, line 2344 Oct 17 22:17:15 data kernel: Oct 17 22:17:15 data kernel: md:^I********************************** Oct 17 22:17:15 data kernel: md:^I* <COMPLETE RAID STATE PRINTOUT> * Oct 17 22:17:15 data kernel: md:^I********************************** Oct 17 22:17:15 data kernel: md0: <hde1><hde><hdf1><hdc1> array superblock: Oct 17 22:17:15 data kernel: md: SB: (V:0.90.0) ID:<a595074f.25e94a64.bec4b48a.e946a7b6> CT:3bdeb7e7 Oct 17 22:17:15 data kernel: md: L5 S60051456 ND:4 RD:3 md0 LO:0 CS:65536 Oct 17 22:17:15 data kernel: md: UT:3daf6d69 ST:0 AD:3 WD:4 FD:0 SD:1 CSUM:99d87466 E:0000009c Oct 17 22:17:15 data kernel: D 0: DISK<N:0,hdc1(22,1),R:0,S:6> Oct 17 22:17:15 data kernel: D 1: DISK<N:1,hdf1(33,65),R:1,S:6> Oct 17 22:17:15 data kernel: D 2: DISK<N:2,hde(33,0),R:2,S:6> Oct 17 22:17:15 data kernel: D 3: DISK<N:3,hde1(33,1),R:3,S:0> Oct 17 22:17:15 data kernel: md: THIS: DISK<N:3,hde1(33,1),R:3,S:0> Oct 17 22:17:15 data kernel: md: rdev hde1: O:hde1, SZ:60051456 F:0 DN:3 md: rdev superblock: Oct 17 22:17:15 data kernel: md: SB: (V:0.90.0) ID:<a595074f.25e94a64.bec4b48a.e946a7b6> CT:3bdeb7e7 Oct 17 22:17:15 data kernel: md: L5 S60051456 ND:4 RD:3 md0 LO:0 CS:65536 Oct 17 22:17:15 data kernel: md: UT:3daf6d69 ST:0 AD:3 WD:4 FD:0 SD:1 CSUM:99d874aa E:0000009c Oct 17 22:17:15 data kernel: D 0: DISK<N:0,hdc1(22,1),R:0,S:6> Oct 17 22:17:15 data kernel: D 1: DISK<N:1,hdf1(33,65),R:1,S:6> Oct 17 22:17:15 data kernel: D 2: DISK<N:2,hde(33,0),R:2,S:6> Oct 17 22:17:15 data kernel: D 3: DISK<N:3,hde1(33,1),R:3,S:0> Oct 17 22:17:15 data kernel: md: THIS: DISK<N:3,hde1(33,1),R:3,S:0> Oct 17 22:17:15 data kernel: md: rdev hde: O:hde, SZ:78150656 F:0 DN:2 md: rdev superblock: Oct 17 22:17:15 data kernel: md: SB: (V:0.90.0) ID:<a595074f.25e94a64.bec4b48a.e946a7b6> CT:3bdeb7e7 Oct 17 22:17:15 data kernel: md: L5 S60051456 ND:4 RD:3 md0 LO:0 CS:65536 Oct 17 22:17:15 data kernel: md: UT:3daf6d69 ST:0 AD:3 WD:4 FD:0 SD:1 CSUM:99d874ad E:0000009c Oct 17 22:17:15 data kernel: D 0: DISK<N:0,hdc1(22,1),R:0,S:6> Oct 17 22:17:15 data kernel: D 1: DISK<N:1,hdf1(33,65),R:1,S:6> Oct 17 22:17:15 data kernel: D 2: DISK<N:2,hde(33,0),R:2,S:6> Oct 17 22:17:15 data kernel: D 3: DISK<N:3,hde1(33,1),R:3,S:0> Oct 17 22:17:15 data kernel: md: THIS: DISK<N:2,hde(33,0),R:2,S:6> Oct 17 22:17:15 data kernel: md: rdev hdf1: O:hdf1, SZ:60051456 F:0 DN:1 md: rdev superblock: Oct 17 22:17:15 data kernel: md: SB: (V:0.90.0) ID:<a595074f.25e94a64.bec4b48a.e946a7b6> CT:3bdeb7e7 Oct 17 22:17:15 data kernel: md: L5 S60051456 ND:4 RD:3 md0 LO:0 CS:65536 Oct 17 22:17:15 data kernel: md: UT:3daf6d69 ST:0 AD:3 WD:4 FD:0 SD:1 CSUM:99d874ec E:0000009c Oct 17 22:17:15 data kernel: D 0: DISK<N:0,hdc1(22,1),R:0,S:6> Oct 17 22:17:15 data kernel: D 1: DISK<N:1,hdf1(33,65),R:1,S:6> Oct 17 22:17:15 data kernel: D 2: DISK<N:2,hde(33,0),R:2,S:6> Oct 17 22:17:15 data kernel: D 3: DISK<N:3,hde1(33,1),R:3,S:0> Oct 17 22:17:15 data kernel: md: THIS: DISK<N:1,hdf1(33,65),R:1,S:6> Oct 17 22:17:15 data kernel: md: rdev hdc1: O:hdc1, SZ:60051456 F:0 DN:0 md: rdev superblock: Oct 17 22:17:15 data kernel: md: SB: (V:0.90.0) ID:<a595074f.25e94a64.bec4b48a.e946a7b6> CT:3bdeb7e7 Oct 17 22:17:15 data kernel: md: L5 S60051456 ND:4 RD:3 md0 LO:0 CS:65536 Oct 17 22:17:15 data kernel: md: UT:3daf6d69 ST:0 AD:3 WD:4 FD:0 SD:1 CSUM:99d8749f E:0000009c Oct 17 22:17:15 data kernel: D 0: DISK<N:0,hdc1(22,1),R:0,S:6> Oct 17 22:17:15 data kernel: D 1: DISK<N:1,hdf1(33,65),R:1,S:6> Oct 17 22:17:15 data kernel: D 2: DISK<N:2,hde(33,0),R:2,S:6> Oct 17 22:17:15 data kernel: D 3: DISK<N:3,hde1(33,1),R:3,S:0> Oct 17 22:17:15 data kernel: md: THIS: DISK<N:0,hdc1(22,1),R:0,S:6> Oct 17 22:17:15 data kernel: md:^I********************************** Oct 17 22:17:15 data kernel: Oct 17 22:17:15 data kernel: md: cannot remove active disk hde from md0 ... Oct 17 22:23:11 data kernel: md: interrupting MD-thread pid 130 Oct 17 22:23:11 data kernel: md: raid5d(130) flushing signals. Oct 17 22:23:11 data kernel: md: marking sb clean... Oct 17 22:23:11 data kernel: md: updating md0 RAID superblock on device Oct 17 22:23:11 data kernel: md: hde1 [events: 0000009d](write) hde1's sb offset: 60051456 Oct 17 22:23:11 data kernel: md: hde [events: 0000009d](write) hde's sb offset: 78150656 Oct 17 22:23:11 data kernel: md: hdf1 [events: 0000009d](write) hdf1's sb offset: 60051456 Oct 17 22:23:11 data kernel: md: hdc1 [events: 0000009d](write) hdc1's sb offset: 60051456 Oct 17 22:23:11 data kernel: md: md0 stopped. Oct 17 22:23:11 data kernel: md: unbind<hde1,3> Oct 17 22:23:11 data kernel: md: export_rdev(hde1) Oct 17 22:23:11 data kernel: md: unbind<hde,2> Oct 17 22:23:11 data kernel: md: export_rdev(hde) Oct 17 22:23:11 data kernel: md: unbind<hdf1,1> Oct 17 22:23:11 data kernel: md: export_rdev(hdf1) Oct 17 22:23:11 data kernel: md: unbind<hdc1,0> Oct 17 22:23:11 data kernel: md: export_rdev(hdc1) Oct 17 22:28:12 data dhcpd: DHCPREQUEST for 192.168.2.113 from 00:50:fc:21:77:64 via eth0 Oct 17 22:29:48 data kernel: (read) hdc1's sb offset: 60051456 [events: 0000009d] Oct 17 22:29:48 data kernel: (read) hdf1's sb offset: 60051456 [events: 0000009d] Oct 17 22:29:48 data kernel: (read) hde's sb offset: 78150656 [events: 0000009d] Oct 17 22:29:49 data kernel: (read) hde1's sb offset: 60051456 [events: 0000009d] Oct 17 22:29:49 data kernel: md: autorun ... Oct 17 22:29:49 data kernel: md: considering hde1 ... Oct 17 22:29:49 data kernel: md: adding hde1 ... Oct 17 22:29:49 data kernel: md: adding hde ... Oct 17 22:29:49 data kernel: md: adding hdf1 ... Oct 17 22:29:49 data kernel: md: adding hdc1 ... Oct 17 22:29:49 data kernel: md: created md0 Oct 17 22:29:49 data kernel: md: bind<hdc1,1> Oct 17 22:29:49 data kernel: md: bind<hdf1,2> Oct 17 22:29:49 data kernel: md: bind<hde,3> Oct 17 22:29:49 data kernel: md0: WARNING: hde1 appears to be on the same physical disk as hde. True Oct 17 22:29:49 data kernel: protection against single-disk failure might be compromised. Oct 17 22:29:49 data kernel: md: bind<hde1,4> Oct 17 22:29:49 data kernel: md: running: <hde1><hde><hdf1><hdc1> Oct 17 22:29:49 data kernel: md: hde1's event counter: 0000009d Oct 17 22:29:49 data kernel: md: hde's event counter: 0000009d Oct 17 22:29:49 data kernel: md: hdf1's event counter: 0000009d Oct 17 22:29:49 data kernel: md: hdc1's event counter: 0000009d Oct 17 22:29:49 data kernel: md0: max total readahead window set to 512k Oct 17 22:29:49 data kernel: md0: 2 data-disks, max readahead per data-disk: 256k Oct 17 22:29:49 data kernel: raid5: spare disk hde1 Oct 17 22:29:49 data kernel: raid5: device hde operational as raid disk 2 Oct 17 22:29:49 data kernel: raid5: device hdf1 operational as raid disk 1 Oct 17 22:29:49 data kernel: raid5: device hdc1 operational as raid disk 0 Oct 17 22:29:49 data kernel: raid5: allocated 3291kB for md0 Oct 17 22:29:49 data kernel: raid5: raid level 5 set md0 active with 3 out of 3 devices, algorithm 0 Oct 17 22:29:49 data kernel: RAID5 conf printout: Oct 17 22:29:49 data kernel: --- rd:3 wd:3 fd:0 Oct 17 22:29:49 data kernel: disk 0, s:0, o:1, n:0 rd:0 us:1 dev:hdc1 Oct 17 22:29:49 data kernel: disk 1, s:0, o:1, n:1 rd:1 us:1 dev:hdf1 Oct 17 22:29:49 data kernel: disk 2, s:0, o:1, n:2 rd:2 us:1 dev:hde Oct 17 22:29:49 data kernel: RAID5 conf printout: Oct 17 22:29:49 data kernel: --- rd:3 wd:3 fd:0 Oct 17 22:29:49 data kernel: disk 0, s:0, o:1, n:0 rd:0 us:1 dev:hdc1 Oct 17 22:29:49 data kernel: disk 1, s:0, o:1, n:1 rd:1 us:1 dev:hdf1 Oct 17 22:29:49 data kernel: disk 2, s:0, o:1, n:2 rd:2 us:1 dev:hde Oct 17 22:29:49 data kernel: md: updating md0 RAID superblock on device Oct 17 22:29:49 data kernel: md: hde1 [events: 0000009e](write) hde1's sb offset: 60051456 Oct 17 22:29:49 data kernel: md: hde [events: 0000009e](write) hde's sb offset: 78150656 Oct 17 22:29:49 data kernel: md: hdf1 [events: 0000009e](write) hdf1's sb offset: 60051456 Oct 17 22:29:49 data kernel: md: hdc1 [events: 0000009e](write) hdc1's sb offset: 60051456 Oct 17 22:29:49 data kernel: md: ... autorun DONE. Thanks, -------------------------------------------------------------------- Karl Hiramoto - Design Engineer Cambridge Accusense www.accusense.com Tel: 978-425-2090 Toll Free in US: 1-800-313-9271 Fax: 978-425-4062

1 0

usb 2.0 backward compatable? yes?
by Wesley Allen 16 Oct '02

16 Oct '02

Hi gang, I did some research on whether or not usb 2.0 card (pci and pcmcia) would work with the 2.4 kernel. If I read right, the answer is yes, they will be seen as usb 1.0 and be able to use those drivers. Is this correct? Now, if I've got problem with my stupid bios not assigning a correct irq on my built-in usb controller, will this issue pan over to a pcmcia card as well? I've got no problem getting a new card for doing this, as I'd eventually want to have usb 2.0 devices come the 2.6 (3.0?) kernel anyway. I'd just be doing it sooner (and if mandrake figures out how to circumvent my bios, I'll have 4 or 6 ports! :-) ). Wes

2 2

RH 8
by Aramico 16 Oct '02

16 Oct '02

Till now, i still get the problem in downloading RH 8 in several diffrent places. Can somebody tell me where can i download it ? All available sites are using identification's login for now.. ..while the other could not be touched using wget...... ;( Thanks!

3 2

Re: [Wlug] Old RAM (OT)
by Thomas Carey 14 Oct '02

14 Oct '02

1 0

Old RAM (OT)
by Tim Trachimowicz 14 Oct '02

14 Oct '02

Hey folks! Since you're probably the biggest group of people I know that might have unused hardware floating around, I figured I'd see if you guys can help me out. I'm searching for some RAM for an older PC I have. Specifically, it's 66mhz SDRAM for a Compaq Deskpro that I'm trying to turn into something useful. Anyways, I was wondeirng if any of you guys might have a DIMM or two flaoting around that's gathering dust (I'll pay you for it) or might know where I can find some on the cheap, before I hit up any of the big guys that I know have the RAM (but at a premium price). Thanks, Tim

2 1

Cinik worm (mod_ssl)
by Richard Goodman 13 Oct '02

13 Oct '02

I have two rather new RH7.3 servers, which I installed without any patches (dumb- had never installed patches before). A couple of weeks ago both got infected with [different] strains of the Cinik (mod_ssl) worm. On machine "A" I shut down Apache for about a week, and left "B" running. On 10/5/02 I downloaded and installed RH patches for apache, bind, glibc, openssh, openssl, php and mod_ssl on both machines. I deleted the cinik stuff from /tmp. Machine "B" has been worm-free since. Cinik reappeared on machine "A" overnight last night -- process running and the usual suspect files back in /tmp. I happened to look in /var/log/cron (on the subject of cron I am rather clueless) and saw the following suspicious entries in the time frame when I believe the worm reappeared: Oct 13 05:20:00 archive3 CROND[25572]: (root) CMD (/usr/bin/mrtg /etc/mrtg/mrtg.cfg) Oct 13 05:20:00 archive3 CROND[25573]: (root) CMD (/usr/lib/sa/sa1 1 1) Oct 13 05:25:00 archive3 CROND[25577]: (root) CMD (/usr/bin/mrtg /etc/mrtg/mrtg.cfg) Oct 13 05:26:34 archive3 crontab[25622]: (apache) REPLACE (apache) Oct 13 05:27:00 archive3 crond[858]: (apache) RELOAD (cron/apache) Oct 13 05:27:29 archive3 crontab[25630]: (apache) REPLACE (apache) Oct 13 05:27:29 archive3 crontab[25635]: (apache) REPLACE (apache) Oct 13 05:27:29 archive3 crontab[25640]: (apache) REPLACE (apache) Oct 13 05:27:29 archive3 crontab[25645]: (apache) REPLACE (apache) Oct 13 05:28:01 archive3 crond[858]: (apache) RELOAD (cron/apache) Oct 13 05:30:00 archive3 CROND[25666]: (root) CMD (/usr/bin/mrtg /etc/mrtg/mrtg.cfg) Oct 13 05:30:00 archive3 CROND[25667]: (root) CMD (/usr/lib/sa/sa1 1 1) Oct 13 05:35:00 archive3 CROND[25670]: (root) CMD (/usr/bin/mrtg /etc/mrtg/mrtg.cfg) Any suggestions as to what the log entries mean (i.e. who did what to Apache?), and why cinik has reappeared? Also, can someone point me towards a resource about cron so that I may become less clueless? Thanks, Dick

2 1

Installfest Media...
by Keller, Tim 12 Oct '02

12 Oct '02

So currently I've got ISO's for Redhat 7.3/8.0 and Mandrake 8.0 (disks 1 and 2, but not the 3rd internationalization disk) What other distributions would people like me to make some copies of? Also, I'm going to put together my obligatory Disk-o-everything. As a side note, I personally think it would be cool if we could have a repository of WLUG goodies, but I know there'd be some logistics around that. So far this is what's going to be on it. (unless otherwise noted, assume I'll be grabbing the latest) Office Stuff: OpenOffice Gimpprint Kernel Stuff: Latest Stable Kernel Sources Latest Unstable Kernel Sources (would like some input here) Sound Stuff: alsa free OSS drivers lame bladeenc cdparanoia grip ogg-vorbis ultramaster xmms xmms plugins Video: Nvidia Drivers (I'll grab everything, for every version they've got) (would like some input here) Video Tools: Cinelerra (and all the stuff that comes with it like Xmovie, etc) (input please!) Burning Tools: cdlabelgen cdrtools gcombust gtoaster xcdroast Browsers: Mozilla Phoenix Opera Netscape plugins video-players: xine mplayer libdvdcss region-changer (would like some input here) Games: Deluxe Xkobo Mame (help...)

4 3

rpm build error
by Bill Mills-Curran 11 Oct '02

11 Oct '02

I just rebuilt apache from the RH 8.0 source rpm. The compilation succeeded, but the rpm failed with the following error message: Checking for unpackaged file(s): /usr/lib/rpm/check-files /home/bcurran/tmp/rpmBuild/httpd-root error: Installed (but unpackaged) file(s) found: /etc/httpd/conf/mime.types /usr/bin/apr-config /usr/bin/apu-config /usr/lib/APRVARS <snip-more files> RPM build errors: Installed (but unpackaged) file(s) found: /etc/httpd/conf/mime.types /usr/bin/apr-config /usr/bin/apu-config /usr/lib/APRVARS <snip-more files> Neither the modified source nor the binary rpm were generated. It looks like these files made it into the temporary install area just prior to generating the packages, and they should not have been there. Is there an option I should be using to make the install tree "right"? I know I can modify the spec file to wildcard include everything in the install directories, but that doesn't seem right. My command: "rpmbuild -ba httpd.spec". TIA, Bill

2 3

:( - Need Sendmail Setting!
by Aramico 11 Oct '02

11 Oct '02

Hi all, Can u please tell me if you have ever installed and configured sendmail bye your self ? I mean, please tell me step by step the thing have you done for it in order to get sendmail running properly ? Of course including all its need. the available tutorial not helping me so much, i need your detail.. Plz... Thanks...

1 0