Gianfranco Durin wrote:
Paul Howarth wrote:
Gianfranco Durin wrote:
Paul Howarth wrote:
Gianfranco Durin wrote:
Paul Howarth wrote:
In any case, what is dm-0?
The first device mapper device, which might be your root filesystem
if you're using LVM or RAID.
[skip]
Dear all and Paul,
today I realized a problem with my dm devices. In fact, fdik -l (see
below) says there are no valid partition tables. After the
installation of FC5 (which is only 2 weeks ago) I did not make
anything about this, I think.
I guess this problem is related to the avc message (file_t, labelling
problem, as Paul says).
But is there a way to solve?
Many (^10) thanks for your help
Gianfranco
---------------------------
Disk /dev/sda: 250.0 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sda1 * 1 67 538146 e W95 FAT16 (LBA)
/dev/sda2 68 80 104422+ 83 Linux
/dev/sda3 81 30401 243553432+ 8e Linux LVM
Disk /dev/sdb: 250.0 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdb1 * 1 67 538146 e W95 FAT16 (LBA)
/dev/sdb2 68 30401 243657855 8e Linux LVM
Disk /dev/dm-0: 24.6 GB, 24628953088 bytes
255 heads, 63 sectors/track, 2994 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk /dev/dm-0 doesn't contain a valid partition table
This looks to be one of your LVM physical volumes and it's not
expected to contain a partition table.
We still need to find out which actual file is trying to be accessed
when you get that AVC.
Paul.
Ok fine. I tried this from /
ls --scontext -R |grep :file_t
and I have 3 type of files:
lost+found
These should be lost_found_t
install.log
install.log.syslog
but the last two are old (of the first day, actually).
They are the logs from the installation, when SELinux was probably not
running. You can fix those:
# restorecon -v /root/install.log*
Dos it make sense?
I suspect that these aren't the source of the problem. You may have a
directory labelled file_t that is used as a mountpoint and thus hidden
under another filesystem once the system has booted.
When exactly do you get these AVCs? Just at boot time, or all the time?
Paul.