On Wed, 2014-06-25 at 20:55 +0200, B wrote:
[...]
And if your $HOME is really 100% full, that means you can't
succeed making: touch ZZZ.ZZZ in it (as the right user).
Is that true? Using touch on a non-existent filename creates a file of
zero length, which I would assume for a lot of file
On Wed, 2014-06-25 at 12:42 -0600, ChadDavis wrote:
I have a single partition mounted at '/'. When I run the disk usage
utility, it shows That I have 66 GB remaining. Which is correct. But when
I scan home it shows my home folder as 100% full.
Why would my home folder be full, when my
I have a single partition mounted at '/'. When I run the disk usage
utility, it shows That I have 66 GB remaining. Which is correct. But when
I scan home it shows my home folder as 100% full.
Why would my home folder be full, when my there is just one huge partition
and it has plenty of empty
On Wed, 25 Jun 2014 12:42:53 -0600
ChadDavis chadmichaelda...@gmail.com wrote:
I have a single partition mounted at '/'. When I run the disk
usage utility, it shows That I have 66 GB remaining. Which is
correct. But when I scan home it shows my home folder as 100%
full.
What do you call
Hi Chris,
Maybe lsof can help you. It gives a list of open files. There is a debian
package for lsof. Unfortunately it is kernel dependent. The slink version
only works for 2.0.35.
Greetings,
Christian van Enckevort
Christian van Enckevort wrote:
Maybe lsof can help you. It gives a list of open files. There is a debian
package for lsof. Unfortunately it is kernel dependent. The slink version
only works for 2.0.35.
That is not true. The slink version for example also works on a 2.0.36
kernel. However, you
Hi all,
I was wondering if there's a utility like top to see who is
accessing the drives. The machine has been going nuts with disk
access for no obvious reason, and we don't know if it's a program
running in the background, one of our shell users, or something else.
Thanks,
Chris
7 matches
Mail list logo
