- WLUG - wlug.mailman3.com

Re: [Wlug] t-shirts
by Peter Gutowski 21 Oct '02

21 Oct '02

>thought the following two would amuse you guys: > >(1) #define QUESTION ((bb) || !(bb)) > There's a lot of truth in that. ;) -- Peter Gutowski <peter(a)linuxchamps.com> // tel.: (413) 531-0123 "When in company, put not your hands to any part of the body not usually discovered." --George Washington, _Rules for Civility and Decent Behavior_

1 0

t-shirts
by doug waud 21 Oct '02

21 Oct '02

Hi all I got a catalog from Computergear.com which offered a variety of T-shirts with various incriptions. I thought the following two would amuse you guys: (1) #define QUESTION ((bb) || !(bb)) and (2) The box said "Requires Windows 98 or better" So I installed Linux. doug

1 0

Re: [Wlug] RH 7.0->7.3 upgrade
by Peter Gutowski 21 Oct '02

21 Oct '02

I'd suggest that you consider upgrading to 8.0. I've been very impressed with the changes in 8.0 primarily in the area of user interface. I've experienced problems with RHL upgrades in the past. But I believe the bulk of those problems owed to the fact that I was attempting to upgrade where the disk setup was just too "tight". Perhaps in contrast to to 7.0, both 7.3 and 8.0 put a lot of files into /usr/share. You'll may make things easier for yourself if /usr/share is on its own partition. Aside from the be prepared for a general tightening of security. If you use sendmail, you'll probably have to add a "sendmail: ALL" into /etc/hosts.allow as the default is to only do mail handling from localhost. RHL 8.0 uses apache 2.x whereas RHL7.3 still uses the 1.3.x versions. Having installations on hard disks with enough hard drive space has made both upgrades, 7.3 and 8.0, pretty painless. As Charles Anderson ;) may likely suggest to you, be sure to read (and digest) the README files on the install disks... probably before you start to alleviate too many surprizes. (Foolish boy that I was, I *didn't*. And to my embarassment, he [rightfully] rubbed my nose in it. But, hey, I learned my lesson.) FYI, this may not be totally meaningful without know how much and just what exactly in installed. But, that said, I'd characterize my installation as medium -- neither slim nor fat. Here's some pertinent partition usages: Filesystem 1K Blocks Used Available % Mounted on /dev/hda3 497861 80662 391495 18% / /dev/hda1 31079 6419 23056 22% /boot /dev/hda11 2063504 98612 1860072 6% /home /dev/hda7 2063504 1209760 748924 62% /usr /dev/hda9 521748 113052 382192 23% /usr/local /dev/hda8 2063504 729108 1229576 38% /usr/share /dev/hda10 521748 154348 340896 32% /usr/src /dev/hda5 497829 76114 396013 17% /var -PG On 10/18/2002 9:53 AM, Richard Goodman <dick(a)goodman1.net> wrote: >I have four RH servers, two 7.0 and two new 7.3 servers just put up >last 6 >weeks or less >How painless would an upgrade of the older servers from 7.0->7.3 >be? Any >surprises I should know about? Any comments or advice? I've never >done a >version upgrade before. > >I already have a CD with the most important security upgrades I used >on the >7.3 servers after I had worm (Slapper/Cinik) problems. > >Dick > > Richard Goodman dick(a)goodman1.net > > > > >_______________________________________________ >Wlug mailing list >Wlug(a)mail.wlug.org >http://mail.wlug.org/mailman/listinfo/wlug > >

6 7

