LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Fedora (https://www.linuxquestions.org/questions/fedora-35/)
-   -   error messages for disk with Centos (https://www.linuxquestions.org/questions/fedora-35/error-messages-for-disk-with-centos-742504/)

mnauta 07-24-2009 11:31 AM

error messages for disk with Centos
 
Switched form FC9 to CentOS5.2 now I have the following messages

Quote:

Jul 24 06:23:48 sxmail kernel: inode_doinit_with_dentry: context_to_sid(unconfined_u:object_r:file_t:s0) returned 22 for dev=cciss/c0d2p1 ino=5341663
This pretty much fills up the message logs.

I did the install the following way:

1) I have 3 (raid) logical drives in the Proliant server. Data is on 2 3.
2) removed 2 and 3 from raid to protect from accidental write over etc.
3) did fresh Centos install on logical drive 1
4) put 2,3 back in raid
5) updated fstab and mtab

Quote:

more /etc/fstab
/dev/VolGroup00/LogVol00 / ext3 defaults 1 1
LABEL=/boot /boot ext3 defaults 1 2
LABEL=/var/opt /var/opt ext3 defaults 1 2
LABEL=/data /data ext3 defaults 1 2
tmpfs /dev/shm tmpfs defaults 0 0
devpts /dev/pts devpts gid=5,mode=620 0 0
sysfs /sys sysfs defaults 0 0
proc /proc proc defaults 0 0
/dev/VolGroup00/LogVol01 swap swap defaults 0 0
Quote:

more /etc/mtab
/dev/mapper/VolGroup00-LogVol00 / ext3 rw 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
devpts /dev/pts devpts rw,gid=5,mode=620 0 0
/dev/cciss/c0d0p1 /boot ext3 rw 0 0
/dev/cciss/c0d1p1 /var/opt ext3 rw 0 0
/dev/cciss/c0d2p1 /data ext3 rw 0 0
tmpfs /dev/shm tmpfs rw 0 0
none /proc/sys/fs/binfmt_misc binfmt_misc rw 0 0
sunrpc /var/lib/nfs/rpc_pipefs rpc_pipefs rw 0 0
I have no problem with accessing the data but I don't want risk future problems. Any suggestions? Should I worry about this?

Thanks

unSpawn 07-24-2009 04:16 PM

Quote:

Originally Posted by mnauta (Post 3619060)
Switched form FC9 to CentOS5.2

Congrats!


Quote:

Originally Posted by mnauta (Post 3619060)
I have no problem with accessing the data but I don't want risk future problems. Any suggestions? Should I worry about this?

It appears printing an error message when an invalid label is found is addressed here: Selinux Kernel Development (bottom of page), leading to this commit 4ba0a8ad63e12a03ae01c039482967cc496b9174.

JulianTosh 06-05-2010 12:21 PM

Quote:

Originally Posted by mnauta (Post 3619060)
I have no problem with accessing the data but I don't want risk future problems. Any suggestions? Should I worry about this?

Thanks

Sorry for the late reply. I had the same problem and was able to resolve the seemingly benign, but annoying, error messages with:

Code:

fixfiles restore [mount path]


All times are GMT -5. The time now is 12:47 AM.