During normal operation of my system today, I did the following:
cd /usr/src
chown -R root.root *
during the chown, I did ctrl-Z; bg.. while it was still running I did an
ls -l, and it segmentation faulted, and continued segfaulting after the
chown was done.
Here's an strace of the ls (not that it means very much to me)
---open("i686/mmx/libc.so.6", O_RDONLY) = -1 ENOENT (No such file or directory) open("i686/libc.so.6", O_RDONLY) = -1 ENOENT (No such file or directory) open("mmx/libc.so.6", O_RDONLY) = -1 ENOENT (No such file or directory) open("libc.so.6", O_RDONLY) = -1 ENOENT (No such file or directory) open("/usr/local/lib/libc.so.6", O_RDONLY) = -1 ENOENT (No such file or directory) open("/lib/libc.so.6", O_RDONLY) = 3 fstat(3, {st_mode=S_IFREG|0755, st_size=4056688, ...}) = 0 read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\300\216"..., 4096) = 4096 old_mmap(NULL, 921404, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0x40020000 mprotect(0x400fa000, 28476, PROT_NONE) = 0 old_mmap(0x400fa000, 16384, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 3, 0xd9000) = 0x400fa000 old_mmap(0x400fe000, 12092, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x400fe000 close(3) = 0 --- SIGSEGV (Segmentation fault) --- +++ killed by SIGSEGV +++
---
and here's the original ls which I managed to copy back, and the ls that appears to have broken:
-rwxr-xr-x 1 root root 49432 Jun 7 03:56 ls -rwxr-xr-x 1 root root 43024 Jun 7 03:56 ls-broken
These files are on an AccuRAID 8600, if that makes any difference.. though I don't know if this could be an issue with my raid controller.
No, I haven't done an fsck yet as this box is responsible for a lot, and can't take it down at will.
If anyone has any help for me, or if this is a known issue, or if I'm talking out of my ass, let me know. :)
Thanks.
,.;:: : Michael J. Dikkema | Programmer / Systems / Network Admin - Internet Solutions, Inc. | http://www.moot.mb.ca Home: (204) 667-3966 ; mjd@moot.mb.ca Work: (204) 982-1073 ',.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed Jun 07 2000 - 21:00:27 EST