https://bugzilla.novell.com/show_bug.cgi?id=648878 https://bugzilla.novell.com/show_bug.cgi?id=648878#c0 Summary: Devices whos names contain spaces (eg. raid arrays) cause yast to generate an invalid fstab entry Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: x86-64 OS/Version: openSUSE 11.2 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: richmoore44@gmail.com QAContact: jsrain@novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US) AppleWebKit/534.7 (KHTML, like Gecko) Chrome/7.0.517.41 Safari/534.7 I have a raid array named 'second raid'. Yast correctly identified it and was able to display it, format it etc. however the mount point it created had the space in the name unquoted in the fstab file. This obviously rendered the fstab entry corrupt which prevented the device from being mounted. Digging around, it appears spaces should be quoted as octal in fstab, so the entry should have been second\040raid for the mounting to work. It might also be worth displaying a warning when detecting an array whos name contains spaces (or other special characters) that there may be interoperability problems. (eg. what i had put a / in the name of the array). Reproducible: Always Steps to Reproduce: 1. Create a named hardware raid array with a name containing a space 2. Add a mount point from the array using yast 3. Reboot and watch for the warning that the fstab entry is broken. Actual Results: Mounting the bad fstab entry fails Expected Results: Mount the partition. -- 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.