Re: not finding extra partitions
removed the cable from one drive and rebooted for a test. All seemed to go well, system ran in degraded mode. When I reconnected drive, only 1 of the 3 partitions on the drive are recognized. 2 of my 3 /dev/md- arrays still run in degraded mode. How can I force a "good" partition so the array will rebuild? raidhotadd /dev/mdX /dev/sd?? then it reconstructs. -sv
Re: RAID 0.90+ status for 2.4 (pre) ??
On Wed, 22 Mar 2000, Matti Aarnio wrote: I myself really need working RAID(1) code, but current 2.3.99 kernels don't even have compilable RAID1 code in them :-( Any change for raid-code keepers to get their act together and publish something working ? Or must I simply reinstall my development machines without RAID ? I myself can't update missing LFS bits into the current kernel unless I get something bootable (and usable) for my machines. /Matti Aarnio [EMAIL PROTECTED] I am still trying to build .99 but I think I found the raid problem with md.c. If you check md_error and patch the printk so that __builtin_return_address(x) is not called then the code compiles. I have not yet tested it. Alvin Starr || voice: (416)585-9971 Interlink Connectivity|| fax: (416)585-9974 [EMAIL PROTECTED] ||
Locking the devices
Title: Locking the devices Hi all, I am making the raid driver, that passes calls to the disk drivers selected for the raid. The problem I am facing is that once I have opened the devices below no other program should be able to open the devices. So, how can I lock the devices in the raid?
Re: not finding extra partitions
Thanks Seth! I dug through the linux-raid archives last night and found the answer too. Got everything resynced last night. I am using RH 6.1 2.2.12-20 with a Promise EIDE-MaxII with 3 Maxtor 51536U3 ide drives; 2 of these drives on Promise card, and 3rd on secondary of motherboard. All seems to be working well. Total cost: 150*3 + 26 = 476 dollars for 30Gig of RAID5. /dev/md0 - /dev/hdc1 /dev/hde1 /dev/hdg1 mounted as /usr /dev/md1 - /dev/hdc5 /dev/hde5 /dev/hdg5 mounted as /home /dev/md2 - /dev/hdc6 /dev/hde6 /dev/hdg6 mounted as /usr1 I have a SOHO and am using the RAID5 as a "network appliance". /usr1/xtools exported as nfs and SAMBA - contains Solaris and win32 cross development tools. /usr1/rtosdev exported as nfs and SAMBA - contains development code /home exported as nfs and SAMBA - misc and NIS home directory Has anyone seen any problems in long term use of linux RAID5 in this or any other environment? Regards, Doug Egan Seth Vidal wrote: removed the cable from one drive and rebooted for a test. All seemed to go well, system ran in degraded mode. When I reconnected drive, only 1 of the 3 partitions on the drive are recognized. 2 of my 3 /dev/md- arrays still run in degraded mode. How can I force a "good" partition so the array will rebuild? raidhotadd /dev/mdX /dev/sd?? then it reconstructs. -sv -- --- +-+ | Douglas EganWind River Systems, Inc.| +-+
Re: not finding extra partitions
I dug through the linux-raid archives last night and found the answer too. Got everything resynced last night. I am using RH 6.1 2.2.12-20 with a Promise EIDE-MaxII with 3 Maxtor 51536U3 ide drives; 2 of these drives on Promise card, and 3rd on secondary of motherboard. All seems to be working well. Total cost: 150*3 + 26 = 476 dollars for 30Gig of RAID5. /dev/md0 - /dev/hdc1 /dev/hde1 /dev/hdg1 mounted as /usr /dev/md1 - /dev/hdc5 /dev/hde5 /dev/hdg5 mounted as /home /dev/md2 - /dev/hdc6 /dev/hde6 /dev/hdg6 mounted as /usr1 I have a SOHO and am using the RAID5 as a "network appliance". /usr1/xtools exported as nfs and SAMBA - contains Solaris and win32 cross development tools. /usr1/rtosdev exported as nfs and SAMBA - contains development code /home exported as nfs and SAMBA - misc and NIS home directory Has anyone seen any problems in long term use of linux RAID5 in this or any other environment? if you continue to use 2.2.12-20 and are planning to do nfs you are going to run into problems - go to nfs.sourceforge.net for more information. -sv
newbie needs help
hallo I´m trying to get a RAID5 system running but i`ve got problems setting up the /dev/md. I´m using a SuSE 6.3, Linux version 2.2.13 ([EMAIL PROTECTED]) (gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)) #1 Mon Nov 8 15:51:29 CET 1999 , and raidtools v.0.90.2 -Alpha, 27th february 1999. My problem is that i don`t know wether these 2 parts fit together. After booting the standard kernel there is a proc/mdstat . When I try : root@foo mkraid --really-force /dev/md0 DESTROYING the contents of /dev/md0 in 5 seconds, Ctrl-C if unsure! handling MD device /dev/md0 analyzing super-block disk 0: /dev/sda3, 8570677kB, raid superblock at 8570560kB disk 1: /dev/sdb3, 8570677kB, raid superblock at 8570560kB disk 2: /dev/sdc3, 8570677kB, raid superblock at 8570560kB mkraid: aborted, see the syslog and /proc/mdstat for potential clues. Is it the wrong raidtool version, is it the wrong kernel patch (SuSE does not respond on my queries), is there a problem with my partition configuration (i.e. wich type has to be set on the partitions being used for RAID (ext2,fd ??)) thanks wo *** * Wolfram Lassnig, SSG - Software Service Group * Untermarkt 9, A-6410 Telfs, Austria * Tel: +43-5262-64727Fax: +43-5262-64926 * email: [EMAIL PROTECTED]www.ssg.co.at ***
Re: newbie needs help
[Wolfram Lassnig] I´m using a SuSE 6.3, Linux version 2.2.13 ([EMAIL PROTECTED]) is it the wrong kernel patch (SuSE does not respond on my queries) SuSE doesn't patch their kernels Excellent software raid howto: http://linuxdoc.org/HOWTO/Software-RAID-HOWTO.html kernel 2.2.14 patch: http://people.redhat.com/mingo/raid-patches/raid-2.2.14-B1 James
Re: newbie needs help
Wolfram Lassnig wrote: hallo I´m trying to get a RAID5 system running but i`ve got problems setting up the /dev/md. I´m using a SuSE 6.3, Linux version 2.2.13 ([EMAIL PROTECTED]) (gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)) #1 Mon Nov 8 15:51:29 CET 1999 , and raidtools v.0.90.2 -Alpha, 27th february 1999. My problem is that i don`t know wether these 2 parts fit together. After booting the standard kernel there is a proc/mdstat . When I try : root@foo mkraid --really-force /dev/md0 DESTROYING the contents of /dev/md0 in 5 seconds, Ctrl-C if unsure! handling MD device /dev/md0 analyzing super-block disk 0: /dev/sda3, 8570677kB, raid superblock at 8570560kB disk 1: /dev/sdb3, 8570677kB, raid superblock at 8570560kB disk 2: /dev/sdc3, 8570677kB, raid superblock at 8570560kB mkraid: aborted, see the syslog and /proc/mdstat for potential clues. Is it the wrong raidtool version, is it the wrong kernel patch (SuSE does not respond on my queries), SuSE has still old-style raid in it's kernel, AFAIK. You have to patch the kernel yourself and install raidtools.rpm (it looks as though you have already done that). Leave your hands off mdtools.rpm!! is there a problem with my partition configuration (i.e. wich type has to be set on the partitions being used for RAID (ext2,fd ??)) snip fd is correct, but it's the hexadecimal value of the partition type byte, not something like ext2 or iso9660. -- Marc Mutz [EMAIL PROTECTED]http://marc.mutz.com/Encryption-HOWTO/ University of Bielefeld, Dep. of Mathematics / Dep. of Physics PGP-keyID's: 0xd46ce9ab (RSA), 0x7ae55b9e (DSS/DH)
Software RAID with kernel 2.2.14
Hello, since two days (and nights) I try to get software RAID 0.90 running on SuSE-Linux with a standard kernel 2.2.14 with an raid patch found at .../mingus running. I can try what I want, every time the following error appears: mkraid: aborted, see the syslog and /proc/mdstat for potential clues but there is no hint. here my raidtab raiddev /dev/md0 raid-level 5 nr-raid-disks 7 nr-spare-disks 0 persistent-superblock 1 parity-algorithmleft-symmetric chunk-size 32 device /dev/hda3 raid-disk 0 device /dev/hdb3 raid-disk 1 device /dev/hdc3 raid-disk Does anyone know what's going wrong? I would be very happy if you can help me! regards Rainer Frohne
Re: Software RAID with kernel 2.2.14
probably, you are not REALLY running a patched kernel. if you cat /proc/mdstat and see stuff about /dev/md0 being 'inactive' then you are running an unpatched kernel, need to check lilo and make sure the new kernel is there. also check your patch for rejects and your config to have raid built in. if you see: Personalities : read_ahead not set unused devices: none instead, then you are running a patched kernel, and your problem must lie elsewhere (try recompiling the raid tools from source) allan Rainer Frohne [EMAIL PROTECTED] said: Hello, since two days (and nights) I try to get software RAID 0.90 running on SuSE-Linux with a standard kernel 2.2.14 with an raid patch found at .../mingus running. I can try what I want, every time the following error appears: mkraid: aborted, see the syslog and /proc/mdstat for potential clues but there is no hint. here my raidtab raiddev /dev/md0 raid-level 5 nr-raid-disks 7 nr-spare-disks 0 persistent-superblock 1 parity-algorithmleft-symmetric chunk-size 32 device /dev/hda3 raid-disk 0 device /dev/hdb3 raid-disk 1 device /dev/hdc3 raid-disk Does anyone know what's going wrong? I would be very happy if you can help me! regards Rainer Frohne
