Re: RAID questions
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 Ingo's older raid patches on 2.2.16 (before raid-2.2.16-A0 was released). I'm not 100% sure, though. > This is a production system I am working on here. I can't afford to have it > down for an hour or two to test a new kernel. I'd rather not be working with > this mess to begin with, but unfortunately this box was purchased before I > started this job, and whoever ordered it decided that software raid was > "Good enough". A test machine comes in handy. Not to actually test the new RAID code (we did/do that already ;) ), but just to train handling of SW raid. > I am not subscribed to either list so CC's are desirable. However if you > don't want to CC then you don't have to -- I'll just read the archives. > That is, if someone fixes the "Mailing list archives" link on www.linux.org > to point to someplace that exists and actually has archives. IMHO, if you need (or want) to work with SW raid, it would be better to subscribe. It's not all that much traffic here and (usually) the stuff we get here is relevant (with exception of too many questions on patches location, but that should be fixed anyway). Besides, any real problems, bug reports, warnings appear here very soon. D.
RE: RAID questions
> -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 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 answered everything with maturity, so no offense taken. Phew. Sometimes I come off poorly, and people flip out. I hate that. > I did a search on google. The majority of posts I was able > to find mentioned > a 2.2.15 patch which could be applied to 2.2.16 as long as > several hunks were > hand-patched. Personally, I don't particularly like > hand-patching code. > Especially when the data that my job depends on is involved. Hmm, there have been some recently (I think) for the 2.2.16 kernels. I've not kept up on my testing (no time), so I'm still running 2.2.14. > > > 2) The current 2.2.16 errata lists a problem with md.c which > > > is fixed by the > > > patch "2.2.16combo". > > > > I believe that md software RAID applies to the old RAID > code. The RAID > > stuff has been VERY good for quite a while now. > > The howto on linux.org listed > ftp://www.fi.kernel.org/pub/linux/daemons/raid > as the "official" location for the RAID patches. The patches > located there > only went up to 2.2.11. In fact, looking now, the > linuxdoc.org howto lists > the same location. True enough, it's out of date. I'm going to try to get Jacob to point to my FAQ, but I haven't gotten enough feedback just yet. > the first place. In retrospect, I suppose it was a stupid > question, but I'd > rather be safe than sorry. There are no stupid questions, only stupid answers. :-) Amongst the other 45 kernel compiles I've got to do this week, I'll try to find some time to look at the 2.2.16 patch, and see if it works nicely with Ingo's RAID patch on my system. > Thanks for the link. However as mentioned above the howto > there still gives > the incorrect location for current kernel patches. Sorry, I can't fix that. I just help put the HOWTOs online, I don't write them (at least not much). > > > So, I have the following questions. > > > > > > 1) Do I need to apply the RAID patch to 2.2.16 or not? > > > > Do you want new RAID, or old RAID? > > Well, the box won't boot with the stock MD driver. In that case, you need to patch your kernel. :) I think you mentioned that you'd already found the 2.2.16 patch, so run with that, and see what happens. > > > 2) If I do, will it still broken unless I apply the > > > "2.2.16combo" patch? D'uh, I'll look and see what it does for me, and report back. Probably NOT tomorrow, but some time this week. Maybe somebody else will step forward with results before I get to it. > I was hoping my post would serve as a reminder to those on > the list who are in > charge of maintaining those resources. I dunno, the kernel list just scares me. There's too much extraneous stuff that goes through there anyway, and 90% of it is over my head. Speaking of which, I'll trim them from the list, after this email (since somebody there might have tried more patches than myself). > > If you don't know what you're doing, GET A TEST MACHINE. > Sorry to yell, but > > don't play with things on production boxes. Find a nice > cheapie P-133 type > > box, grab a couple of drives, and test out RAID that way. > Don't do that one > > production boxes. If somebody can't come up with $200 to > get you a test > > box, then spring for it yourself, and get a decent X term for home. [SNIP] > My current prime objective is getting rid of the current kernel we are > running, as I am having other problems with the box that I > think are kernel > related. (EAGAIN errors -- resource temporarily unavailable > when trying to > make a TCP connection to a remote host after about 5 days of > uptime) A test > box would be nice but it could take weeks to obtain one. > Personally, I'd > rather avoid having to go in at 2:30 in the morning again to > reboot the box. Ah, sorry about that one, it might have been a little out of line. However, do get yourself a test box, doesn't even need to be the same hardware, just something that you can break. > > I looked at geocrawler, b
Re: RAID questions
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 answered everything with maturity, so no offense taken. > > Hello, > > > > I consider the current state of affairs with Software-RAID to > > be unbelievable. > > It's not as bad as you think. :-) Maybe not to someone who follows the list regularly, but for someone who needs to get things accomplished, it's pretty bad. > > 1) The current RAID-Howto (on www.linux.org) does not > > indicate the correct > > location of RAID patches. I had to go searching all over > > the web to find > > the 2.2.16 RAID patch. > > Did you try reading the archives for the Linux-RAID list? I've started on a > FAQ that will be updated at very least monthly, and posted to linux-raid. I did a search on google. The majority of posts I was able to find mentioned a 2.2.15 patch which could be applied to 2.2.16 as long as several hunks were hand-patched. Personally, I don't particularly like hand-patching code. Especially when the data that my job depends on is involved. > > 2) The current 2.2.16 errata lists a problem with md.c which > > is fixed by the > > patch "2.2.16combo". > > I believe that md software RAID applies to the old RAID code. The RAID > stuff has been VERY good for quite a while now. The howto on linux.org listed ftp://www.fi.kernel.org/pub/linux/daemons/raid as the "official" location for the RAID patches. The patches located there only went up to 2.2.11. In fact, looking now, the linuxdoc.org howto lists the same location. > > 3) The patch "2.2.16combo" FAILS if the RAID patch has > > already been applied. > > Ditto with the RAID patches to md.c if the 2.2.16combo > > patch has already > > been applied. > > Perhaps they're not compatible, or perhaps one includes the other? Have you > looked at the patches to try to figure out why they don't work? I'm NOT a > hacker, but I can certainly try to figure out why patches don't work. I looked at them. It appears as though the RAID patch changes the relevant section to something totally different than it was before, so that the patch can't be applied, even with an offset. This is why I asked the question in the first place. In retrospect, I suppose it was a stupid question, but I'd rather be safe than sorry. > > 4) The kernel help for all of the MD drivers lists a nonexistant > > Software-RAID mini-howto, which is supposedly located at > > ftp://metalab.unc.edu/pub/Linux/docs/HOWTO/mini. There is no such > > document at this location. > > There are 2 Software-RAID HOWTOs available there, although they are 1 > directory higher than that URL. For the code included in the stock kernels, > see ftp://metalab.unc.edu/pub/Linux/docs/HOWTO/Software-RAID-0.4x-HOWTO. > For the new RAID code by Ingo and others, see > ftp://metalab.unc.edu/pub/Linux/docs/HOWTO/Software-RAID-HOWTO. Both of > these documents are easily available from http://www.LinuxDoc.org/ Thanks for the link. However as mentioned above the howto there still gives the incorrect location for current kernel patches. > > 5) The kernel help also does not make it clear that you even > > need a RAID > > patch with current kernels. It is implied that if you > > "Say Y here" then > > your kernel will support RAID. This problem is > > exacerbated by the missing > > RAID patches at the location specified in the actual > > Software-RAID-Howto. > > No, you don't NEED to patch your kernel to get RAID (md raid, that is) > working. You DO need to patch the kernel if you want the new RAID code. > Everyone on the Linux-RAID list will recommend the new code, I don't know > about anybody else. > > > So, I have the following questions. > > > > 1) Do I need to apply the RAID patch to 2.2.16 or not? > > Do you want new RAID, or old RAID? Well, the box won't boot with the stock MD driver. > > 2) If I do, will it still broken unless I apply the > > "2.2.16combo" patch? > > If you apply the combo patch, that will fix things with the old code (I > think, have not verified this yet). If you apply the RAID patch (from the > location above), then you don't need to worry about the fixes in the > 2.2.16combo. > > > 3) If it will, then how do I resolve the problem with the > > md.c hunk failing > > with "2.2.16combo"? > > Apply manually? Just take a look at the .rej files (from /usr/src/linux do > a 'find . -name "*rej*"') and see what failed to apply. I generally open a > split pane editor, (for emacs, just put two file names on the command line), > and see if I can find where the patch failed, and try to add the > missing/remove the extraneous lines by hand. It's worked so far. See above. > > 4) Is there someone I can contact who can
RE: RAID questions
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 PROTECTED] > Subject: RAID questions > > Hello, > > I consider the current state of affairs with Software-RAID to > be unbelievable. It's not as bad as you think. :-) > 1) The current RAID-Howto (on www.linux.org) does not > indicate the correct > location of RAID patches. I had to go searching all over > the web to find > the 2.2.16 RAID patch. Did you try reading the archives for the Linux-RAID list? I've started on a FAQ that will be updated at very least monthly, and posted to linux-raid. > 2) The current 2.2.16 errata lists a problem with md.c which > is fixed by the > patch "2.2.16combo". I believe that md software RAID applies to the old RAID code. The RAID stuff has been VERY good for quite a while now. > 3) The patch "2.2.16combo" FAILS if the RAID patch has > already been applied. > Ditto with the RAID patches to md.c if the 2.2.16combo > patch has already > been applied. Perhaps they're not compatible, or perhaps one includes the other? Have you looked at the patches to try to figure out why they don't work? I'm NOT a hacker, but I can certainly try to figure out why patches don't work. > 4) The kernel help for all of the MD drivers lists a nonexistant > Software-RAID mini-howto, which is supposedly located at > ftp://metalab.unc.edu/pub/Linux/docs/HOWTO/mini. There is no such > document at this location. There are 2 Software-RAID HOWTOs available there, although they are 1 directory higher than that URL. For the code included in the stock kernels, see ftp://metalab.unc.edu/pub/Linux/docs/HOWTO/Software-RAID-0.4x-HOWTO. For the new RAID code by Ingo and others, see ftp://metalab.unc.edu/pub/Linux/docs/HOWTO/Software-RAID-HOWTO. Both of these documents are easily available from http://www.LinuxDoc.org/ > 5) The kernel help also does not make it clear that you even > need a RAID > patch with current kernels. It is implied that if you > "Say Y here" then > your kernel will support RAID. This problem is > exacerbated by the missing > RAID patches at the location specified in the actual > Software-RAID-Howto. No, you don't NEED to patch your kernel to get RAID (md raid, that is) working. You DO need to patch the kernel if you want the new RAID code. Everyone on the Linux-RAID list will recommend the new code, I don't know about anybody else. > So, I have the following questions. > > 1) Do I need to apply the RAID patch to 2.2.16 or not? Do you want new RAID, or old RAID? > 2) If I do, will it still broken unless I apply the > "2.2.16combo" patch? If you apply the combo patch, that will fix things with the old code (I think, have not verified this yet). If you apply the RAID patch (from the location above), then you don't need to worry about the fixes in the 2.2.16combo. > 3) If it will, then how do I resolve the problem with the > md.c hunk failing > with "2.2.16combo"? Apply manually? Just take a look at the .rej files (from /usr/src/linux do a 'find . -name "*rej*"') and see what failed to apply. I generally open a split pane editor, (for emacs, just put two file names on the command line), and see if I can find where the patch failed, and try to add the missing/remove the extraneous lines by hand. It's worked so far. > 4) Is there someone I can contact who can update publically > available > documentation to make it easier for people to find what > they're looking > for? Not sure about the stuff in the Linux kernel sources, but I'd assume that somebody on the Linux-kernel list can do that. As for the Software-RAID HOWTO, tell Jacob (he IS on the raid list). Again, I've created a FAQ for the Linux-raid mailing list, which should cover many of these questions. I'll be asking the list maintainer about putting a footer onto posts to the list, but I'm not sure about the feasibility of that just yet. > This is a production system I am working on here. I can't > afford to have it > down for an hour or two to test a new kernel. I'd rather not > be working with > this mess to begin with, but unfortunately this box was > purchased before I > started this job, and whoever ordered it decided that > software raid was > "Good enough". If you don't know what you're doing, GET A TEST MACHINE. Sorry to yell, but don't play with things on production boxes. Find a nice cheapie P-133 type box, grab a couple of drives, and test out RAID that way. Don't do that one production boxes. If somebody can't come up with $200 to get you a test box, then spring for it yourself, and get a decent X term for home. As for Software RAID being good enough, I find that to be true. If I needed hot swap,
Re: RAID questions
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, 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"? 4) Is there someone I can contact who can update publically available documentation to make it easier for people to find what they're looking for? This is a production system I am working on here. I can't afford to have it down for an hour or two to test a new kernel. I'd rather not be working with this mess to begin with, but unfortunately this box was purchased before I started this job, and whoever ordered it decided that software raid was "Good enough". I am not subscribed to either list so CC's are desirable. However if you don't want to CC then you don't have to -- I'll just read the archives. That is, if someone fixes the "Mailing list archives" link on www.linux.org to point to someplace that exists and actually has archives. Thanks for your time, --Adam - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
RE: Raid Questions
At 04:43 PM 9/17/1999 +0100, you wrote: > > I'm confused. You're using 2 devices of apparently equal size (which I > assume > > means they're the same kind of device). However, you have one defined > as an > > IDE disk and one defined as a SCSI disk in your raidtab file. Could > > that be the > > problem? > >You can mix SCSI and IDE in a software-RAID. It is more likely to be that in >upgrading to 2.2.12, Kenny didn't realize that he had to patch the kernel with >the raid0145 patch (from >ftp://ftp..kernel.org/pub/linux/daemons/raid/alpha), because the >stock RedHat 2.2.5 kernels came ready-patched. Will the 2.2.11 patch work on the 2.2.12 kernel? latest patch seems to be 2.2.11 === 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: Raid Questions
> I'm confused. You're using 2 devices of apparently equal size (which I assume > means they're the same kind of device). However, you have one defined as an > IDE disk and one defined as a SCSI disk in your raidtab file. Could > that be the > problem? You can mix SCSI and IDE in a software-RAID. It is more likely to be that in upgrading to 2.2.12, Kenny didn't realize that he had to patch the kernel with the raid0145 patch (from ftp://ftp..kernel.org/pub/linux/daemons/raid/alpha), because the stock RedHat 2.2.5 kernels came ready-patched. Cheers, Bruno Prior [EMAIL PROTECTED] > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Chris Mauritz > Sent: 17 September 1999 01:27 > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] > Subject: Re: Raid Questions > > > I'm confused. You're using 2 devices of apparently equal size (which I assume > means they're the same kind of device). However, you have one defined as an > IDE disk and one defined as a SCSI disk in your raidtab file. Could > that be the > problem? > > > From [EMAIL PROTECTED] Thu Sep 16 19:38:15 1999 > > > > Hello -- there is a lot of confusing and incorrect howto's, etc. out there. > > I was using raid0 with kernel 2.2.5 just fine. I have upgraded the > > kernel to 2.2.12 in an effort to solve a SMP kernel gen problem, and I can > > not get raid0 to work at all.. Any advice, including rtm is fine if > > given the real manual or doc.
Re: Raid Questions
I'm confused. You're using 2 devices of apparently equal size (which I assume means they're the same kind of device). However, you have one defined as an IDE disk and one defined as a SCSI disk in your raidtab file. Could that be the problem? > From [EMAIL PROTECTED] Thu Sep 16 19:38:15 1999 > > Hello -- there is a lot of confusing and incorrect howto's, etc. out there. > I was using raid0 with kernel 2.2.5 just fine. I have upgraded the > kernel to 2.2.12 in an effort to solve a SMP kernel gen problem, and I can > not get raid0 to work at all.. Any advice, including rtm is fine if > given the real manual or doc. > > Kenny > > fdisk - > > Disk /dev/sdb: 255 heads, 63 sectors, 527 cylinders > Units = cylinders of 16065 * 512 bytes > >Device BootStart EndBlocks Id System > /dev/sdb1 1 527 4233096 fd Unknown > > Disk /dev/sdc: 255 heads, 63 sectors, 527 cylinders > Units = cylinders of 16065 * 512 bytes > >Device BootStart EndBlocks Id System > /dev/sdc1 1 527 4233096 fd Unknown > > > Config: > > Redhat 6.0 with adapetic scsi. I have the partitions defined > as type fd (fdisk indicates unknown type). > > /proc/mdstat indicates: > > Personalities : [1 linear] [2 raid0] [3 raid1] > read_ahead not set > md0 : inactive > md1 : inactive > md2 : inactive > md3 : inactive > > mkraid (raidtools 0.90) gives me: > > # ./mkraid --really-force -c /etc/raidtab /dev/md1 > DESTROYING the contents of /dev/md1 in 5 seconds, Ctrl-C if unsure! > handling MD device /dev/md1 > analyzing super-block > disk 0: /dev/sdb1, 4233096kB, raid superblock at 4233024kB > disk 1: /dev/sdc1, 4233096kB, raid superblock at 4233024kB > mkraid: aborted, see the syslog and /proc/mdstat for potential clues. > My raidtab follows: > > raiddev /dev/md0 > raid-level 0 # > nr-raid-disks 2 # > persistent-superblock 1 # set this to 1 if you want autostart > chunk-size 8 > device /dev/hdb1 > raid-disk 0 > device /dev/sda1 > raid-disk 1 > > raiddev /dev/md1 > raid-level 0 # > nr-raid-disks 2 # > persistent-superblock 1 # set this to 1 if you want autostart > chunk-size 8 > device /dev/sdb1 > raid-disk 0 > device /dev/sdc1 > raid-disk 1 > > -- Christopher Mauritz [EMAIL PROTECTED]
Re: Raid Questions
On Thu, 16 Sep 1999 [EMAIL PROTECTED] wrote: > Hello -- there is a lot of confusing and incorrect howto's, etc. out there. > I was using raid0 with kernel 2.2.5 just fine. I have upgraded the > kernel to 2.2.12 in an effort to solve a SMP kernel gen problem, and I can > not get raid0 to work at all.. Any advice, including rtm is fine if > given the real manual or doc. see http://ostenfeld.dk/~jakob/Software-RAID.HOWTO/ good luck! *---(*)---**--> Francisco J. Montilla System & Network administrator [EMAIL PROTECTED] irc: pukkaSevilleSpain INSFLUG (LiNUX) Coordinator: www.insflug.org - ftp.insflug.org
