https://bugzilla.novell.com/show_bug.cgi?id=851355
https://bugzilla.novell.com/show_bug.cgi?id=851355#c1
Remco de Vreugd changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rdevreugd@novell.com
--- Comment #1 from Remco de Vreugd 2014-04-07 16:26:38 UTC ---
The problem is not limited to just LVM. Anything that involves the device
mapper (and its need to create device nodes for new mappings) runs into the
"Read-only file system" error.
Here's how to reproduce it with LUKS.
1. Perform an installation of openSUSE 13.1 towards /dev/sda with an
unencrypted boot partition (sda1) and a LUKS-encrypted root partition (sda2).
2. Boot rescue.
3. Login as root.
4. Attempt to unlock the encrypted partition (i.e. set up a decrypting device
mapping) using "cryptsetup luksOpen /dev/sda2 root".
This produces the following error:
/dev/mapper/temporary-cryptsetup-1508: mknod for temporary-cryptsetup-1508
failed: Read-only file system
Failed to open temporary keystore device.
(with 1508 a varying nummer, presumably a process ID)
Remounting /dev in read-write mode, using "mount -o rw,remount /dev" does not
help. The remount of the devtmpfs succeeds, but the /dev/mapper branch remains
read-only. "touch /dev/foo" works fine, "touch /dev/mapper/foo" runs into a
"Read-only file system" error.
A workaround would be appreciated. As it is, the rescue installation of
openSUSE 13.1 Final is basically useless to deployments that use LVM, full disk
encryption, or both.
--
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.
