On Fri, Jul 30, 2010 at 01:34, Andrey Vul <andrey....@gmail.com> wrote: > On Thu, Jul 29, 2010 at 08:31, Alex Schuster <wo...@wonkology.org> wrote: >> walt writes: >> >>> On 07/28/2010 01:20 PM, Andrey Vul wrote: >>> > Creating files in /tmp, /etc, /lib32, and /var return ENOENT (touch >>> > /tmp/foo => strerror(ENOENT)). >>> > However, this is done as root and the dirs are marked 755 root:root. >> >> Are all these directories located on the root file system? >> >>> Is the sticky bit set on /tmp? >>> >>> drwxrwxrwt 26 root root 36864 2010-07-29 04:15 tmp/ >>> ^ >> >> Well, it set or not, this would not prevent the creation of files. >> >> I have no idea what's going on here. I'd force a fsck (touch /forcefsck; >> reboot) to make sure it's no file system problem. And what about a live- >> cd, does the problem happen then, too? >> > > fsck -f followed by use of USB-SATA bridge seems to work. However, my > laptop just died, so I can't really test it on the laptop. >
Quoting fsck.jfs : "Incorrect link counts have been detected. Will correct." Apparently, some subtle data corruption was invisible by fsck -p but noticed by fsck -f. A corrupt inode does explain why the directory was somehow 555 in behavior.
