Hi all,
I am attempting to get RAID going along with LVM under kernel 2.2.16. I
have used RAID successfully in the past but never with LVM. I am using
Ingo's latest patch from people.redhat.com/mingo and the LVM patch located
at:
ftp.kernel.org/pub/linux/kernel/people/andrea/lvm/aa-2119/z-
On Tuesday June 13, [EMAIL PROTECTED] wrote:
>
> On Tue, 13 Jun 2000, Neil Brown wrote:
>
> no, (and i told you this before) it does not need MSDOS style partition
> tables. Linux's partition system is 'generic', and when i implemented this
> i only added the 'lowlevel glue' to support MSDOS-sty
> -Original Message-
> From: Jeff Hill [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, June 13, 2000 3:56 PM
> To: Gregory Leblanc
> Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Re: Benchmarks, raid1 (was raid0) performance
>
> Gregory Leblanc wrote:
> >
> > I don't have anything that
Gregory Leblanc wrote:
>
> I don't have anything that caliber to compare against, so I can't really
> say. Should I assume that you don't have Mika's RAID1 read balancing patch?
I have to admit I was ignorant of the patch (I had skimmed the archives,
but not well enough). Searched the archive f
I created a raid but I now want to create a new raid in its place. When I
run mkraid -f /dev/md0 it returns a warning about using -f but doesn't do
any more. How do you really force it to destroy the old raid and create a
new raid in its place
Raidtools ver 0.90
Kernel 2.2.11
Bug1: Maybe im missing something here, why arent reads just as fast as writes?
The cynic in me suggests that the RAID driver has to wait for the
information to be read off the disks, but it doesn't have to wait for the
writes to complete before returning, but I haven't read the code.
-HJC
On Tue, Jun 13, 2000 at 04:51:46AM +1000, bug1 wrote:
> Maybe im missing something here, why arent reads just as fast as writes?
I note the same on a 2 way IDE RAID-1 device, with both disks on a separate
bus.
Regards,
bert hubert
--
| http://www.rent-a-ne
Gregory Leblanc wrote:
>>--snip--<<
> > I conclude that on my system there is an ide saturation point (or
> > bottleneck) around 40MB/s
> Didn't the LAND5 people think that there was a bottleneck around 40MB/Sec at
> some point? Anybody know if they were talking about IDE drives? Seems
> quite
On Tue, 13 Jun 2000 04:36:39 -0400, Edward Schernau <[EMAIL PROTECTED]>
wrote:
>> Could this be changed to 2.2.16-raid for future versions or should I
>> better get in touch with kernel-package's maintainer?
>
>Or just get a real kernel from kernel.org.
Debian's kernel package relies on "real" ke
On Tue, 13 Jun 2000 09:02:42 +0200 (CEST), Ingo Molnar <[EMAIL PROTECTED]>
wrote:
>On Tue, 13 Jun 2000, Marc Haber wrote:
>> A kernel patched this way doesn't build with Debian's kernel package.
>> Complains "The version number 2.2.16-RAID is not all lowercase. Stop."
>>
>> Could this be changed
> -Original Message-
> From: bug1 [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, June 13, 2000 10:39 AM
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Subject: Re: Benchmarks, raid0 performance, 1,2,3,4 drives
>
> Ingo Molnar wrote:
> >
> > could you send me your /etc/raidtab? I've teste
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Hello,
Just to let you know, I also see very similar IDE-RAID0 performance
problems:
I have RAID0 with two 30G DiamondMax (Maxtor) ATA-66 drives connected to
a Promise Ultra66 controller.
I am using kernel 2.4.0-test1-
On Mon, 12 Jun 2000, Matthew Kirkwood wrote:
> I suspect that I did something silly, but is there a
> way to bring up the array without bring sda5 into the
> picture to see if there's only the one broken disk?
Hi,
Apologies for the self-followup, but I could do to start
restoring this thing fro
Theo Van Dinter wrote:
>
> I wasn't sure if there was a 2.2.16 patch coming out soon, and I wasn't sure
> I wanted to install a "A0" patch ... Any thoughts?
Nothing to worry about is just mingos
versioning system for the patches he maintains. Has nothing to do with
alpha or so. If he just po
Ingo Molnar wrote:
>
> could you send me your /etc/raidtab? I've tested the performance of 4-disk
> RAID0 on SCSI, and it scales perfectly here, as far as hdparm -t goes.
> (could you also send the 'hdparm -t /dev/md0' results, do you see a
> degradation in those numbers as well?)
>
> it could e
Adrian Head wrote:
>
> I have seen people complain about simular issues on the kernel mailing
> list so maybe there is an actual kernel problem.
>
> What I have always wanted to know but haven't tested yet is to test raid
> performance with and without the noatime attribute in /etc/fstab I
> th
I have seen people complain about simular issues on the kernel mailing
list so maybe there is an actual kernel problem.
What I have always wanted to know but haven't tested yet is to test raid
performance with and without the noatime attribute in /etc/fstab I
think that when Linux reads a file
Having looked over the boot redundancy thread, I am still under the
impression this is a symptom of a bug. My system worked absolutely fine
until I upgraded to 2.2.16. Now having done so, I am unable to install a
new kernel as running lilo from 2.2.16-RAID results in a lockup at boot
after lilo pr
Marc Haber wrote:
>
> On Mon, 12 Jun 2000 14:34:59 +0200 (CEST), Ingo Molnar <[EMAIL PROTECTED]>
> wrote:
> >the latest 2.2 (production) RAID code against 2.2.16-final can be found
> >at:
> >
> >http://www.redhat.com/~mingo/raid-patches/raid-2.2.16-A0
> >
> >let me know if you have any pr
On Tue, 13 Jun 2000, Neil Brown wrote:
> One way is by setting the partition type of the relevant partitions.
> This is nice and easy, but requires you to use MSDOS style partition
> tables (which only 99.4% of Linux users do:-), and works fine for
> RAID0 or 1 or 5 or Linear.
no, (and i told y
On Tue, 13 Jun 2000, Marc Haber wrote:
> A kernel patched this way doesn't build with Debian's kernel package.
> Complains "The version number 2.2.16-RAID is not all lowercase. Stop."
>
> Could this be changed to 2.2.16-raid for future versions or should I
> better get in touch with kernel-pack
21 matches
Mail list logo
