[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: cannot access `./proc/6535/task/6535/fd/4



On 2011-12-25 00:42:25 +0800, lina wrote:
> du: cannot access `./proc/6535/task/6535/fd/4': No such file or directory
> du: cannot access `./proc/6535/task/6535/fdinfo/4': No such file or directory
> du: cannot access `./proc/6535/fd/4': No such file or directory
> du: cannot access `./proc/6535/fdinfo/4': No such file or directory
> End
> 
> Just want to know is it dangerous?

I don't think so. I suppose that the fd was open when you started to
run "du" but was closed before "du" read the files. Said otherwise,
"du" is not atomic: if files are removed while it is being run, you
can get errors. This is true for every similar utilities.

> Today, I checked the df -h
> it showed used 100%, actually there were still 7M left.

If this hasn't changed, some disk space is reserved for root (so that
the system can still run if you get out of disk space). This may be
the reason. Or it's just the rounding to an integer: it's almost 100%.

> so I remove one old kernel, so now is
> /dev/sda5       666M  547M   86M  87% /
> 
> I remember once Camaleón suggested to check the
> 
> cd /
> 
> du -sh | grep [0-9]M | sort -nr
> 
> find out the largest ones,

I don't think that's correct: the -s du option will just give you the
total.

> but when I used, I met above problem,
> 
> Something wrong?
> 
> and it's bad no warning about the / nearly reach full.

You can install the monit package, and configure it to give you a
warning when some filesystem starts to become full (I suppose that
"space usage", but I'm not sure).

-- 
Vincent Lefèvre <vincent@vinc17.net> - Web: <http://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / Arénaire project (LIP, ENS-Lyon)


Reply to: