Re: Something eating diskspace in Testing

2018-02-17 Thread Roberto C . Sánchez
On Fri, Feb 16, 2018 at 10:14:25PM -0800, David Christensen wrote:
> 
> Unix has a feature whereby a program can open a file, save the file handle,
> and then unlink the file.  Once unlinked, the file is inaccessible to most
> (all?) other programs, but the originating program can still access the file
> contents via the saved file handle.  When the program closes the file
> handle, the file contents on disk are freed. See unlink(2).
> 
> 
Incidentally, That is one of my favorite sysadmin job interview
scenarios. Hand the candidate a system where a process is doing just as
you describe and see if he/she can identify that as the cause. It as an
excellent way to assess the depth of someone's knowledge of Unix-like
systems.

Regards,

-Roberto

-- 
Roberto C. Sánchez



Re: Something eating diskspace in Testing

2018-02-17 Thread rhkramer
On Saturday, February 17, 2018 12:51:54 AM Johan DS wrote:
> hi
> I have testing installed with a separete /Home partition.
> 
> My root partition /dev/sda2 is slowly filling up. In a few hours it goes
> from 7GB to 15GB.
> Until there is no more space. I used ncdu. And also did
> ls and finds for big files and/or directories . But I can not find a file
> or directory that eats up space.
> 
> Any body a clou?

I used to have a problem like that because x used to spew thousands of errors 
into the .xsession-errors files.  Iirc, the problem was with the user version 
rather than root (on Wheezy / kde3 --or, actually, I guess it was on Debian 
5.n, which I guess was Lenny??).

Anyway, I worked around the problem by adding 2 lines to root's crontab (and I 
carried those over when I moved to Wheezy).  I don't see nearly as many errors 
there anymore, but ... 

  *  *  *   *   * echo "Cleared on $(date) by $USER cron" > 
/home//.xsession-errors
  *  *  *   *   * echo "Cleared on $(date) by $USER cron" > 
/root/.xsession-errors

Another thing I did was put /home on a separate small partition (currently 1 
GB, iirc), and I keep all of my "real user data" (i.e., documents, pictures, 
videos, programs that I write,  ...) under a separate top level directory, 
/.



Re: Something eating diskspace in Testing

2018-02-16 Thread David Christensen

On 02/16/18 21:51, Johan DS wrote:

hi
I have testing installed with a separete /Home partition.

My root partition /dev/sda2 is slowly filling up. In a few hours it goes
from 7GB to 15GB.
Until there is no more space. I used ncdu. And also did
ls and finds for big files and/or directories . But I can not find a file
or directory that eats up space.

Any body a clou?


Unix has a feature whereby a program can open a file, save the file 
handle, and then unlink the file.  Once unlinked, the file is 
inaccessible to most (all?) other programs, but the originating program 
can still access the file contents via the saved file handle.  When the 
program closes the file handle, the file contents on disk are freed. 
See unlink(2).



So, you could have a process that uses the above trick to create and 
write to a file (likely a temporary file), but never stops writing.



In any case, I would try lsof(8).


David



Something eating diskspace in Testing

2018-02-16 Thread Johan DS
hi
I have testing installed with a separete /Home partition.

My root partition /dev/sda2 is slowly filling up. In a few hours it goes
from 7GB to 15GB.
Until there is no more space. I used ncdu. And also did
ls and finds for big files and/or directories . But I can not find a file
or directory that eats up space.

Any body a clou?