RE: bigger disks

2000-08-08 Thread Jones, Clay
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)

RE: help, help, help

2000-02-11 Thread Jones, Clay
Title: RE: help, help, help Here is the main clue as to what is wrong ** #cat /proc/mdstat Personalities : [1 linear] [2 raid0] [3 raid1] read_ahead not set md0 : inactive md1 : inactive md2 : inactive md3 : inactive Any time you see a /proc/mdstat listing md0 through md3 with

RE: Possible memory leak + setup questions

2000-01-19 Thread Jones, Clay
Title: RE: Possible memory leak + setup questions According Ingo Molnar the raid maintainer: here is the first alpha version of the '2.4 RAID merge' patch against pre4-2.3.40: http://www.redhat.com/~mingo/ibc-ext2-raid-2.3.40-N1 And for 2.2.14 here is the patch.

RE: Welcome to linux-raid

2000-01-08 Thread Jones, Clay
Title: RE: Welcome to linux-raid Actually, that's incorrect (Sorry David). For the 2.2.14 kernel, Ingo Molinar has released a specific patch. He sent it out to the board a couple days ago. http://www.redhat.com/~mingo/raid-2.2.14-B1 Get that patch, apply it to the 2.2.14 kernel, then raid

RE: Where has the Autodetect RAID partitions option in the 2.3.x kernels gone?

1999-12-15 Thread Jones, Clay
Title: RE: Where has the Autodetect RAID partitions option in the 2.3.x kernels gone? I do not belive that the raid 0.90 has been ported to the 2.3 series of kernels yet. Clay -Original Message- From: Nigel Tamplin [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 15, 1999

RE: where is autodetect raid code in 2.3.19??

1999-10-11 Thread Jones, Clay
Title: RE: where is autodetect raid code in 2.3.19?? Just a wild guess, but I'd assume that the core kernel guys still have not decided to add the raid patches to main kernel base. (None of the stock 2.2.x kernels have the latest raid in them). I've seen messages of people applying the

RE: raid 1 problem with kernel 2.2.12

1999-10-09 Thread Jones, Clay
Title: RE: raid 1 problem with kernel 2.2.12 Stock kernels from kernel.org do not have the latest raid patches in them (Don't ask). You have to get the patch for 2.2.11 and apply it to 2.2.12 with one error (anser N twice). Patches are found in pub/linux/daemons/alpha. Clay

RE: Raid0

1999-10-08 Thread Jones, Clay
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

RE: Prob with RAID1 - RedHat 6.0 - Kernel 2.2.12

1999-10-02 Thread Jones, Clay
Title: RE: Prob with RAID1 - RedHat 6.0 - Kernel 2.2.12 It won't change until Linus and the rest of the kernel team decide to add the new raid to released kernels. I know when I first started looking into raid, I'd heard all of the autodiscover stuff for over a year, and just naturally

RE: Prob with RAID1 - RedHat 6.0 - Kernel 2.2.12

1999-10-02 Thread Jones, Clay
version are dated 11-07-1997 ! and tens of alpha verision are available since...) Is there a political problem with the kernel team ? At 12:45 02/10/99 -0700, Jones, Clay wrote: It won't change until Linus and the rest of the kernel team decide to add the new raid to relesed kernels. I know

RE: undocumented error from /proc/mdstat: read_ahead not set

1999-10-01 Thread Jones, Clay
Title: RE: undocumented error from /proc/mdstat: read_ahead not set You are using the new raid tools (version 90) without having the kernel patched with the new raid code. Kernel patches are found in ftp://ftp.us.kernel.org/pub/linux/daemons/raid/alpha Clay -Original Message-

RE: experimenting with raid

1999-09-28 Thread Jones, Clay
Title: RE: experimenting with raid You need to use raidhotadd /dev/mdx /dev/lox to add the loop device back onto the raid array. It will not automatically get sucked back in. If it happen to be that a hard disk had crashed, you would first need to do a raidhotremove /dev/mdx /dev/hdax to