[Bug 280972] New: DMRAID support!
https://bugzilla.novell.com/show_bug.cgi?id=280972 Summary: DMRAID support! Product: openSUSE 10.3 Version: Alpha 4plus Platform: x86-64 OS/Version: openSUSE 10.2 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: c.exe@gmx.de QAContact: qa@suse.de Hi OpenSuSE Team! The only thing that is missing (in my opinion) in OpenSuSE 10.2 is the SATA RAID support. So could you please include into 10.3 support for SATA Fake RAID. It uses DMRAID, since some parts are software controlled. Please include it at boot time, like other distro´s do (for example: Fedora Core 6), cause i want to use OpenSuSE 10.3 with a NVIDIA NFORCE 4 SATA2 Chipset, using two Seagate 160GB disks as RAID0. Thanks a lot. MorpheusB. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=280972 mhorvath@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team- |mkoenig@novell.com |screening@forge.provo.novell| |.com | Severity|Normal |Enhancement -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=280972 mkoenig@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |c.exe@gmx.de ------- Comment #1 from mkoenig@novell.com 2007-06-11 04:53 MST ------- Can you please specify what exactly is missing? We have dmraid and we have a boot script. If this does not work for you please describe the problems. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=280972#c2
Richard Creighton
https://bugzilla.novell.com/show_bug.cgi?id=280972#c3
--- Comment #3 from Richard Creighton
https://bugzilla.novell.com/show_bug.cgi?id=280972#c4
Matthias Koenig
https://bugzilla.novell.com/show_bug.cgi?id=280972#c5
--- Comment #5 from Richard Creighton
https://bugzilla.novell.com/show_bug.cgi?id=280972#c6
--- Comment #6 from Matthias Koenig
https://bugzilla.novell.com/show_bug.cgi?id=280972#c7
--- Comment #7 from Richard Creighton
https://bugzilla.novell.com/show_bug.cgi?id=280972#c8
Matthias Koenig
https://bugzilla.novell.com/show_bug.cgi?id=280972
Matthias Koenig
https://bugzilla.novell.com/show_bug.cgi?id=280972
Matthias Koenig
https://bugzilla.novell.com/show_bug.cgi?id=280972#c9
--- Comment #9 from Thomas Fehr
https://bugzilla.novell.com/show_bug.cgi?id=280972#c10
--- Comment #10 from Richard Creighton
https://bugzilla.novell.com/show_bug.cgi?id=280972#c11
Richard Creighton
https://bugzilla.novell.com/show_bug.cgi?id=280972#c12
--- Comment #12 from Richard Creighton
Well, to be honest this sounds all unclear to me. What you are describing is a regression, so I will reopen the bug for further analysis. We need to get this clear first to get some progress in this issue.
1. You are talking about dmraid and RAID5. dmraid is a user space tool, which sets up a virtual RAID device via device-mapper which is a generic layer in the kernel to stack up logical devices. It does not need device dependent drivers; what it does is simply reading the RAID configuration, which is stored on disk and creating a device-mapper setup based on this configuration. Up to now there never existed RAID5 support with dmraid, since there does not exist a RAID5 device mapper target.
2. You seem to have set up a working RAID5 with 10.0 The only RAID5 solution Suse has supported is md raid. This is a kernel layer similar but different to device-mapper. So I am wondering what your actual raid setup is.
For further analysis please attach your Yast logs as described in http://en.opensuse.org/Bugs/YaST
<snip>
1. You are talking about dmraid and RAID5.
Correct It is the device mapper that is not providing the correct information to DMRaid which raid45 used to do and raid456 should do.
2. You seem to have set up a working RAID5 with 10.0 The only RAID5 solution Suse has supported is md raid. This is a kernel layer similar but different to device-mapper. So I am wondering what your actual raid setup is.
For further analysis please attach your Yast logs as described in http://en.opensuse.org/Bugs/YaST
The logs I used to have were destroyed by 10.3a6 which failed to write GRUB properly and forced me to completely reinstall to that machine from scratch. However I am including the article I used when I did the original installation and which I attempted again but which failed when the raid45 module was replaced with the raid456 module. The DMRAID software does support my motherboard at all raid levels up to raid level 5 even though the article did not mention it, the software documentation for dmraid itself did and it did work. From what I can tell, this is simply a device mapping issue in that if the raid456 module that is loaded by SUSE already would advertise itself as supporting raid45 in a way dmraid is and continues to expect, it should work. All functions of dmraid work now EXCEPT activate. It displays the dataset volume information correctly, I just can't activate it. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=280972#c13
Matthias Koenig
https://bugzilla.novell.com/show_bug.cgi?id=280972#c14
Richard Creighton
Of course, dmraid detects the raid 5 signature on the disk, but it
cannot setup a device, since there is no device-mapper target for raid 5 in the kernel. This simply is currently not supported.
Have you read the HOWTO I enclosed as an attachment? It has been a long time since I did this proceedure. I am pretty sure that DMraid is one of the things installable under YAST as I don't remember having to download it or perhaps I had to get a newer version but I know it is in the distribution disk and I installed it from YAST. I am not a systems programmer even though I have been fiddling with Linux since Slackware was in 60 floppies. I taught Linux OS in college, and I have been a customer of SUSE since I bought a copy of 9.3 pro and have been using openSUSE as upgrades ever since. I used to use RedHat prior to discovering SUSE and after exposure to Slackware initially, but in all that time, I never got into the lowest level 'innards' of modifying kernels and creating boot cd/dvd media from scratch with the exception of that one HOWTo I sent you. I agonized over that for almost a week before I got it to work and when it stopped working after upgrading to 10.2, I was crestfallen and I never could get it to work again. I tried in opensuse-users for weeks to get help and finally gave up and installed MDRaid and a small IDE drive so I could boot which is NOT what I previously was able to do under 10.0 using DMRaid. The term raid45 comes from the error message returned from dmraid -ay and the 'help' received from the maillist. My understanding is that RedHat functions with the newest kernel, the same one that SUSE uses. This means to me that a module is available that works with dmraid somewhere and my understanding was that it was raid456, but that may be incorrect, and if it is, I'll be happy to admit confusion and error. I can't stand the thought though that my choice of an OS and distro cannot do what Windoze can do so effortlessly (demonstrated before I bought the MBd) and what I am told (via the RedHat maillist) works on that (but not the distro of choice for me) in the Linux environment. I hate Windoze and everything it stands for and have fought battles like this for years and due to a lot of hard work by people like you, Novell, Red Hat, Debian and a host of others, Linux is at critical-mass in terms of viability as an alternative to Windoze. Manufacturers are starting to support Linux both hardware and software and because of that, consumers are starting to use and demand Linux. But, we are not there yet. Closer, yes, there, not yet. Until we can slide a DVD in and install features the way Redmond can in a way an non-technical person can be successful at most of the time, Linux will not succeed. That would be a shame. You are in a position to make it work. Many motherboard manufacturers are now offering hardware raid support (aka fake-raid) and people want it and shouldn't have to jump through hoops or buy extra drives to make it work and with Windoze, they don't have to and you can make it work with Linux and I believe you can do it with little effort because DMRAID is already written and it worked in 10.0 and should work in 10.3 regardless of whether *it* is the module, or it depends on raid456 or some other module that I am currently unaware of that apparantly existed in 10.0 and was inadvertantly loaded by following the instructions in the HOWto.doc I gave you. PLEASE take a look at that document and use your expertise to see what I blundered through but by accident or design, got to work as a 4 drive, 1TB raid5 DMraid based raid bootable system. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=280972#c15
Matthias Koenig
https://bugzilla.novell.com/show_bug.cgi?id=280972#c16
Richard Creighton
Can you please specify what exactly is missing? We have dmraid and we have a boot script. If this does not work for you please describe the problems.
To what boot script are you referring? I haven't found any script that allows booting from DM raid. I am probably blind and I know I am dumb but I cannot find a module called dm-raid4-5 either, Do you know if SUSE has (experimental or otherwise) a raid 5 device-mapper target module or is that only available from Red Hat to the best of your knowledge? Mr. Koenig, I know it doesn't sound like it, but I really do appreciate your efforts in this matter. Anything to bring Linux up to or exceed Redmond in this area. Linux already does in so many areas. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=280972#c17
Matthias Koenig
https://bugzilla.novell.com/show_bug.cgi?id=280972#c18
--- Comment #18 from Richard Creighton
https://bugzilla.novell.com/show_bug.cgi?id=280972#c19
Jeff Mahoney
https://bugzilla.novell.com/show_bug.cgi?id=280972#c20
Richard Creighton
It has been included already, just not in a new alpha release.
Tue Jul 17 17:51:31 CEST 2007 - bphilips@suse.de
- patches.drivers/ati-sb700-sata-add-all-ids.patch: Add more device IDs for supporting ATI SB700 SATA controller completely (291744).
Can you try the appropriate KOTD kernel from ftp://ftp.suse.com/pub/projects/kernel/kotd/HEAD and verify that it fixes your problem?
I downloaded 2.6.22.1-2007-200726189100-bigsmp.i686 and installed it and verified that it booted that version in sysinfo and then tried dmraid -ay which reported 'device mapper target type 'dmraid45' not in kernel' Do I need to do anything else to enable the patch. In other words, when this system was installed, the raid array would not have been properly detected at installation and it is possible a required module is not loaded that I should and could load manually now for the purposes of this test. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=280972#c21
--- Comment #21 from Jeff Mahoney
https://bugzilla.novell.com/show_bug.cgi?id=280972#c22
--- Comment #22 from Richard Creighton
https://bugzilla.novell.com/show_bug.cgi?id=280972#c23
--- Comment #23 from Stephan Kulow
https://bugzilla.novell.com/show_bug.cgi?id=280972#c24
--- Comment #24 from Steve Kelem
https://bugzilla.novell.com/show_bug.cgi?id=280972#c25
--- Comment #25 from Richard Creighton
https://bugzilla.novell.com/show_bug.cgi?id=280972#c26
--- Comment #26 from Jeff Mahoney
https://bugzilla.novell.com/show_bug.cgi?id=280972#c27
--- Comment #27 from Richard Creighton
Ok, I had a chance to review the patch today. The changes to the core core are minimal, and the only part that looked concerning the last time I looked was just moved to a module_init/exit pair, so that call isn't getting lost. Otherwise, it's all just additional debugging strings and some EXPORT_SYMBOLS.
I'll include the patch, and it'll be part of the next release.
Thank you sir. If you would like, let me know when it is in the kernel of the day and I'll be most happy to test it in the same manner as in the previous request and provide you feedback. I will even procure a new set of drives so I can afford to damage them (datawise) if something goes wrong so I can give it a good test if you wish. What I am not competent to do is low-level programming as my expertise is databases, not C++ and module development though I was writing BBS software in Pascal (QuickBBS) predating the internet but that doesn't help generating driver modules for SuSe :) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=280972
Greg Kroah-Hartman
https://bugzilla.novell.com/show_bug.cgi?id=280972
User jeffm@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=280972#c28
Jeff Mahoney
participants (1)
-
bugzilla_noreply@novell.com