I issued the command (SLES 11) from root [FONT=Courier New]du -sh /*[/FONT] but got some errors.
Its seems that /var/lib/ntp/proc whichs is mounted provokes this error.
Any advise on how to avoid/fix that?
Thank U
Andreas
df -a
…
none 0 0 0 - /var/lib/ntp/proc
…
[FONT=Courier New]$ du -sh /*
9.1M bin
43M boot
9.3G dev
74M etc
3.8M home
146M lib
19M lib64
16K lost+found
4.0K media
756G mnt
6.8G opt
568K oracle_admin
58M oracle_backups
45G oradata
263G oradata_slow
344K oradiag_root
[COLOR="#FF0000"]du: cannot access proc/6475/task/6475/fd/4': No such file or directory du: cannot access proc/6475/task/6475/fdinfo/4’: No such file or directory
du: cannot access proc/6475/fd/4': No such file or directory du: cannot access proc/6475/fdinfo/4’: No such file or directory
[/COLOR]0 proc
268M root
13M sbin
4.0K selinux
88K srv
0 sys
4.4M tmp
3.8G usr
207M var
440K volumes_usage[/FONT]
Is there a reason it is causing you problems? Trying to find the used
disk space of a virtual filesystem (/proc, /sys, /dev, etc.) does not
make a lot of sense. Perhaps add the --exclude option to ‘du’ to
exclude things that, by definition, are not using disk-users.
Good luck.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/
I believe SLES 10 used xntp (a separate project, using the xntpd
process) where we now use ntp (and the ntpd process).
I am not sure exactly why, but I’m guessing with the following:
ntp can be chroot’d and if that’s done then it wants access to things
like /proc. ntp does not create proc, it simply does a “bind mount” so
that it can access stuff like any other process. In order to do that it
basically makes the /proc filesystem available within its chroot jail so
now /proc can be accessed from either location.
Keep in mind that errors about missing /proc/ directories
are possible anytime you go looking in there since those directories are
created and destroyed with every process that is started and stopped.
Looking for things in a “directory” at the time the “directory” goes
away is just an effort in futility. Looking for disk usage in a
“directory” that is merely a window into the running kernel’s memory
(nothing to do with disk) is too.
Good luck.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/