On Mon, 30 May 2005 15:02:44 CDT, Justin Conover said:
Not so fast on "A" :D
Well, the *current* evidence indicates you're not off the deep end on this specific issue, anyhow.. ;)
fedora.img is part of some Xen stuff I was doing, which initially started this whole thing of mkfs not working.
We probably need to come back sometime and address the issues of mkfs on a file intended for loopback-mount - that's a separate borkage..
--- file_contexts/program/lvm.fc.dist 2005-05-20 14:53:12.000000000 -0400 +++ file_contexts/program/lvm.fc 2005-05-30 13:10:03.000000000 -0400 @@ -12,6 +12,7 @@ /etc/lvm/lock(/.*)? system_u:object_r:lvm_lock_t /var/lock/lvm(/.*)? system_u:object_r:lvm_lock_t /dev/lvm -c system_u:object_r:fixed_disk_device_t +/dev/mapper/.* -c system_u:object_r:fixed_disk_device_t /dev/mapper/control -c system_u:object_r:lvm_control_t /lib/lvm-10/.* -- system_u:object_r:lvm_exec_t /lib/lvm-200/.* -- system_u:object_r:lvm_exec_t
At least on my system, that leaves the /dev/mapper/* entries more sane....
(Justin - the above patch won't fly unless you have policy-sources installe
d.
If you're feeling brave, crazy, and adventurous, make a similar change to /etc/selinux/strict/contexts/files/file_contexts, and then do a 'restorecon -v -R /dev' - make sure to save a backup of file_contexts first
.. ;)
After that, you *should* be able to do a 'mkfs.ext3 /dev/mapper/VolGroup00-LogVol10'
I have no problem doing some of this if someone else chimes in too, it's a new box I'm working on so there is nothing that a new install wont cure for a borked system.
If you can try the file_contexts tweak I mentioned, and verify that you can or can't do a mkfs on /dev/dm-N and /dev/mapper/VolGrouo00-LogVol10, that would help some (and at least give you a known-good workaround while we come up with a proper fix. Even if I've recommended something stupid, a re-install will clear it. ;)
/dev/VolGroup00/LogVol?? will require some other fix which I'd speculate on, but I have to be at a barbeque in 30 mins.. ;)