Re: autodetect help needed
At 18:08 06.10.99 -0400, Gerrish, Robert wrote: I need some help getting autodetect working. I've tried everything and am probably just missing some little piece. FDC 0 is a post-1991 82077 md driver 0.90.0 MAX_MD_DEVS=256, MAX_REAL=12 linear personality registered raid0 personality registered raid1 personality registered raid5 personality registered raid5: measuring checksumming speed raid5: MMX detected, trying high-speed MMX checksum routines pII_mmx : 1001.649 MB/sec p5_mmx: 1045.464 MB/sec 8regs : 774.573 MB/sec 32regs: 411.480 MB/sec using fastest function: p5_mmx (1045.464 MB/sec) (scsi0) Adaptec AHA-294X Ultra2 SCSI host adapter found at PCI 11/0 (scsi0) Wide Channel, SCSI ID=11, 32/255 SCBs (scsi0) Downloading sequencer code... 374 instructions downloaded scsi0 : Adaptec AHA274x/284x/294x (EISA/VLB/PCI-Fast SCSI) 5.1.19/3.2.4 Adaptec AHA-294X Ultra2 SCSI host adapter scsi : 1 host. (scsi0:0:0:0) Synchronous at 40.0 Mbyte/sec, offset 31. Vendor: QUANTUM Model: QM318000TD-SW Rev: N1B0 Type: Direct-Access ANSI SCSI revision: 02 Detected scsi disk sda at scsi0, channel 0, id 0, lun 0 scsi : detected 1 SCSI disk total. SCSI device sda: hdwr sector= 512 bytes. Sectors= 35566499 [17366 MB] [17.4 GB] 3c59x.c:v0.99H 11/17/98 Donald Becker http://cesdis.gsfc.nasa.gov/linux/drivers/vortex.html tulip.c:v0.89H 5/23/98 [EMAIL PROTECTED] eth0: Lite-On 82c168 PNIC at 0xd000, 00 a0 cc 54 bf b4, IRQ 10. eth0: MII transceiver found at MDIO address 1, config 3000 status 7829. eth0: Advertising 01e1 on PHY 1, previously advertising 01e1. Partition check: sda: sda1 sda2 sda5 sda6 sda7 sda8 sda9 md.c: sizeof(mdp_super_t) = 4096 autodetecting RAID arrays autorun ... ... autorun DONE. VFS: Mounted root (ext2 filesystem) readonly. Up to here I haven't seen any mention of the IDE disks, kernel load is finised, rest is doen by init scripts. Freeing unused kernel memory: 36k freed Adding Swap: 265032k swap-space (priority -1) hda: ST3491A D, ATA DISK drive hdb: ST34321A, ATA DISK drive hdc: FUJITSU MPD3043AT, ATA DISK drive hdd: ATAPI CDROM, ATAPI CDROM drive ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 ide1 at 0x170-0x177,0x376 on irq 15 hda: ST3491A D, 408MB w/120kB Cache, CHS=899/15/62 hdb: ST34321A, 4103MB w/128kB Cache, CHS=8894/15/63 hdc: FUJITSU MPD3043AT, 4125MB w/512kB Cache, CHS=8940/15/63 hda: hda1 hda2 hdb: hdb1 hdb2 hdb3 hdc: hdc1 hdc2 hdc3 This looks like IDE support is compiled as a module, and therefore the kernel doesn't see your disks when checking for partitions to include in autostart. Bye, Martin "you have moved your mouse, please reboot to make this change take effect" -- Martin Bene vox: +43-664-3251047 simon media fax: +43-316-813824-6 Andreas-Hofer-Platz 9 e-mail: [EMAIL PROTECTED] 8010 Graz, Austria -- finger [EMAIL PROTECTED] for PGP public key
Re: Is Raid Stable?
[EMAIL PROTECTED] writes: For more direct results, I've got a raid 1 on my web server, a raid 0 in test (stupid jedi mind trick - what happens with a 2gig and 200mb stripe set), and I hope to try raid 5 real soon now. I'm using software RAID5 on our IMAP server mailstore cluster: 6 nodes each with 6 x 9GB 10KRPM disks installed in 3 hot-swap hot-everything Sun D1000 arrays. It's up to 8300 users now and will be tripling over the next year or two. No problems. I also use software RAID5 (5 x 9GB 10K RPM disks in a Sun hot-swap multipack) for our web server (2 million hits/week, 90+ main sites, thousands of small user sites). No problems. I also use it on our mirror server (similar hardware). No problems. I trust it. --Malcolm -- Malcolm Beattie [EMAIL PROTECTED] Unix Systems Programmer Oxford University Computing Services
Re: Notify scripts?
I've had a disk failure or two. The only problem I had was the SCSI timeouts with an AIC7890. The system would lock up waiting on the SCSI i/o, but a reboot would always recover and come up with 2 out of 3. Here's a script I use for watching status (forget where I got it from). Just run "checkmd -i", then put a crontab entry like: 15 * * * * /usr/local/bin/checkmd -v If there's any output (i.e. errors) root will get an email. # #! /bin/bash # # This script checks that the md configuration is the same as that # read at configuration time. When called with the -i option, it # reads /proc/mdstat and learns the configuration. If called without # args, it returns non zero status if the configuration is different # from the one learned, and prints a message if the -v flag is present. # # usage: checkmd.sh [-iv] init="" verbose="" CONF=/etc/md.conf while getopts "iv" opt; do case $opt in i) init=true ;; v) verbose=true ;; *) cat -EOF usage: $0 [-iv] [fromdev] [todev] -i means init the file $CONF with the current md configuration -v means display a message in case of configuration mismatch EOF exit 1 ;; esac; done if [ ! -r $CONF -o "$init" = true ]; then cat /proc/mdstat $CONF chmod 444 $CONF echo "Current configuration saved in $CONF:" 2 cat $CONF 2 else cat /proc/mdstat | cmp $CONF /dev/null if [ $? != 0 ]; then if [ $verbose ]; then echo 2 echo "ALARM! md configuration problem" 2 echo 2 echo "Current configuration is:" 2 cat /proc/mdstat 2 echo 2 echo "should be:" 2 cat $CONF 2 fi exit 1 fi fi # Michael D. Black Principal Engineer [EMAIL PROTECTED] 407-676-2923,x203 http://www.csi.cc Computer Science Innovations http://www.csi.cc/~mike My home page FAX 407-676-2355 - Original Message - From: Wayne Buttles [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, October 07, 1999 7:12 PM Subject: Notify scripts? I have been playing with raid on a stock Redhat 6.0 install for a couple days now. I think I have finally figured everything out. I have raid5 working with 3 drives automounting via the kernel with type fd partitions. I powered off a drive and then added it back with raidhotadd on a successive boot with no problem. All seems swell. I was wondering, are there scripts to add audible beep and/or email admin on failure? After all, if raid is working properly you won't even notice unless you are logged in (right?). Also, has anyone had a drive fail for real? I'm curious about the real life condidion of a scsi driver dealing with a failed drive. Thanks, Wayne.
Re: FW: Dream RAID System
On Fri, 8 Oct 1999, Oscar Fernández Cantero wrote: Hi, This is just to tell that with almost the same configuration which has been described (Mylex Extremeraid, 4 Cheetahs of third generation), the only difference being that I use raid 0 and the system is a Dell Poweredge 6300 with two PIII Xeon-500Mhz, I get roughly 70Mb/sec reading and 90Mb/sec writing of sustained throughput. How much RAM? Which were the bonnie file sizes? saludos, *---(*)---**-- Francisco J. Montilla System Network administrator [EMAIL PROTECTED] irc: pukkaSevilleSpain INSFLUG (LiNUX) Coordinator: www.insflug.org - ftp.insflug.org
Raid 1 in kernel 2.2.12
Hi all I'm trying to set up a box with its root filesystem on a RAID1 "partition" and I'm quite confused because pacthes for the kernel are either too old, either differents at some mirrors that at others (I mean the version), and now Ive found RAID-1 (mirroring) mode (NEW) in kernel 2.2.12 but nowhere says that it's fully functional and it'll work with raidtools and so on .. Can anybody pleas tell me what do I need to patch to make this run? :? Thanks a lot .. :) -- Se despide Javi Polo el fracasado ;) -= Administrador de OniNET CB =- Me puedes encontrar en fido en 2:347/13.4
Re: FW: Dream RAID System
The machine has 512 Mb RAM and the Bonnie file size 512 Mb. No cache advantage involved. Hasta luego Francisco Jose Montilla wrote: On Fri, 8 Oct 1999, Oscar Fernández Cantero wrote: Hi, This is just to tell that with almost the same configuration which has been described (Mylex Extremeraid, 4 Cheetahs of third generation), the only difference being that I use raid 0 and the system is a Dell Poweredge 6300 with two PIII Xeon-500Mhz, I get roughly 70Mb/sec reading and 90Mb/sec writing of sustained throughput. How much RAM? Which were the bonnie file sizes? saludos, -- -- Oscar Fernández Cantero [EMAIL PROTECTED] CEIFE - Centro Español de Investigación Farmacoepidemiológica Almirante 28 2º http://www.ceife.es 28004 MADRID, SPAIN Phone: +34 91 531 7975 Fax: +34 91 531 2871 ---
Re: FW: Dream RAID System
[ Friday, October 8, 1999 ] Oscar Fernández Cantero wrote: The machine has 512 Mb RAM and the Bonnie file size 512 Mb. No cache advantage involved. I don't think many would agree with you on this :) Could you print out runs with -s 512 and -s 2000, please? James -- Miscellaneous Engineer --- IBM Netfinity Performance Development
Support for 2.2.12?
Hi all. I recall a few weeks ago someone sent me a link to a patch for 2.2.12, but I've lost that email. Is there an official patch for 2.2.12 yet? Thanks, Dave
Re: FW: Dream RAID System
At the moment I can offer you the Bonnie results on a single Seagate Cheetah drive attached to an integrated AIC-7890 LVD controller. I think the possible differences between 512 o 2000 Mb file size, should be shown in a similar way through the results on this single disk. 512Mb file size: ---Sequential Output ---Sequential Input-- --Random-- -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- MachineMB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU 1* 512 5812 76.9 21659 23.3 6179 16.1 7498 94.6 19780 21.6 859.2 9.2 2000Mb file size: ---Sequential Output ---Sequential Input-- --Random-- -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- MachineMB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU 1*2000 6148 79.1 18639 22.3 6176 15.9 7038 88.3 19431 20.8 107.4 2.2 As you can see, the results are pretty close, except for the random seeks. Anyway, when available I also will offer you the results using the Mylex ExtremeRaid and the 4 cheetahs in a raid0 configuration. Please note that pure cache reads in my machine are about 200 Mb/sec, and that I use two LVD channels, each with two drives. Regards -- -- Oscar Fernández Cantero [EMAIL PROTECTED] CEIFE - Centro Español de Investigación Farmacoepidemiológica Almirante 28 2º http://www.ceife.es 28004 MADRID, SPAIN Phone: +34 91 531 7975 Fax: +34 91 531 2871 --- Oscar Fernández Cantero wrote: Hello, I have currently returned the card because of something wrong with the battery backup memory. As soon as I receive the replacement (one or two weeks), I'll perform the test you tell, and send the results to the list. Bye James Manning wrote: [ Friday, October 8, 1999 ] Oscar Fernández Cantero wrote: The machine has 512 Mb RAM and the Bonnie file size 512 Mb. No cache advantage involved. I don't think many would agree with you on this :) Could you print out runs with -s 512 and -s 2000, please? James -- Miscellaneous Engineer --- IBM Netfinity Performance Development
Raid0
I was working on doing the autostart for raid0 and the part where it says: 3. The partition-types of the devices used in the RAID must be set to 0xFD (use fdisk and set the type to ``fd'') is confusing because I don't have a choice of fd for partition type. If I put it in it lets me do it but labels it unknown. Is this correct or am I doing something wrong? Thanks, Pat --- Patrick Heath Network Administrator Fred Hutchinson Cancer Research Center 1100 Fairview Avenue North, A1-162 Seattle, WA 98109 Email: [EMAIL PROTECTED] Phone: (206) 667-2000 Fax:(206) 667-6525 ---
Raid0
I was working on doing the autostart for raid0 and the part where it says: 3. The partition-types of the devices used in the RAID must be set to 0xFD (use fdisk and set the type to ``fd'') is confusing because I don't have a choice of fd for partition type. If I put it in it lets me do it but labels it unknown. Is this correct or am I doing something wrong? Here is my dmesg. Any ideas as to why it bombs on startup? If I raidstart manually everything works fine? Linux version 2.2.5-15 ([EMAIL PROTECTED]) (gcc version egcs-2.91.66 1 9990314/Linux (egcs-1.1.2 release)) #1 Mon Apr 19 23:00:46 EDT 1999 Detected 448626242 Hz processor. Console: colour VGA+ 80x25 Calibrating delay loop... 447.28 BogoMIPS Memory: 192600k/196608k available (996k kernel code, 412k reserved, 2216k data, 60k init) VFS: Diskquotas version dquot_6.4.0 initialized CPU: Intel Pentium II (Deschutes) stepping 02 Checking 386/387 coupling... OK, FPU using exception 16 error reporting. Checking 'hlt' instruction... OK. POSIX conformance testing by UNIFIX mtrr: v1.26 (19981001) Richard Gooch ([EMAIL PROTECTED]) PCI: PCI BIOS revision 2.10 entry at 0xfca8e PCI: Using configuration type 1 PCI: Probing PCI hardware Linux NET4.0 for Linux 2.2 Based upon Swansea University Computer Society NET3.039 NET4: Unix domain sockets 1.0 for Linux NET4.0. NET4: Linux TCP/IP 1.0 for NET4.0 IP Protocols: ICMP, UDP, TCP, IGMP Initializing RT netlink socket Starting kswapd v 1.5 Detected PS/2 Mouse Port. Serial driver version 4.27 with MANY_PORTS MULTIPORT SHARE_IRQ enabled ttyS00 at 0x03f8 (irq = 4) is a 16550A ttyS01 at 0x02f8 (irq = 3) is a 16550A pty: 256 Unix98 ptys configured apm: BIOS version 1.2 Flags 0x03 (Driver version 1.9) Real Time Clock Driver v1.09 RAM disk driver initialized: 16 RAM disks of 4096K size PIIX4: IDE controller on PCI bus 00 dev 39 PIIX4: not 100% native mode: will probe irqs later ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:DMA, hdb:pio ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hdc:DMA, hdd:pio hda: Maxtor 90845D4, ATA DISK drive hdc: CRD-8400B, ATAPI CDROM drive ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 ide1 at 0x170-0x177,0x376 on irq 15 hda: Maxtor 90845D4, 8063MB w/512kB Cache, CHS=1027/255/63 hdc: ATAPI 40X CD-ROM drive, 128kB Cache Uniform CDROM driver Revision: 2.54 Floppy drive(s): fd0 is 1.44M FDC 0 is a National Semiconductor PC87306 md driver 0.90.0 MAX_MD_DEVS=256, MAX_REAL=12 raid5: measuring checksumming speed raid5: using high-speed MMX checksum routine pII_mmx : 1091.946 MB/sec p5_mmx: 1058.037 MB/sec 8regs : 773.049 MB/sec 32regs: 555.498 MB/sec using fastest function: pII_mmx (1091.946 MB/sec) scsi : 0 hosts. scsi : detected total. md.c: sizeof(mdp_super_t) = 4096 Partition check: hda: hda1 hda2 hda5 hda6 RAMDISK: Compressed image found at block 0 autodetecting RAID arrays autorun ... ... autorun DONE. VFS: Mounted root (ext2 filesystem). (scsi0) Adaptec AHA-294X Ultra2 SCSI host adapter found at PCI 13/0 (scsi0) Wide Channel, SCSI ID=7, 32/255 SCBs (scsi0) Downloading sequencer code... 374 instructions downloaded scsi0 : Adaptec AHA274x/284x/294x (EISA/VLB/PCI-Fast SCSI) 5.1.15/3.2.4 Adaptec AHA-294X Ultra2 SCSI host adapter scsi : 1 host. (scsi0:0:1:0) Synchronous at 40.0 Mbyte/sec, offset 31. Vendor: IBM Model: DNES-318350W Rev: SA30 Type: Direct-Access ANSI SCSI revision: 03 Detected scsi disk sda at scsi0, channel 0, id 1, lun 0 (scsi0:0:2:0) Synchronous at 40.0 Mbyte/sec, offset 15. Vendor: SEAGATE Model: ST318275LWRev: 0001 Type: Direct-Access ANSI SCSI revision: 02 Detected scsi disk sdb at scsi0, channel 0, id 2, lun 0 (scsi0:0:3:0) Synchronous at 40.0 Mbyte/sec, offset 31. Vendor: QUANTUM Model: VIKING II 9.1WSE Rev: 4110 Type: Direct-Access ANSI SCSI revision: 02 Detected scsi disk sdc at scsi0, channel 0, id 3, lun 0 (scsi0:0:4:0) Synchronous at 40.0 Mbyte/sec, offset 31. Vendor: QUANTUM Model: VIKING II 9.1WSE Rev: 5520 Type: Direct-Access ANSI SCSI revision: 02 Detected scsi disk sdd at scsi0, channel 0, id 4, lun 0 SCSI device sda: hdwr sector= 512 bytes. Sectors= 35843670 [17501 MB] [17.5 GB] sda: unknown partition table SCSI device sdb: hdwr sector= 512 bytes. Sectors= 35566480 [17366 MB] [17.4 GB] sdb: unknown partition table SCSI device sdc: hdwr sector= 512 bytes. Sectors= 17836668 [8709 MB] [8.7 GB] sdc: sdc1 SCSI device sdd: hdwr sector= 512 bytes. Sectors= 17836668 [8709 MB] [8.7 GB] sdd: sdd1 autodetecting RAID arrays (read) sdc1's sb offset: 8915968 [events: 0002] (read) sdd1's sb offset: 8915968 [events: 0002] autorun ... considering sdd1 ... adding sdd1 ... adding sdc1 ... created md0 bindsdc1,1 bindsdd1,2 running: sdd1sdc1 now! sdd1's event counter: 0002 sdc1's event counter: 0002 kmod: failed to exec /sbin/modprobe -s -k md-personality-2, errno = 2 do_md_run()
Re: Raid0
You're OK...there's a newer version of fdisk which recognizes this new partition type. Michael D. Black Principal Engineer [EMAIL PROTECTED] 407-676-2923,x203 http://www.csi.cc Computer Science Innovations http://www.csi.cc/~mike My home page FAX 407-676-2355 - Original Message - From: Pat Heath [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, October 08, 1999 11:28 AM Subject: Raid0 I was working on doing the autostart for raid0 and the part where it says: 3. The partition-types of the devices used in the RAID must be set to 0xFD (use fdisk and set the type to ``fd'') is confusing because I don't have a choice of fd for partition type. If I put it in it lets me do it but labels it unknown. Is this correct or am I doing something wrong? Thanks, Pat --- Patrick Heath Network Administrator Fred Hutchinson Cancer Research Center 1100 Fairview Avenue North, A1-162 Seattle, WA 98109 Email: [EMAIL PROTECTED] Phone: (206) 667-2000 Fax: (206) 667-6525 ---
mirroring over net
hello, i have a little question, i made a mirror of a lokal 'disk' over nbd (net block device) to a second server. if the first server goes down (failed) the second server mounts the mirrored 'disk' localy (after fsck) and starts the service (e.g. mailservice, samba homedirs..) .. everything works fine, but: now the primary server comes up again (after repair) the secondary server stops all services, unmounts the 'disk' and exports it again over nbd but how could i tell the md driver on the primary server that the local disk is faulty and the 'nbd-disk' from the second server is ok thank you greetings from vienna leo
any disk monitoring software for raids?
Anybody know of any disk rate monitoring software out there that will monitor disk ios and disk transfer rates on Linux systems? On another os, I have a monitor program that records the following information: hostname Fri Oct 8 13:14:29 1999 2.25 1.65 1.531 user Mem: act inact wired free Forks: fork vforkChar: in out 124336 10664 17440 1216 7.88 0.00 0.0 101.5 Paging: re pin pout flts cowzf hit% Disk: kbps tps queue 072 0 822 23678 0 rz0 404 55 2 rz2 154 0 Swap: Reserved Free Cache: Namei Buffer 2% 98% 96% 99% CPU: user nice sys idle wait swtch intr scall #0 280 7102647338 2139 Net: ipkts ierrs opkts oerrs collis ln0 57.20.0 42.40.01.0 sl00.00.00.00.00.0 lo0 28.10.0 28.10.00.0 ppp0 0.00.00.00.00.0 Paging: re pin pout flts cowzf hit% Disk: kbps tps 072 0 822 23678 0 rz0 404 55 rz2 154 In particular, I am interested in the number of bytes per second written to each disk drive (whether they are raided or not). I am looking for bottlenecks. I may try to port the software, but am not interested in reinventing the wheel if anyones knows of monitoring software for Linux that already exists. Thanks in advance, Kent Ziebell
Re: Raid0
On Fri, Oct 08, 1999 at 08:28:39AM -0700, Pat Heath wrote:
I was working on doing the autostart for raid0 and the part where it says:
3. The partition-types of the devices used in the RAID must be set to
0xFD (use fdisk and set the type to ``fd'')
is confusing because I don't have a choice of fd for partition type. If I
put it in it lets me do it but labels it unknown. Is this correct or am I
doing something wrong?
It's correct. fdisk doesn't know about type 0xFD yet.
The HOWTO should probably state this. I'll fix it :)
: [EMAIL PROTECTED] : And I see the elder races, :
:.: putrid forms of man:
: Jakob Østergaard : See him rise and claim the earth, :
:OZ9ABN : his downfall is at hand. :
:.:{Konkhra}...:
RE: Raid0
Title: RE: Raid0 Did you use persistent superblocks in your raidtab? Clay -Original Message- From: Pat Heath [mailto:[EMAIL PROTECTED]] Sent: Friday, October 08, 1999 9:50 AM To: [EMAIL PROTECTED] Subject: Raid0 I was working on doing the autostart for raid0 and the part where it says: 3. The partition-types of the devices used in the RAID must be set to 0xFD (use fdisk and set the type to ``fd'') is confusing because I don't have a choice of fd for partition type. If I put it in it lets me do it but labels it unknown. Is this correct or am I doing something wrong? Here is my dmesg. Any ideas as to why it bombs on startup? If I raidstart manually everything works fine? Linux version 2.2.5-15 ([EMAIL PROTECTED]) (gcc version egcs-2.91.66 1 9990314/Linux (egcs-1.1.2 release)) #1 Mon Apr 19 23:00:46 EDT 1999 Detected 448626242 Hz processor. Console: colour VGA+ 80x25 Calibrating delay loop... 447.28 BogoMIPS Memory: 192600k/196608k available (996k kernel code, 412k reserved, 2216k data, 60k init) VFS: Diskquotas version dquot_6.4.0 initialized CPU: Intel Pentium II (Deschutes) stepping 02 Checking 386/387 coupling... OK, FPU using exception 16 error reporting. Checking 'hlt' instruction... OK. POSIX conformance testing by UNIFIX mtrr: v1.26 (19981001) Richard Gooch ([EMAIL PROTECTED]) PCI: PCI BIOS revision 2.10 entry at 0xfca8e PCI: Using configuration type 1 PCI: Probing PCI hardware Linux NET4.0 for Linux 2.2 Based upon Swansea University Computer Society NET3.039 NET4: Unix domain sockets 1.0 for Linux NET4.0. NET4: Linux TCP/IP 1.0 for NET4.0 IP Protocols: ICMP, UDP, TCP, IGMP Initializing RT netlink socket Starting kswapd v 1.5 Detected PS/2 Mouse Port. Serial driver version 4.27 with MANY_PORTS MULTIPORT SHARE_IRQ enabled ttyS00 at 0x03f8 (irq = 4) is a 16550A ttyS01 at 0x02f8 (irq = 3) is a 16550A pty: 256 Unix98 ptys configured apm: BIOS version 1.2 Flags 0x03 (Driver version 1.9) Real Time Clock Driver v1.09 RAM disk driver initialized: 16 RAM disks of 4096K size PIIX4: IDE controller on PCI bus 00 dev 39 PIIX4: not 100% native mode: will probe irqs later ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:DMA, hdb:pio ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hdc:DMA, hdd:pio hda: Maxtor 90845D4, ATA DISK drive hdc: CRD-8400B, ATAPI CDROM drive ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 ide1 at 0x170-0x177,0x376 on irq 15 hda: Maxtor 90845D4, 8063MB w/512kB Cache, CHS=1027/255/63 hdc: ATAPI 40X CD-ROM drive, 128kB Cache Uniform CDROM driver Revision: 2.54 Floppy drive(s): fd0 is 1.44M FDC 0 is a National Semiconductor PC87306 md driver 0.90.0 MAX_MD_DEVS=256, MAX_REAL=12 raid5: measuring checksumming speed raid5: using high-speed MMX checksum routine pII_mmx : 1091.946 MB/sec p5_mmx : 1058.037 MB/sec 8regs : 773.049 MB/sec 32regs : 555.498 MB/sec using fastest function: pII_mmx (1091.946 MB/sec) scsi : 0 hosts. scsi : detected total. md.c: sizeof(mdp_super_t) = 4096 Partition check: hda: hda1 hda2 hda5 hda6 RAMDISK: Compressed image found at block 0 autodetecting RAID arrays autorun ... ... autorun DONE. VFS: Mounted root (ext2 filesystem). (scsi0) Adaptec AHA-294X Ultra2 SCSI host adapter found at PCI 13/0 (scsi0) Wide Channel, SCSI ID=7, 32/255 SCBs (scsi0) Downloading sequencer code... 374 instructions downloaded scsi0 : Adaptec AHA274x/284x/294x (EISA/VLB/PCI-Fast SCSI) 5.1.15/3.2.4 Adaptec AHA-294X Ultra2 SCSI host adapter scsi : 1 host. (scsi0:0:1:0) Synchronous at 40.0 Mbyte/sec, offset 31. Vendor: IBM Model: DNES-318350W Rev: SA30 Type: Direct-Access ANSI SCSI revision: 03 Detected scsi disk sda at scsi0, channel 0, id 1, lun 0 (scsi0:0:2:0) Synchronous at 40.0 Mbyte/sec, offset 15. Vendor: SEAGATE Model: ST318275LW Rev: 0001 Type: Direct-Access ANSI SCSI revision: 02 Detected scsi disk sdb at scsi0, channel 0, id 2, lun 0 (scsi0:0:3:0) Synchronous at 40.0 Mbyte/sec, offset 31. Vendor: QUANTUM Model: VIKING II 9.1WSE Rev: 4110 Type: Direct-Access ANSI SCSI revision: 02 Detected scsi disk sdc at scsi0, channel 0, id 3, lun 0 (scsi0:0:4:0) Synchronous at 40.0 Mbyte/sec, offset 31. Vendor: QUANTUM Model: VIKING II 9.1WSE Rev: 5520 Type: Direct-Access ANSI SCSI revision: 02 Detected scsi disk sdd at scsi0, channel 0, id 4, lun 0 SCSI device sda: hdwr sector= 512 bytes. Sectors= 35843670 [17501 MB] [17.5 GB] sda: unknown partition table SCSI device sdb: hdwr sector= 512 bytes. Sectors= 35566480 [17366 MB] [17.4 GB] sdb: unknown partition table SCSI device sdc: hdwr sector= 512 bytes. Sectors= 17836668 [8709 MB] [8.7 GB] sdc: sdc1 SCSI device sdd: hdwr sector= 512 bytes. Sectors= 17836668 [8709 MB] [8.7 GB] sdd: sdd1 autodetecting RAID arrays (read) sdc1's sb offset: 8915968 [events: 0002] (read) sdd1's sb offset: 8915968 [events: 0002] autorun ... considering sdd1 ... adding sdd1 ... adding sdc1 ... created md0 bindsdc1,1 bindsdd1,2 running: sdd1sdc1 now! sdd1's event counter: 0002 sdc1's event counter: 0002 kmod: failed to exec
FDISK
Where can the new version of FDISK be found at? === David Cooley N5XMT Internet: [EMAIL PROTECTED] Packet: N5XMT@KQ4LO.#INT.NC.USA.NA T.A.P.R. Member #7068 We are Borg... Prepare to be assimilated! ===
RE: mirroring over net
Leonhard Zachl wrote: but how could i tell the md driver on the primary server that the local disk is faulty and the 'nbd-disk' from the second server is ok have you tried this? I haven't done anything with nbd, but I would expect the following to happen: * primary server comes up again * primary server starts raid set with the local disk the nbd * it reads both superblocks, and will see that the nbd is more up to date, and start the raid using only the nbd * then do raidhotadd /dev/md0 /dev/localdisk, and it should rebuild note: from everything I've heard you should basically expect horrible performance from at least the rebuild from the nbd, if not all the time. You'll want to hack the raid code to never do reads from the nbd (currently it will load balance between the two). And you'd probably want to set it up so that the secondary server only relinquishes control after the primary server's disk is rebuilt... which could take forever with nbd? Tom
Re: Is Raid Stable?
Hardware raid is most likely easier, and therefore better for a quick solution. Also easier to boot from. I don´t have any experience with hardware raid however. For stability there is most likely no difference. Hot swap may pose some hardware-related difficulties with software raid. The raid patch is surely ready for "serious use" now. It´s in public test since last year, and on one of my production servers I still run an early version from december 98. The server is under load most of the time and works like a charm for 8 months now (5 IBM IDE drives, 4 for raid5, P133). For software raid I recommend SCSI. Should be relatively easy. Take care about the mke2fs options (4096 blocksize, stride etc.). Brave ones may build IDE raids. My recommendations for this are in the next message. -- the online community service for gamers friends - http://www.rivalnet.com * unterstützt über 50 PC-Spiele im Multiplayer-Modus * Dateien senden empfangen bis 500 MB am Stück * Newsgroups, Mail, Chat mehr
