First I want to say that the contents and of this machine is not important,
but I assume you are interested in any problems. I do not know if this
is XFS-related, but
$ mount
/dev/hda1 on / type xfs (rw)
proc on /proc type proc (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
it's the only file system I use.
I noticed the following process;
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
root 6172 0.0 0.1 1464 496 ? D May30 0:04 find / (..)
and I found out that this problem isn't new, this had happened to every
updatedb-job started by crond, and it happened to my `find /' process too.
Further checking showed;
# ls -l /proc/6172/cwd
cwd -> /usr/share/texmf/fonts/tfm/cg/
# ls -l /proc/6172/fd/
...
4 -> /usr/share/texmf/fonts/tfm/cg/times/
# strace ls -l /usr/share/texmf/fonts/tfm/cg/times/
open("/usr/share/texmf/fonts/tfm/cg/times/",
O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY) = 3
fstat64(3, {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
fcntl64(3, F_SETFD, FD_CLOEXEC) = 0
brk(0x8059000) = 0x8059000
getdents64(0x3, 0x8056848, 0x1000, 0
^-- end of output
So - this happens to every process doing that there, I haven't found anything
similar elsewhere so far. These processes does not respond to kill -9, and
I assumed you wanted to know about this before I'll reboot and see if the
problem persists.
System info:
$ uname -a
Linux jollyjumper 2.4.18-xfs-1.1 #6 Fri May 24 23:33:01 CEST 2002 i686 unknown
$ cat /var/log/dmesg | important-stuff(?)
Linux version 2.4.18-xfs-1.1 (root@jollyjumper) (gcc version 3.0.4) #6 Fri May
24 23:33:01 CEST 2002
CPU: AMD Duron(tm) Processor stepping 01
SGI XFS with ACLs, quota, no debug enabled
^- ouch
XFS mounting filesystem ide0(3,1)
XFS: WARNING: recovery required on readonly filesystem.
^- hmm[0]
XFS: write access will be enabled during mount.
Starting XFS recovery on filesystem: ide0(3,1) (dev: 3/1)
Ending XFS recovery on filesystem: ide0(3,1) (dev: 3/1)
[0] Hmm;
$ uptime
16:56:16 up 7 days, 15 min, 3 users, load average: 10.28, 10.10, 9.65
$ last | magickfilter
reboot system boot 2.4.18-xfs-1.1 Sun May 26 16:40 (7+00:14)
I cannot remember why I rebooted, but I think it shut down as normal
but not completely, it froze for more than 30 sec without making a sound
so I `pulled the plug'. At least this[1] shows the problem didn't start
directly after the unclean shutdown.
[1]
$ ps aux |grep D
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
[..not State D..]
root 6172 0.0 0.1 1464 496 ? D May30 0:04 find / -xdev (
-false ) -prune -o ( -type f -perm +06000 -o ( ( -type b -o -type c ) -a -not (
-false ) ) ) -printf %8i %5m %3n %-10u %-10g %9s %t %h/%f?n
[...]
Cron probably started several similar find-processes before without any
problems.
$ dpkg -l xfsprogs
ii xfsprogs 2.0.6-2 Utilities for managing the XFS filesystem
Full logs, config files etc. are available at request - I can put them out on
the web if you want, I'm available on IRC as Plante, #xfs@OPN at least today,
sunday, and monday.
--
best regards
Carl Lunde
|