Description of problem: I have a FakeRAID controller made by JMicron (oh well) where RAID names must be set on boot. I don't have much control over those names and it appears they always end with spaces and funny non-ascii characters (e.g. "jmicron_JRAID " - mind the white spaces.) In /lib/systemd/fedora-storage-init, line 22, RAID set names are parsed with the Shell FOR command: for dmname in $dmraidsets; do where spaces are item delimiters, hence my RAID set cannot be activated. Version-Release number of selected component (if applicable): Fedora 15 How reproducible: Always Steps to Reproduce: 1. Use spaces in names of RAID sets controlled by a dmraid-compatible controller 2. Run Fedora 15 Actual results: the RAID name is not parsed correctly
Created attachment 551105 [details] Potential patch for fedora-storage-init.
Looks reasonable, added to git. Does it work for you?
initscripts-9.35-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/initscripts-9.35-1.fc17
Package initscripts-9.35-1.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing initscripts-9.35-1.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-3459/initscripts-9.35-1.fc17 then log in and leave karma (feedback).
initscripts-9.34.1-1.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/initscripts-9.34.1-1.fc16
initscripts-9.34.2-1.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/initscripts-9.34.2-1.fc16
initscripts-9.34.2-1.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.