| Summary: | various permission denied on files as root (may be emerge related, or reiserfs related) | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Patrick Hanevold <ph> |
| Component: | [OLD] Core system | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | critical | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
When I try to update with emerge as root, it complains about file permission errors. The files cannot be deletet manually to fix the problem as permissions do not allow to chmod, ls, chown, or any action at all. Moving the parent folder to /tmp is possible. Reproducible: Always Steps to Reproduce: Can not be reproduced on a fresh install. When trying to emerge after moving troubled packages out of the way. A file in /etc allso got this same symptom. It may allready have had the symptom, but it was not repported before, so it seems logical it got garbled during the emerge. lstat64("/etc/init.d/gpm", {st_mode=S_IFREG|0755, st_size=958, ...}) = 0 lstat64("/etc/init.d/xdm", {st_mode=S_IFREG|0755, st_size=2988, ...}) = 0 lstat64("/etc/init.d/xfs", {st_mode=S_IFREG|0755, st_size=7264, ...}) = 0 lstat64("/etc/init.d/famd", {st_mode=S_IFREG|0755, st_size=512, ...}) = 0 lstat64("/etc/init.d/lisa", {st_mode=S_IFREG|0755, st_size=546, ...}) = 0 lstat64("/etc/init.d/nscd", {st_mode=S_IFREG|0755, st_size=856, ...}) = 0 lstat64("/etc/init.d/slpd", 0x805e38c) = -1 EACCES (Permission denied) As seen above in some of the output from a strace of "ls -l /etc" slpd gives EACCES errors from unknown origins. It is not possible to see the file permissions on slpd itself, but /etc has all required access flags for root to access. uname -a outout: Mon Sep 20 19:04:31 CEST 2004 i686 Intel(R) Pentium(R) 4 CPU 2.80GHz GenuineIntel GNU/Linux The running kernel is installed by genkernel recently. Allso I recently performed the steps adviced by emerge to switch to the hardened x86 profile. It may not be relevant, but worth mentioning anyways. It is not a physical error with the disk or any other hardware. The system is otherwize operational at the moment.