OS X Firewall? (#2)
by Richard Goodman 21 Oct '02

21 Oct '02

>I would run a packet sniffer (ethereal, tcpdump, etc) on the Linux box >and see what the iBook is putting out BTW the iBook is running 10.2 (brand new) Could not check the ipfw list as it appears that we don't currently have administrator privileges on the iBook. checking the preferences/sharing/firewall showed the firewall off, however I was concerned about the following entries from the iBook's /var/msg/system.log: IP packet filtering initialized, divert enabled, rule-based forwarding enabled, default to accept, logging disabled IP firewall loaded arplookup <IP of my linux box> failed: host is not on localnetwork I have never run a packet sniffer before, so cannot interpret it, but I fired up tcpdump and did a) ping yahoo.com b) attempt to load yahoo.com in IE5 and got the following two dumps (assume I've snipped enough) tcpdump host 192.168.1.49 Kernel filter, protocol ALL, datagram packet socket tcpdump: listening on all devices 15:55:16.232303 eth1 < host49.goodman1.net.49174 > bach.goodman1.net.domain: 49847+ A? yahoo.com. (2 7) 15:55:16.373034 eth1 > bach.goodman1.net.domain > host49.goodman1.net.49174: 49847* 2/5/5 A w1.rc.vi p.dcx.yahoo.com, A w1.rc.vip.scd.yahoo.com (229) 15:55:16.476477 eth1 < host49.goodman1.net > w1.rc.vip.dcx.yahoo.com: icmp: echo request 15:55:17.476548 eth1 < host49.goodman1.net > w1.rc.vip.dcx.yahoo.com: icmp: echo request 15:55:18.476633 eth1 < host49.goodman1.net > w1.rc.vip.dcx.yahoo.com: icmp: echo request 15:55:19.476745 eth1 < host49.goodman1.net > w1.rc.vip.dcx.yahoo.com: icmp: echo request 15:55:20.476828 eth1 < host49.goodman1.net > w1.rc.vip.dcx.yahoo.com: icmp: echo request 15:55:21.476890 eth1 < host49.goodman1.net > w1.rc.vip.dcx.yahoo.com: icmp: echo request 15:55:22.476949 eth1 < host49.goodman1.net > w1.rc.vip.dcx.yahoo.com: icmp: echo request 15:55:23.477008 eth1 < host49.goodman1.net > w1.rc.vip.dcx.yahoo.com: icmp: echo request 15:55:24.477084 eth1 < host49.goodman1.net > w1.rc.vip.dcx.yahoo.com: icmp: echo request <<continued similarly many more lines> tcpdump host 192.168.1.49 Kernel filter, protocol ALL, datagram packet socket tcpdump: listening on all devices 16:01:00.340200 eth1 < host49.goodman1.net.49174 > bach.goodman1.net.domain: 45963+ A? www.yahoo.com . (31) 16:01:00.558192 eth1 > bach.goodman1.net.domain > host49.goodman1.net.49174: 45963 13/10/3 CNAME www .yahoo.akadns.net., A www9.dcx.yahoo.com, A w9.dcx.yahoo.com, (504) 16:01:00.563859 eth1 < host49.goodman1.net.49153 > www9.dcx.yahoo.com.www: S 1383754426:1383754426(0 ) win 32768 <mss 1460,nop,wscale 0,nop,nop,timestamp 8687 0> (DF) 16:01:01.247337 eth1 < host49.goodman1.net.49153 > w9.dcx.yahoo.com.www: S 2642071908:2642071908(0) win 32768 <mss 1460,nop,wscale 0,nop,nop,timestamp 8688 0> (DF) 16:01:01.962006 eth1 < host49.goodman1.net.49153 > w3.dcx.yahoo.com.www: S 3424625619:3424625619(0) win 32768 <mss 1460,nop,wscale 0,nop,nop,timestamp 8689 0> (DF) 16:01:02.719348 eth1 < host49.goodman1.net.49153 > www10.dcx.yahoo.com.www: S 715459341:715459341(0) win 32768 <mss 1460,nop,wscale 0,nop,nop,timestamp 8691 0> (DF) 16:01:03.433706 eth1 < host49.goodman1.net.49153 > w2.dcx.yahoo.com.www: S 3613744425:3613744425(0) win 32768 <mss 1460,nop,wscale 0,nop,nop,timestamp 8692 0> (DF) 16:01:04.115338 eth1 < host49.goodman1.net.49153 > w6.dcx.yahoo.com.www: S 941366980:941366980(0) wi n 32768 <mss 1460,nop,wscale 0,nop,nop,timestamp 8694 0> (DF) 16:01:04.796809 eth1 < host49.goodman1.net.49153 > w8.dcx.yahoo.com.www: S 1223626321:1223626321(0) win 32768 <mss 1460,nop,wscale 0,nop,nop,timestamp 8695 0> (DF) 16:01:05.480085 eth1 < host49.goodman1.net.49153 > w1.dcx.yahoo.com.www: S 1755119059:1755119059(0) win 32768 <mss 1460,nop,wscale 0,nop,nop,timestamp 8696 0> (DF) 16:01:05.550034 eth1 > arp who-has host49.goodman1.net tell localhost.localdomain (0:80:19:35:ad:39) 16:01:05.550329 eth1 < arp reply host49.goodman1.net is-at 0:3:93:c5:39:7c (0:80:19:35:ad:39) 16:01:06.163479 eth1 < host49.goodman1.net.49153 > www7.dcx.yahoo.com.www: S 2895506991:2895506991(0 ) win 32768 <mss 1460,nop,wscale 0,nop,nop,timestamp 8698 0> (DF) 16:01:06.846666 eth1 < host49.goodman1.net.49153 > www8.dcx.yahoo.com.www: S 3434260281:3434260281(0 ) win 32768 <mss 1460,nop,wscale 0,nop,nop,timestamp 8699 0> (DF) 16:01:07.529897 eth1 < host49.goodman1.net.49155 > www9.dcx.yahoo.com.www: S 2654995975:2654995975(0 ) win 32768 <mss 1460,nop,wscale 0,nop,nop,timestamp 8701 0> (DF) 16:01:09.379617 eth1 < host49.goodman1.net.49155 > w9.dcx.yahoo.com.www: S 607986242:607986242(0) wi n 32768 <mss 1460,nop,wscale 0,nop,nop,timestamp 8704 0> (DF) 16:01:11.231084 eth1 < host49.goodman1.net.49155 > w3.dcx.yahoo.com.www: S 1683897864:1683897864(0) win 32768 <mss 1460,nop,wscale 0,nop,nop,timestamp 8708 0> (DF) 16:01:13.079138 eth1 < host49.goodman1.net.49155 > www10.dcx.yahoo.com.www: S 3195269927:3195269927( 0) win 32768 <mss 1460,nop,wscale 0,nop,nop,timestamp 8712 0> (DF) 16:01:14.929941 eth1 < host49.goodman1.net.49155 > w2.dcx.yahoo.com.www: S 1831211410:1831211410(0) win 32768 <mss 1460,nop,wscale 0,nop,nop,timestamp 8715 0> (DF) 16:01:16.778674 eth1 < host49.goodman1.net.49155 > w6.dcx.yahoo.com.www: S 3961536773:3961536773(0) win 32768 <mss 1460,nop,wscale 0,nop,nop,timestamp 8719 0> (DF) 16:01:18.628462 eth1 < host49.goodman1.net.49155 > w8.dcx.yahoo.com.www: S 4286238440:4286238440(0) win 32768 <mss 1460,nop,wscale 0,nop,nop,timestamp 8723 0> (DF) Does this provide enough information? Dick

4 3

OS X firewall ?
by Richard Goodman 20 Oct '02

20 Oct '02

I put the question to the list because I think its related enough to be of interest. My wife just got a top-of-the-line iBook with OS X from school. Connects to the network at school instantly as it should. (I am brand new on OS X) At home I run an network based on a RH7.0 box with IpMasq and some servers going to a static-IP DSL line. About 10 machines, mixed Win and Mac, mixed static and DHCP. When she starts up the iBook: a) the DHCP server on the Linux box shows the normal DHCPREQUEST and DHCPACK lines. b) the Network panel on the iBook shows all the values I would expect to have been handed off by DHCP, 192.168.1.x IP, 255.255.255.0 mask, 192.168.1.1 gateway c) but unable to connect to the internet I found "Terminal" and was able to: d) ping the linux box e) do a nslookup against the name server on the linux box, resolving outside domain names f) bring up web pages running on the Apache server on the linux box But I don't seem to be able to get outside I thought the first thing to try would be to disable the IP Firewall that's being started on the iBook, but haven't been able to figure out how (or where its files are). BTW I run a fairly strict firewall on the linux box and the log shows no hits related to the iBook attempting to get outside. Or I could be totally off base, in which case I would be open to other avenues towards fixing this. Less related: There is an Apple Select 360 appletalk laserwriter on the network, connected thru an Asante appletalk/ethernet bridge which my wife has used with her G3. She can select it through the chooser on the iBook, and we can read and set printer config info, but although everything appears normal when printing for an application in OS9 classic, nothing gets to the printer (and no blinking green light indicating data transfer). Dick

2 1

Re: [Wlug] RH 7.0->7.3 upgrade
by Peter Gutowski 18 Oct '02

18 Oct '02

On 10/18/2002 1:23 PM, Wes Allen <wallen(a)charter.net> wrote: >On Friday 18 October 2002 11:03, Peter Gutowski wrote: >> I'd suggest that you consider upgrading to 8.0. I've been very >>impressed with the........ ...snip... >Is the php module ready for 2.x? I've been thinking about giving >RH 8.0 a try >to see if I can make use of my usb ports! RHL8.0 includes PHP 4.2.2, plus various modules (libphp4.so for apache, imap, mysql, etc....) You might need to rework portions of the /etc/php.ini file, but it seems to be a straight shot. -PG

2 1

RH 7.0->7.3 upgrade
by Richard Goodman 18 Oct '02

18 Oct '02

I have four RH servers, two 7.0 and two new 7.3 servers just put up last 6 weeks or less How painless would an upgrade of the older servers from 7.0->7.3 be? Any surprises I should know about? Any comments or advice? I've never done a version upgrade before. I already have a CD with the most important security upgrades I used on the 7.3 servers after I had worm (Slapper/Cinik) problems. Dick Richard Goodman dick(a)goodman1.net

3 2

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