Re: here we go again...

1999-08-14 Thread James Manning
After editing the fs type on my raid partitions (thanks James Andreas), the system saw the raid device during boot. But it is only using one of the disk in the raid device. (Is mentioned during boot) Did mkraid again, some mount/umount raidstart/stop to test things Seemed ok.

unrecognized option failed-disk

1999-08-14 Thread Drenning Bruce
I've got rh6.0. I'm trying to implement RAID1. I compiled the 2.2.10-4 kernel with the raid1 option. I installed the 0.90-4 rpm of raidtools. I'm trying to use the failed-disk option but it doesn't appear to be recognized. I've been lurking on the list for a while so I know there is a patch for

raidtools won't compile - part of raid-1 saga (fwd)

1999-08-14 Thread Jon Nathan
hello, i posted this to comp.os.linux.misc before i found the list. sorry if some people see it twice.. any help would be appreciated. -- Jon Nathan [EMAIL PROTECTED] http://www.rupture.net/~jon/ -- Forwarded message -- Date: Thu, 12 Aug 1999 13:15:46 -0400 From: Jon Nathan

Re: Re: Can not mount raid0 nor raid1 devices in 2.2.11

1999-08-14 Thread thomasko321
ftp://ftp.de.kernel.org/pub/linux/daemons/raid/alpha/ raid0145-date-kernel-version.bz2 and the raidtools-date-raid-version.tar.bz2 ftp://ftp.de.kernel.org/pub/linux/daemons/raid/alpha/raid0145-19990724-2.2.10.bz2

Re: Error on fsck

1999-08-14 Thread thomasko321
How did you create it? Did you upgrade from a previous version of md? How does your /etc/raidtab look like? Did you create your raid1 over an existing file-system? Thomas Hi. i am having trouble on fsck my raid1 array. Fsck says: The filesystem size (according to the superblock) is 8787555

Re: Byte the big 'B'

1999-08-14 Thread Jan Edler
It's Byte, so 66 Megabytes/sec is correct. But that's just the burst rate. If you look at the specs for the disk drives, you'll see that they can't keep up with that rate. I figure anything 10MB/s sustained is pretty good for todays drives. Expect more in the future. Jan Edler NEC Research

Re: Re: Error on fsck

1999-08-14 Thread thomasko321
That's not very good because raid whatever places in the last few bytes its raid-superblock. When you created the raid, you wrote the super-block over the last bytes of the filesystem. Now it's corrupted. When you want to create a raid over an existing ext2 filesystem you have to resize the

To List owner

1999-08-14 Thread David Wyman
I have sent tow requests to majordomo telling it to change my email addres but it has refused me both times. Can the owner of this list please change my email from [EMAIL PROTECTED] to [EMAIL PROTECTED] Thanks, David

Re: Byte the big 'B'

1999-08-14 Thread Michael Tibor
On Fri, 30 Jul 1999, D. Carlos Knowlton wrote: Alright, what's going on guys?! I called Western Digital technical support to find out what I need to do to get my U-ATA/66 drives to transfer anything near 66MB/s, (Mega"bytes", note the capital 'B')like all the literature and advertising and

Re: Promise UDMA-66 RAID- Help!

1999-08-14 Thread D. Carlos Knowlton
Jakob Osterngaard wrote: [snip] Was 19MB/s from a RAID ? If so, how many disks ? What RAID configuration ? How did you measure it ? I'm running RAID level 5 on four WD Caviar 20.4GB U66 drives. 19MB/s is what I get when I do a "hdparm -t /dev/md0". I also tried cp'ing a 1GB file to

Goin' Crazy

1999-08-14 Thread maisel
I keep getting: handling MD device /dev/md0 analyzing super-block disk 0: /dev/sda1, 8883913kB, raid superblock at 8883840kB disk 1: /dev/sdb1, 8883913kB, raid superblock at 8883840kB disk 2: /dev/sdc1, 8883913kB, raid superblock at 8883840kB disk 3: /dev/sdd1, 8883913kB, raid superblock at

Re: harmless (?) error

1999-08-14 Thread James Manning
disk 0: /dev/rd/c0d0p1, 88866800kB, raid superblock at 88866688kB disk 1: /dev/rd/c0d1p1, 35547120kB, raid superblock at 35547008kB disk 2: /dev/rd/c0d2p1, 35547120kB, raid superblock at 35547008kB disk 3: /dev/rd/c0d3p1, 35547120kB, raid superblock at 35547008kB disk 4: /dev/rd/c0d4p1,

The patch??

1999-08-14 Thread maisel
Hi! After applying the raid0145-19990724-2.2.10 Patch, I get: martian:/usr/src/linux# make dep ; make clean make[1]: Entering directory `/usr/src/linux-2.2.10/arch/i386/boot' make[1]: Nothing to be done for `dep'. make[1]: Leaving directory `/usr/src/linux-2.2.10/arch/i386/boot' scripts/mkdep

harmless (?) error

1999-08-14 Thread James Manning
In my s/w raid5 over h/w raid0 testing, I had just completed s/w raid5 over 4 h/w raid0's (via Mylex DAC1164P, 5 drives each), recorded the bonnie results. After using Mylex's config util (in a DOS reboot) and making the 20 drives into 10 raid0's with 2 drives each, I did the follow: - killed