On Mon, 14 Aug 2000, Corin Hartland-Swann wrote:
>I have tried this out, and found that the default settings were:
>elevator ID=232 read_latency=128 write_latency=8192 max_bomb_segments=4
(side note: Jens increased bomb segments to 32 in recent 2.2.17)
I think we can apply this patch on top of
On Mon, 14 Aug 2000, Jens Axboe wrote:
>> I found that increasing the read_latency to match write_latency fixes the
>> problems perfectly - thanks for the pointer!
>
>Ok good. Andrea, could we bump read latency in 2.2.17-pre?
Yes.
>> Increasing the read_latency and write_latency to 10,000,000 r
Check out the section on that in the Software-RAID HOWTO. You can get it
from http://www.LinuxDoc.org/HOWTO/Software-RAID-HOWTO-6.html#ss6.1 but a
mirror closer to you might be better.
Greg
> -Original Message-
> From: Martin Brown [mailto:[EMAIL PROTECTED]]
> Sent: Monday, Augu
Corin Hartland-Swann wrote:
>
> Hi Andre,
>
> The revised comparison between 2.2.15 and 2.4.0-test5 are as follows:
>
> ==> 2.2.15 <==
>
> Dir Size BlkSz Thr# Read (CPU%) Write (CPU%) Seeks (CPU%)
> - -- --- - -- --
> /mnt/ 256
judging by the traffic on this list, patched 2.2.14 is your best
bet. I have 2.2.12 which came with RH 6.1, and it works fine.
--
ai
http://sefiroth.org
On Mon, 14 Aug 2000, Ryan Daly wrote:
> Guys,
>
> I'm using 2.4.0-test5 right now 'cause I don't have the time to figure out how
> the n
> file. Should the /dev/mdx's which are equivalent to the / and /boot
> filesystems, respectively, be the first ones to be mounted?
Doesn't matter. The kernel mounts the root and the others are mounted
when fstab is read (root is already mounted at this point).
[EMAIL PROTECTED]
On Monday August 14, [EMAIL PROTECTED] wrote:
> Guys,
>
> I'm using 2.4.0-test5 right now 'cause I don't have the time to figure out how
> the new module directory structure works... (If anyone knows what to do, can
> you let me know?)
"make modules_install" should install the RAID modules into
hi ya ryan
usually i get the opposite problem
how to stop the system from autodetecting the
raid array sot hat it doesnt stop the booting...
so to turn it ondo the oopposite of what i do
to fix my "faulty raid" when it dies
- make sure you have /etc/raidtab
- make sure your kernel
On Mon, Aug 14 2000, Corin Hartland-Swann wrote:
> I have tried this out, and found that the default settings were:
> elevator ID=232 read_latency=128 write_latency=8192 max_bomb_segments=4
>
> Can anyone point me to any documentation on this elevator code? I was
> wondering what exactly the diff
Hi there,
I am CC:ing this to Andrea Arcangeli because he is credited at the top of
drivers/block/ll_rw_blk.c as writing the elevator code.
On Sun, 13 Aug 2000, Jens Axboe wrote:
> On Sun, Aug 13 2000, Corin Hartland-Swann wrote:
> > The fact remains that disk performance is much worse under 2
On Sun, 13 Aug 2000, Edward Schernau wrote:
> Anyone used the DC690 under Linux? Its a PCI card, 2 IDE busses,
> no CDROM support, with 4 30pin SIMM slots. Supposedly does mirroring,
> all of which is transparent to the OS. It doesn't require any DOS
> drivers. Any pointers would be apprectiat
On Sun, Aug 13 2000, Corin Hartland-Swann wrote:
> The fact remains that disk performance is much worse under 2.2.16 and
> heavy loads than under 2.2.15 - what I was trying to find out was what
A new elevator was introduced into 2.2.16, that may be affecting
results. Try using elvtune from util
> -Original Message-
> From: Matthias Koelle [mailto:[EMAIL PROTECTED]]
> Sent: Sunday, August 13, 2000 3:53 AM
> To: [EMAIL PROTECTED]
> Subject: Problem with RAID1 at Boot time and DMA problem
>
> Hi all,
>
> first of all...sorry for my english ;)
> I had a strange problem at boot time
> From [EMAIL PROTECTED] Sun Aug 13 12:58:36 2000
>
> Anyone used the DC690 under Linux? Its a PCI card, 2 IDE busses,
> no CDROM support, with 4 30pin SIMM slots. Supposedly does mirroring,
> all of which is transparent to the OS. It doesn't require any DOS
> drivers. Any pointers would be a
Date: Sun, 13 Aug 2000 19:03:27 +0200
From: Hubert Tonneau <[EMAIL PROTECTED]>
I removed the Mylex controler, and since it's a production server,
I cannot do experiments on this one, so I cannot get any more informations
(I'm sorry about that because I find very important to spend some
Mark,
On Sat, 12 Aug 2000, Mark Hahn wrote:
> > > readahead is effecting things (shouldnt, but...)
> >
> > mke2fs only allows block sizes of 1K, 2K or 4K, so I can't make the
> > blocksize any larger...
>
> I meant "size of block being read", rather than filesystem block size.
I've now tested
Leonard N. Zubkoff wrote:
>
> Generally, the Mylex PCI RAID controllers take disks offline when certain types
> of unrecoverable errors occur. The driver will log the reason for any disk
> being killed as a console message. Without further information as to precisely
> why the disks were taken
> From [EMAIL PROTECTED] Sun Aug 13 12:00:21 2000
> [snip]
>
> So, the final unanswered question is why did the Mylex controler failed
> that ungracefully if no disk contains dead blocks ?
> My experimental conclusion is that Linux software RAID is even more
> reliable (the two RAID set
Date: Sun, 13 Aug 2000 17:35:22 +0200
From: Hubert Tonneau <[EMAIL PROTECTED]>
This a report about real production experiment using both Linux
software RAID and a Mylex hardware RAID controler (real production
tend to be even harder than tests, even on a lower load, since
more
better, because I need one.
Also, what experiences do you have with the cable length?
--
Subject: Re: Problem with RAID1 at Boot time and DMA problem
Hi Mathias,
I don't know if this is your problem. But I have had the same DMA problem
when
I overclocked a mother
Hi Mathias,
I don't know if this is your problem. But I have had the same DMA problem when
I overclocked a motherboard and the FSB was not divisible by 33( This was on a
Abit BP6 ). When it was not overclocked DMA worked great.
Craig
Matthias Koelle wrote:
> Hi all,
>
> first of all...sorry
You could probably make it work OK by using initrd and loading the module
with the script, but compiling in support would be much more straightforward.
On Sat, 12 Aug 2000, Christian Bucher wrote:
> Hermann 'mrq1' Gausterer wrote:
> >
> > if you have a raid-root-fs, then
> > i think the proble
i have also some add-ons for the howto:
i have mailed them to michael, but i got no answer :-(
again my points:
1)
at 4.4 Copy the current OS to the new raid device
you should add a hint for creating a empty boot and proc
directory, my rh6.1 box hangs after the first reboot
with the floppy, "
Hermann 'mrq1' Gausterer wrote:
>
> if you have a raid-root-fs, then
> i think the problem is that the kernel cannot load
> the modules unless the rootfilessystem is mounted
> and /lib/modules/ is available. but without
> the module, a mount is not possible. :-o
Looks like raid-root-fs and /
hi christian
if you have a raid-root-fs, then
i think the problem is that the kernel cannot load
the modules unless the rootfilessystem is mounted
and /lib/modules/ is available. but without
the module, a mount is not possible. :-o
have you tried with compiled in support ?
ps: nice to see
Hi Andre,
On Fri, 11 Aug 2000, Andre Hedrick wrote:
> On Fri, 11 Aug 2000, Corin Hartland-Swann wrote:
> > When I try hdparm -m -c -d1 -a, I get the following output:
> >
> > /dev/hdc:
> > setting using_dma to 1 (on)
> > HDIO_SET_DMA failed: Operation not permitted
> > multcount= 16 (on)
Sheesh you have to at least turn on in the kernel at compile time to
attempt dma. Maybe using the chipset tuning code to get it programmed
correctly, would get you to the average 22MB/sec that piix and drive combo
will do.
On Fri, 11 Aug 2000, Corin Hartland-Swann wrote:
>
> Mark,
>
> I'm cr
> -Original Message-
> From: Nick Kay [mailto:[EMAIL PROTECTED]]
> Sent: Friday, August 11, 2000 9:27 AM
> To: Gregory Leblanc
> Cc: [EMAIL PROTECTED]
> Subject: RE: lilo issue
>
> >Can you show us your lilo.conf? Do you have a default label
> set? Does
On Fri, Aug 11, 2000 at 05:11:59PM +0100, Corin Hartland-Swann wrote:
> Partition check:
> hda: hda1 hda2 hda3
> hdb: hdb1
> hdc: [PTBL] [4982/255/63] hdc1
>
> Can anyone explain to me what the [PTBL] bit means? I've been wondering
> this for about 4 years now, and still don't know :)
For al
>
>Can you show us your lilo.conf? Do you have a default label set? Does
>lilo-21.5 include RH's boot from RAID1 patch, or another boot from RAID1
>patch?
No I don't have the default label set - I tend to like having the
option of alternate kernels as a rescue mechanism. I guess I
don't hav
Mark,
I'm cross-posting this to the kernel and RAID lists again, because there's
more information about the problem in here. I hope this is acceptable.
On Thu, 10 Aug 2000, Mark Hahn wrote:
> > Intel 810E Chipset Motherboard (CA810EAL), Pentium III-667, 32M RAM,
> > Maxtor DiamondMax Plus 40 40
> -Original Message-
> From: Nick Kay [mailto:[EMAIL PROTECTED]]
> Sent: Friday, August 11, 2000 6:51 AM
> To: [EMAIL PROTECTED]
> Subject: lilo issue
>
> Hi all,
> I have my raid-1 up and running over two 9gig scsi
> drives under slackware 7.1 with kernel 2.2.16+raid-2.2.6-AO
> fro
Yeah, it's in there. I was blowing past that before... My mistake.
Thanks for the help.
--
On Aug 11 at 14:32, Nick Kay (nick) wrote:
> Subject: Re: How do I tell the kernel I want RAID-5?
>
> At 09:12 11/08/00 -0400, you wrote:
> >This is going to sound pretty s
At 09:12 11/08/00 -0400, you wrote:
>This is going to sound pretty stupid, but here goes anyway...
>
>I got 2.2.16 and the latest patch from kernel.org, applied it and started to
>rebuild.
>
>The question is, where do I tell the kernel to use RAID-5?
>
>I can't see it in the 'make menuconfig' stuf
Gregory Leblanc writes:
...
> > I know that the Linux kernel auto-detects the SCSI devices on boots
> > and assigns them
> >
> > /dev/sda to the first one
> > /dev/sdb to the second one ...
> >
> > and so on.
>
> Yep. Lots of planning done there. :-)
>
> > Doesn't this put a kink
Christoph Kukulies writes:
...
> > Would there be a patch against an oldstyle md-patched kernel somewhere?
> > Since your distribution (Wasn't it RedHat?) is delivering it like that
>
> Yes, RH 6.1
>
> > maybe they should do that?
> >
> > But your best strategy is probably to grab a cl
On 11-Aug-00 Christoph Kukulies wrote:
>> So you have a kernel which is already patched with raid-code and you try
>> to
>
> patched with old style raid code?
Yes -- thats the problem.
SuSE is just the same -- They distribute kernels which include a lot of
patches and you almost can't apply a
On Fri, Aug 11, 2000 at 10:53:11AM +0200, Karl-Heinz Herrmann wrote:
>
> On 11-Aug-00 Christoph Kukulies wrote:
> ># cat /proc/mdstat
> > Personalities : [1 linear] [2 raid0] [3 raid1] [4 raid5]
> > read_ahead not set
> > md0 : inactive
> > md1 : inactive
> > md2 : inactive
> > md3 : inactive
>
On 11-Aug-00 Christoph Kukulies wrote:
># cat /proc/mdstat
> Personalities : [1 linear] [2 raid0] [3 raid1] [4 raid5]
> read_ahead not set
> md0 : inactive
> md1 : inactive
> md2 : inactive
> md3 : inactive
Yes -- thats old style md-raid.
So you have a kernel which is already patched with raid
On Thu, Aug 10, 2000 at 05:07:42PM +0200, Karl-Heinz Herrmann wrote:
> Hi,
>
>
> On 10-Aug-00 Christoph Kukulies wrote:
> >> If the patch is not clean (i.e. rejects) you probably had a kernel
> >> patched
> >> with the old style md-raid. The patch is probably against a clean kernel
> >> source.
On Thursday August 10, [EMAIL PROTECTED] wrote:
> I'm using software raid and since a few developer kernel versions I have problems
>with the multiple device driver;
> now I describe the situation with the newest kernel test6 - messages I get from the
>kernel:
> 1) sizeof(mdp_super_t) = 4096
> -Original Message-
> From: Eric Z. Ayers [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, August 10, 2000 6:46 AM
> To: [EMAIL PROTECTED]
> Subject: Loss of a SCSI device and RAID
>
> I've been wonder how this would work for a while.
>
> I know that the Linux kernel auto-detects the SCSI d
On Thu, 10 Aug 2000, Christoph Kukulies wrote:
>
> I have found a raid patch on a machine in our net, which is:
>
> raid0145-2110-2.2.14.patch
>
> Having used patch under other OSs (BSD) I'm a bit puzzled why
>
> patch -p /usr/src doesn't run smooth). patch stops at every file
> sayin
Hi,
> patch -p /usr/src doesn't run smooth). patch stops at every file
> saying it cannot find the file. Sorry if this may be a
> basic question but things are so different und Linux.
Hmmm... "-p" what? there is supposed to follow a number (at least patch on
DEC OSF4.0 wan
> I'm running RH 6.1 and a 2.2.14 kernel from SCSI drives. Then I have
Have U pached this kernel for the `new' md driver,
wich will work with raidtools v0.9
> 4x 60GB IDE disks which I want to format as a RAID0 array.
Why? I can't see the point in making 1 240Gb filesystem.
> I performed the fo
On Wednesday August 9, [EMAIL PROTECTED] wrote:
>
> Hi there,
>
> I am planning on doing some tests on disk performance for the following:
> 2.4.0-test5
> 2.4.0-test5 (with patches)
>
> My problem is I can't work out whether I need the last one, and if I do
> where to get the patches from.
> * Is there a way of initializing the array without destroying data
> on the first disk, so that reconstruction is commenced at once.
>
> * How to deal with the problem that the first disk is also the
> boot disk.
http://metalab.unc.edu/pub/Linux/docs/HOWTO/Boot+Root+Raid+LILO
su-27
> -Original Message-
> From: Thomas Waldmann [mailto:[EMAIL PROTECTED]]
> Sent: Sunday, August 06, 2000 10:38 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Where to get uptodate raidtool/kernelpatches (2.2.1x) ?
>
> > Sure enough, you've got an old version of t
upgrading from 2.2.14 to 2.2.16. is the 2.2.16 patch to use still the
> one at http://people.redhat.com/mingo/raid-patches/ ?
>
> and is the raidtools-0.90-5 rpm still up to date?
>
> also, does the 2.2.16 patch conflict with the other raid patch that fixes
> that one raid thin
> said, ext2 cannot be resized easily. So unless you run reiserfs or maybe
> ext3 you're SOL right out of the gate.
the post previous said you could resize ext2fs ( which is what I have )
> is properly distributed and no drive gets more than it's share. If you
> remove a small drive and then
> Suppose I have a SW RAID5 over 5 disks, 9.1 G each
> We are getting to a point where we need more space, but the box has no
> more space. So I am wondering how I might go about upgrading the disks to
> bigger capacity volumes. Suppose I insert bigger disks one by one and let
> the array reconst
Title: RE: bigger disks
It is possible to resize the filesystem (ext2), but it is NOT possible to resize the raid 5.
There has been some experimental work done in the area of resizing raid 5 arrays (and raid 0), but it is a risky proposition and never was completed.
You either need to 1
> -Original Message-
> From: Jane Dawson [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, August 08, 2000 2:03 AM
> To: [EMAIL PROTECTED]
> Subject: RE: Problems booting from RAID
>
> Hi,
>
> I am tearing my hair out over this stuff (I should have
> mentioned
> -Original Message-
> From: Kay Salzwedel [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, August 08, 2000 5:46 AM
> To: [EMAIL PROTECTED]
> Subject: disc drive cache
>
> Hello,
>
> does anybody know how to find out about the size of a (EIDE) drives
> cache if the company 'lost' the data she
Hi,
> > I will try to play with next time the server crash. Also maybe it is
> > because of the reconstruction is done in the same time that the fsck.
>
> I think you answered your questions. If the raid ist reconstructing and
> gets changes bu fsck all the time this will slow down.
so, somethi
Hi,
> > raiddev /dev/md0
> > device /dev/sda2
> > device /dev/sdb2
>
> > /dev/hda6 / ext2defaults1 1
> > /dev/hda1 /boot ext2defaults1 2
> > /d
On 08-Aug-00 octave klaba wrote:
> I will try to play with next time the server crash. Also maybe it is
> because of the reconstruction is done in the same time that the fsck.
I think you answered your questions. If the raid ist reconstructing and
gets changes bu fsck all the time this will slow
---
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Gregory Leblanc
> Sent: 07 August 2000 15:06
> To: [EMAIL PROTECTED]
> Subject: RE: Problems booting from RAID
>
>
> > -Original Message-
> > From: Jane Dawson [mailto:[EMAIL PROTECTED]]
>
> Sure enough, you've got an old version of the RAID code. Hop over to
> http://people.redhat.com/mingo/raid-patches/ . I've had no problems running
> Alan Cox's 2.2.17pre13 code with the 2.2.17 patch from Ingo. The raidtools
> 0.90 that you have should work fine, if you have any concerns just
On Mon, 7 Aug 2000, Adam McKenna wrote:
> 2) If I do, will it still broken unless I apply the "2.2.16combo" patch?
> 3) If it will, then how do I resolve the problem with the md.c hunk failing
> with "2.2.16combo"?
If I remember correctly, 2.2.16combo was there to make it possible to use
> -Original Message-
> From: Adam McKenna [mailto:[EMAIL PROTECTED]]
> Sent: Monday, August 07, 2000 9:27 PM
> To: Gregory Leblanc
> Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Re: RAID questions
>
> On Mon, Aug 07, 2000 at 08:07:58PM -0700, Gregory
On Mon, Aug 07, 2000 at 08:07:58PM -0700, Gregory Leblanc wrote:
> I'm a little verbose, but this should answer most of your questions,
> although sometimes in a slightly annoyed tone. Don't take it personally.
There's a difference between being annoyed and being immature. You seem to
have answ
I'm a little verbose, but this should answer most of your questions,
although sometimes in a slightly annoyed tone. Don't take it personally.
> -Original Message-
> From: Adam McKenna [mailto:[EMAIL PROTECTED]]
> Sent: Monday, August 07, 2000 12:10 PM
> To: [EMAIL PROTECTED]
> Cc: [EMAIL
I found it sufficient to apply
http://people.redhat.com/mingo/raid-patches/raid-2.2.16-A0
to the stock 2.2.16 kernel. Works fine with rh6.2 raid tools.
Hope it helps,
--andrew
So, I have the following questions.
1) Do I need to apply the RAID patch to 2.2.16 or not?
2) If I do, w
Hi,
On 07-Aug-00 octave klaba wrote:
> raiddev /dev/md0
> device /dev/sda2
> device /dev/sdb2
> /dev/hda6 / ext2defaults1 1
> /dev/hda1 /boot ext2def
On Mon, Aug 07, 2000 at 08:47:47AM -0700, Gregory Leblanc wrote:
> > -Original Message-
> > From: James Manning [mailto:[EMAIL PROTECTED]]
> > Sent: Saturday, August 05, 2000 6:08 AM
> > To: Linux Raid list (E-mail)
> > Subject: Re: FAQ update
> >
>
> -Original Message-
> From: Carlos Carvalho [mailto:[EMAIL PROTECTED]]
> Sent: Monday, August 07, 2000 10:57 AM
> To: Andrea Arcangeli
> Cc: [EMAIL PROTECTED]
> Subject: Re: raid-2.2.17-A0 cleanup for LVM
>
> >In 2.2.x that's not possible but for _ve
> -Original Message-
> From: James Manning [mailto:[EMAIL PROTECTED]]
> Sent: Saturday, August 05, 2000 6:08 AM
> To: Linux Raid list (E-mail)
> Subject: Re: FAQ update
>
> [Luca Berra]
> > >The patches for 2.2.14 and later kernels are at
> > >
Hi,
> > I realized after a crash, if in /etc/fstab the fsck is
> > on, it takes about 45-50 minutes to check 2x18Go scsi in raidsoft.
> > [...] and make all
> > folks handly (unmount, fsck, reboot) and it takes 6 minutes.
>
> H... Do you have *only one* raid partitions on that drive or are t
On Mon, 7 Aug 2000, Carlos Carvalho wrote:
>So can't this be fixed?
Everything can be fixed, the fact is that I'm not sure if it worth, we'd
better spend efforts in making 2.4.x more stable than overbackporting
new stuff to 2.2.x... The fix precisely to allow raid5 on raid0 could be
pretty local
Andrea Arcangeli ([EMAIL PROTECTED]) wrote on 7 August 2000 16:50:
>On Sun, 6 Aug 2000, Carlos Carvalho wrote:
>
>>Does this patch allow raid5 over raid0? That'd be really wonderful...
>
>Despite it's useful nor not, which 2.?.x?
The latest if possible, but the one your patch applies to if I
> > /dev/md0 17251748 9969024 6406384 61% /home
>
> Which partitions are included in your md0?
raiddev /dev/md0
raid-level 1
nr-raid-disks 2
nr-spare-disks 0
chunk-size 32
persi
Here's one more update of the FAQ. Assuming not too many objections, I'll
send it to Jacob, and see if I can contact the list owner and get a footer
onto this list.
Greg
Linux-RAID FAQ
Gregory Leblanc
gleblanc (at) cu-portland.edu
Revision History
Revision v0
you could write a simple shell or perl script to do this using the
/proc/mdstat as a reference, but it is a bad idea to put in a drive and have
the kernel _assume_ you want to put things back the way they were. i prefer
the control, rather than have the kernel assume.
allan
Emmanuel Galanos <[EM
On 07-Aug-00 octave klaba wrote:
> /dev/md0 17251748 9969024 6406384 61% /home
Which partitions are included in your md0?
K.-H.
E-Mail: Karl-Heinz Herrmann <[EMAIL PROTECTED]>
http://www.kfa-juelich.de/
Hi!
On 07-Aug-00 octave klaba wrote:
> I realized after a crash, if in /etc/fstab the fsck is
> on, it takes about 45-50 minutes to check 2x18Go scsi in raidsoft.
> [...] and make all
> folks handly (unmount, fsck, reboot) and it takes 6 minutes.
H... Do you have *only one* raid partitions
On Sun, 6 Aug 2000, Carlos Carvalho wrote:
>Does this patch allow raid5 over raid0? That'd be really wonderful...
Despite it's useful nor not, which 2.?.x?
In 2.2.x that's not possible but for _very_ silly reasons.
Raid0 in general is a no brainer and fully transparent layer that we can
place
> -Original Message-
> From: Jane Dawson [mailto:[EMAIL PROTECTED]]
> Sent: Monday, August 07, 2000 3:13 AM
> To: [EMAIL PROTECTED]
> Subject: Problems booting from RAID
>
> Hi,
>
> I decided to set up a completely RAID-based system using two
> identical IDE
> hard disks, each with 3 p
> > > disks are less than two weeks old, although I have heard
> of people
> > > having similar problems (disks failing in less than a
> month new from
> > > the factory) with this brand and model I would like
> to get the
>
> In my experience 95% of drive failures occur in the first
Hi!
On 07-Aug-00 Tomasz Gralewski wrote:
> I need help.
> I use on the corporate machine linux kernel of 2.2.16 version.
> The problem is:
> This version of kernel does not support CONFIG_AUTODETECT_RAID.
> I'd like to start the root filesystem from /dev/md0 but the kernel tell
> me durring a bo
On Mon, 7 Aug 2000, Corin Hartland-Swann wrote:
> I have to confess I've never heard of manufacturers offering diagnostic
> utilities for disks... Gregory, can you point me at any examples? Am I
> just being a complete dumbass here?
At least Western Digital does on their ftp address
ftp://ftp.wd
Jeffrey,
On Sun, 6 Aug 2000, Gregory Leblanc wrote:
> On Sun, 6 Aug 2000, Jeffrey Paul wrote:
> > h, the day i had hoped would never arrive has...
It's _always_ waiting :(
> > Aug 2 07:38:27 chrome kernel: raid1: Disk failure on hdg1,
> > disabling device.
OK, so it thinks hdg1 is fault
Chris Mauritz ([EMAIL PROTECTED]) wrote on 6 August 2000 22:17:
>> Does this patch allow raid5 over raid0? That'd be really wonderful...
>
>Huh? What do you mean by that? Raid 5 is essentially Raid 0 with the
>parity bits spread out across all the drives. Running one on top of
>the other
> From [EMAIL PROTECTED] Sun Aug 6 21:45:04 2000
>
> Andrea Arcangeli ([EMAIL PROTECTED]) wrote on 3 August 2000 19:55:
> >>On Aug 2, 7:12pm, Andrea Arcangeli wrote:
> >>} Subject: raid-2.2.17-A0 cleanup for LVM
> >>
> >>> This patch cleanups the new raid code so that we have a chance that
> -Original Message-
> From: Jeffrey Paul [mailto:[EMAIL PROTECTED]]
> Sent: Sunday, August 06, 2000 5:56 PM
> To: [EMAIL PROTECTED]
> Subject: owie, disk failure
>
> h, the day i had hoped would never arrive has...
>
> Aug 2 07:38:27 chrome kernel: raid1: Disk failure on hdg1,
> d
Andrea Arcangeli ([EMAIL PROTECTED]) wrote on 3 August 2000 19:55:
>>On Aug 2, 7:12pm, Andrea Arcangeli wrote:
>>} Subject: raid-2.2.17-A0 cleanup for LVM
>>
>>> This patch cleanups the new raid code so that we have a chance that LVM on
>>> top of RAID will keep working. It's untested at the
> I just try to install a raid5 on 4 disks. The system running is a SuSE
> 6.3 which has kernelpatches but seems to use the older mdadd,
> mdrun,.. commands in the init scripts.
> They Do have raidtools including mkraid and raidstart/stop, but when I
> try to do a mkraid I get:
...
> # cat /proc/m
Yo Luca!
On Sat, 5 Aug 2000, Edward Schernau wrote:
> > i'd add: dont use netscape to fetch patches from mingo's site, it hurts
> > use lynx/wget/curl/lftp
>
> Works fine for me.
We are not worried about you. We are worried about mingos FTP
server. If you access an FPT server with Netscape
[Luca Berra]
> >The patches for 2.2.14 and later kernels are at
> >http://people.redhat.com/mingo/raid-patches/. Use the right patch for
> >your kernel, these patches haven't worked on other kernel revisions
> >yet.
>
> i'd add: dont use netscape to fetch patches from mingo's site
Luca Berra wrote:
> i'd add: dont use netscape to fetch patches from mingo's site, it hurts
> use lynx/wget/curl/lftp
Works fine for me.
--
Edward Schernau,mailto:[EMAIL PROTECTED]
Network Architect http://www.schernau.com
RC5-64#: 243249 e-gold ac
On Fri, Aug 04, 2000 at 01:47:23PM -0700, Gregory Leblanc wrote:
> Here's a new version, with a couple of changes. What other questions get
> asked all the time?
> Greg
>The patches for 2.2.14 and later kernels are at
>http://people.redhat.com/mingo/raid-patches/. Use the right patc
Tim Walberg wrote:
>
> On 08/04/2000 09:54 -0400, Theo Van Dinter wrote:
> >> The usual suggestion is:
> >>
> >> bzip2 -dc | tar -xf -
> >>
>
> or use bzcat, which is exactly the same as bzip2 -dc...
most versions of tar now support either I or y for (un)compress
--
Mathieu Arnold
On 08/04/2000 09:54 -0400, Theo Van Dinter wrote:
>> The usual suggestion is:
>>
>> bzip2 -dc | tar -xf -
>>
or use bzcat, which is exactly the same as bzip2 -dc...
--
+--+--+
| Tim Walberg | [EMAIL PROTECT
On Fri, 4 Aug 2000, Stew Benedict wrote:
> > How does a patched Kernel's /proc/mdstat look like without any
> > raid-drives configured?
>
> Personalities :
> read_ahead not set
> md0 : inactive
> md1 : inactive
> md2 : inactive
> md3 : inactive
This is what an *UNPATCHED* mdstat lo
Personalities :
read_ahead not set
md0 : inactive
md1 : inactive
md2 : inactive
md3 : inactive
On Fri, 4 Aug 2000, Felix Leder wrote:
> How does a patched Kernel's /proc/mdstat look like without any
> raid-drives configured?
>
Stew Benedict
Oooh ooh ooh! FAQ! :-) Unfortunately, it's not on the web yet, but here's
the relevant section:
2.2. How can I tell if I need to patch my kernel?
The easiest way is to check what's in /proc/mdstat. Here's a sample
from a 2.2.x kernel, with the RAID patches applied.
[gleblanc@greg
How about just putting something in like:
"Uncompressing the patch is beyond the scope of this document."
--
Edward Schernau,mailto:[EMAIL PROTECTED]
Network Architect http://www.schernau.com
RC5-64#: 243249 e-gold acct #:131897
On Fri, Aug 04, 2000 at 09:48:18AM +0530, Abhishek Khaitan wrote:
> Can;t we use bunzip2 instead of playing with tar? And after bunzip2, try tar
> -x kernel-2.2.16.tar ?
The usual suggestion is:
bzip2 -dc | tar -xf -
s/bzip2/gzip/ or s/bzip2/uncompress/ as necessary
--
Randomly Generated Ta
Can;t we use bunzip2 instead of playing with tar? And after bunzip2, try tar
-x kernel-2.2.16.tar ?
> -Original Message-
> From: James Manning [SMTP:[EMAIL PROTECTED]]
> Sent: Thursday, August 03, 2000 10:35 AM
> To: [EMAIL PROTECTED]
> Subject: Re: FAQ
> -Original Message-
> From: James Manning [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, August 03, 2000 10:35 AM
> To: [EMAIL PROTECTED]
> Subject: Re: FAQ
>
> [Marc Mutz]
> > >2.4. How do I apply the patch to a kernel that I just
> downlo
1 - 100 of 5524 matches
Mail list logo
