selinux and file system check

cornel panceac cpanceac at
Mon Nov 1 07:10:37 UTC 2010

2010/10/29 Bruno Wolff III <bruno at>

> On Fri, Oct 29, 2010 at 17:35:54 +0300,
>  cornel panceac <cpanceac at> wrote:
> > > not yet, if possible i'll create a bug tomorrow. the behaviour is like
> > this: i boot rescue environment, maybe yum update the system to be
> rescued,
> > then reboot on the then reboot. ""Superblock etc" then immediately "file
> > system relabel is required". this happened several times today on a
> system
> > which was dvd upgraded from f13 to f14 rc1. the relabel doesn't show up
> when
> > i just rebooted the system.
> There might be two problems. The superblock timestamp may have to do with
> timezone settings and how you have your bios clock set. If the rescue
> image and the normal image have different ideas about what the time of
> the bios clock means (say one assumes it is UTC and the other assumes it
> is localtime) I think you could see a symptom like this.
> For the update / selinux relabel issue, if you write to file systems
> with selinux disabled that is going to trigger needing a relabel.

this happens without any writing (that i know about) occuring. just enter
and exit rescue mode, with the partition(s) mounted rw.

> I think
> it is normal for updating stuff while using rescue mode to trigger a
> relabel,
> as if the policy of the rescue image weren't to match that of the installed
> system, when you did an update files could get incorrectly labelled.
-------------- next part --------------
An HTML attachment was scrubbed...

More information about the test mailing list