/sourceware/cvs-tmp FULL!!

/sourceware/cvs-tmp FULL!!

[Andrew Cagney]

[cagney@sourceware cvs-tmp]$ df -k /sourceware/cvs-tmp
Filesystem           1k-blocks      Used Available Use% Mounted on
/dev/sdd2               303243    287585         0 100%
/sourceware/cvs-tmp

	Andrew

Re: /sourceware/cvs-tmp FULL!!

[Chris Faylor]

On Fri, Sep 08, 2000 at 06:25:08PM +1100, Andrew Cagney wrote:
>[cagney@sourceware cvs-tmp]$ df -k /sourceware/cvs-tmp
>Filesystem           1k-blocks      Used Available Use% Mounted on
>/dev/sdd2               303243    287585         0 100%
>/sourceware/cvs-tmp

Looks like somebody cleaned it up?

cgf

Re: /sourceware/cvs-tmp FULL!!

[Jeffrey A Law]

  In message < 20000908124210.B13006@cygnus.com >you write:
  > On Fri, Sep 08, 2000 at 06:25:08PM +1100, Andrew Cagney wrote:
  > >[cagney@sourceware cvs-tmp]$ df -k /sourceware/cvs-tmp
  > >Filesystem           1k-blocks      Used Available Use% Mounted on
  > >/dev/sdd2               303243    287585         0 100%
  > >/sourceware/cvs-tmp
  > 
  > Looks like somebody cleaned it up?
It was clean by the time I looked at it this morning.

jeff

Re: /sourceware/cvs-tmp FULL!!

[Chris Faylor]

On Fri, Sep 08, 2000 at 10:47:54AM -0600, Jeffrey A Law wrote:
>
>  In message < 20000908124210.B13006@cygnus.com >you write:
>  > On Fri, Sep 08, 2000 at 06:25:08PM +1100, Andrew Cagney wrote:
>  > >[cagney@sourceware cvs-tmp]$ df -k /sourceware/cvs-tmp
>  > >Filesystem           1k-blocks      Used Available Use% Mounted on
>  > >/dev/sdd2               303243    287585         0 100%
>  > >/sourceware/cvs-tmp
>  > 
>  > Looks like somebody cleaned it up?
>It was clean by the time I looked at it this morning.

Should we add a "delete all files in cvs-tmp older than n days" cleanup
to cron?  Or is there something doing that already?

cgf

Re: /sourceware/cvs-tmp FULL!!

[Tom Tromey]

Chris> Should we add a "delete all files in cvs-tmp older than n days"
Chris> cleanup to cron?  Or is there something doing that already?

There is almost something doing it already:

15 3 * * * cd /sourceware/cvs-tmp; /usr/bin/find . -xdev -name '#*' -mtime +2 -type f -exec rm -f {} \;

This looks like it is built to clean up after log_accum only, though.
It won't remove old cvs-serv* stuff.
Maybe extending it to do that would be good.  What is the danger of
doing it?

Tom

Re: /sourceware/cvs-tmp FULL!!

[Jeffrey A Law]

  In message < 20000908124856.D13006@cygnus.com >you write:
  > On Fri, Sep 08, 2000 at 10:47:54AM -0600, Jeffrey A Law wrote:
  > >
  > >  In message < 20000908124210.B13006@cygnus.com >you write:
  > >  > On Fri, Sep 08, 2000 at 06:25:08PM +1100, Andrew Cagney wrote:
  > >  > >[cagney@sourceware cvs-tmp]$ df -k /sourceware/cvs-tmp
  > >  > >Filesystem           1k-blocks      Used Available Use% Mounted on
  > >  > >/dev/sdd2               303243    287585         0 100%
  > >  > >/sourceware/cvs-tmp
  > >  > 
  > >  > Looks like somebody cleaned it up?
  > >It was clean by the time I looked at it this morning.
  > 
  > Should we add a "delete all files in cvs-tmp older than n days" cleanup
  > to cron?  Or is there something doing that already?
I'm not aware of anything that's already doing this.  If we don't have
such a cleaner, we probably should add one.
jeff

Re: /sourceware/cvs-tmp FULL!!

[Jeffrey A Law]

  In message < 87lmx2yfgb.fsf@creche.cygnus.com >you write:
  > Chris> Should we add a "delete all files in cvs-tmp older than n days"
  > Chris> cleanup to cron?  Or is there something doing that already?
  > 
  > There is almost something doing it already:
  > 
  > 15 3 * * * cd /sourceware/cvs-tmp; /usr/bin/find . -xdev -name '#*' -mtime 
  > +2 -type f -exec rm -f {} \;
  > 
  > This looks like it is built to clean up after log_accum only, though.
  > It won't remove old cvs-serv* stuff.
  > Maybe extending it to do that would be good.  What is the danger of
  > doing it?
At the worst, the client side would abort if the cvs-serv files went away
from under it.  Consider if someone accidentally stopped a cvs update, then
realized it a few days later and restarted it (been there, done that :-)

I won't corrupt the repo on either end as far as I know.
jeff

Re: /sourceware/cvs-tmp FULL!!

[Andrew Cagney]

Andrew Cagney wrote:
> 
> [cagney@sourceware cvs-tmp]$ df -k /sourceware/cvs-tmp
> Filesystem           1k-blocks      Used Available Use% Mounted on
> /dev/sdd2               303243    287585         0 100%
> /sourceware/cvs-tmp

Given everyone is denying responsibility for fixing the problem I guess
it fixed itsself :-)
Some one must have been doing as jason suggested (full update) and when
that fell over it freed the space up again.

Thanks everyone for checking.

Tom Tromey wrote:
> 
> Chris> Should we add a "delete all files in cvs-tmp older than n days"
> Chris> cleanup to cron?  Or is there something doing that already?
> 
> There is almost something doing it already:
> 
> 15 3 * * * cd /sourceware/cvs-tmp; /usr/bin/find . -xdev -name '#*' -mtime +2 -type f -exec rm -f {} \;
> 
> This looks like it is built to clean up after log_accum only, though.
> It won't remove old cvs-serv* stuff.
> Maybe extending it to do that would be good.  What is the danger of
> doing it?

Depends on who it is being done as.  Isn't there a rule of thumb that
you should never run `find|xargs rm` as root?  I know you at least need
to be very careful.

	Andrew

Re: /sourceware/cvs-tmp FULL!!

[Phil Edwards]

On Sun, Sep 10, 2000 at 10:00:18PM +1100, Andrew Cagney wrote:
> 
> Depends on who it is being done as.  Isn't there a rule of thumb that
> you should never run `find|xargs rm` as root?  I know you at least need
> to be very careful.

"Works fer meeeee!"

A suitably paranoid script will suffice.  On my systems, for example,
the find(1) is very careful to ignore certain filenames, anything owned
by certain users, etc.  After building a list, occasionally some more
checking is done on the list elements, and /then/ the list gets fed to rm(1).


Phil

Re: /sourceware/cvs-tmp FULL!!

[Tom Tromey]

Chris> Should we add a "delete all files in cvs-tmp older than n days"
Chris> cleanup to cron?  Or is there something doing that already?

There is almost something doing it already:

15 3 * * * cd /sourceware/cvs-tmp; /usr/bin/find . -xdev -name '#*' -mtime +2 -type f -exec rm -f {} \;

This looks like it is built to clean up after log_accum only, though.
It won't remove old cvs-serv* stuff.
Maybe extending it to do that would be good.  What is the danger of
doing it?

Tom

Re: /sourceware/cvs-tmp FULL!!

[Chris Faylor]

On Fri, Sep 08, 2000 at 06:25:08PM +1100, Andrew Cagney wrote:
>[cagney@sourceware cvs-tmp]$ df -k /sourceware/cvs-tmp
>Filesystem           1k-blocks      Used Available Use% Mounted on
>/dev/sdd2               303243    287585         0 100%
>/sourceware/cvs-tmp

Looks like somebody cleaned it up?

cgf

Re: /sourceware/cvs-tmp FULL!!

[Phil Edwards]

On Sun, Sep 10, 2000 at 10:00:18PM +1100, Andrew Cagney wrote:
> 
> Depends on who it is being done as.  Isn't there a rule of thumb that
> you should never run `find|xargs rm` as root?  I know you at least need
> to be very careful.

"Works fer meeeee!"

A suitably paranoid script will suffice.  On my systems, for example,
the find(1) is very careful to ignore certain filenames, anything owned
by certain users, etc.  After building a list, occasionally some more
checking is done on the list elements, and /then/ the list gets fed to rm(1).


Phil

Re: /sourceware/cvs-tmp FULL!!

[Jeffrey A Law]

  In message < 20000908124856.D13006@cygnus.com >you write:
  > On Fri, Sep 08, 2000 at 10:47:54AM -0600, Jeffrey A Law wrote:
  > >
  > >  In message < 20000908124210.B13006@cygnus.com >you write:
  > >  > On Fri, Sep 08, 2000 at 06:25:08PM +1100, Andrew Cagney wrote:
  > >  > >[cagney@sourceware cvs-tmp]$ df -k /sourceware/cvs-tmp
  > >  > >Filesystem           1k-blocks      Used Available Use% Mounted on
  > >  > >/dev/sdd2               303243    287585         0 100%
  > >  > >/sourceware/cvs-tmp
  > >  > 
  > >  > Looks like somebody cleaned it up?
  > >It was clean by the time I looked at it this morning.
  > 
  > Should we add a "delete all files in cvs-tmp older than n days" cleanup
  > to cron?  Or is there something doing that already?
I'm not aware of anything that's already doing this.  If we don't have
such a cleaner, we probably should add one.
jeff

Re: /sourceware/cvs-tmp FULL!!

[Andrew Cagney]

Andrew Cagney wrote:
> 
> [cagney@sourceware cvs-tmp]$ df -k /sourceware/cvs-tmp
> Filesystem           1k-blocks      Used Available Use% Mounted on
> /dev/sdd2               303243    287585         0 100%
> /sourceware/cvs-tmp

Given everyone is denying responsibility for fixing the problem I guess
it fixed itsself :-)
Some one must have been doing as jason suggested (full update) and when
that fell over it freed the space up again.

Thanks everyone for checking.

Tom Tromey wrote:
> 
> Chris> Should we add a "delete all files in cvs-tmp older than n days"
> Chris> cleanup to cron?  Or is there something doing that already?
> 
> There is almost something doing it already:
> 
> 15 3 * * * cd /sourceware/cvs-tmp; /usr/bin/find . -xdev -name '#*' -mtime +2 -type f -exec rm -f {} \;
> 
> This looks like it is built to clean up after log_accum only, though.
> It won't remove old cvs-serv* stuff.
> Maybe extending it to do that would be good.  What is the danger of
> doing it?

Depends on who it is being done as.  Isn't there a rule of thumb that
you should never run `find|xargs rm` as root?  I know you at least need
to be very careful.

	Andrew

Re: /sourceware/cvs-tmp FULL!!

[Chris Faylor]

On Fri, Sep 08, 2000 at 10:47:54AM -0600, Jeffrey A Law wrote:
>
>  In message < 20000908124210.B13006@cygnus.com >you write:
>  > On Fri, Sep 08, 2000 at 06:25:08PM +1100, Andrew Cagney wrote:
>  > >[cagney@sourceware cvs-tmp]$ df -k /sourceware/cvs-tmp
>  > >Filesystem           1k-blocks      Used Available Use% Mounted on
>  > >/dev/sdd2               303243    287585         0 100%
>  > >/sourceware/cvs-tmp
>  > 
>  > Looks like somebody cleaned it up?
>It was clean by the time I looked at it this morning.

Should we add a "delete all files in cvs-tmp older than n days" cleanup
to cron?  Or is there something doing that already?

cgf

Re: /sourceware/cvs-tmp FULL!!

[Jeffrey A Law]

  In message < 20000908124210.B13006@cygnus.com >you write:
  > On Fri, Sep 08, 2000 at 06:25:08PM +1100, Andrew Cagney wrote:
  > >[cagney@sourceware cvs-tmp]$ df -k /sourceware/cvs-tmp
  > >Filesystem           1k-blocks      Used Available Use% Mounted on
  > >/dev/sdd2               303243    287585         0 100%
  > >/sourceware/cvs-tmp
  > 
  > Looks like somebody cleaned it up?
It was clean by the time I looked at it this morning.

jeff

Re: /sourceware/cvs-tmp FULL!!

[Jeffrey A Law]

  In message < 87lmx2yfgb.fsf@creche.cygnus.com >you write:
  > Chris> Should we add a "delete all files in cvs-tmp older than n days"
  > Chris> cleanup to cron?  Or is there something doing that already?
  > 
  > There is almost something doing it already:
  > 
  > 15 3 * * * cd /sourceware/cvs-tmp; /usr/bin/find . -xdev -name '#*' -mtime 
  > +2 -type f -exec rm -f {} \;
  > 
  > This looks like it is built to clean up after log_accum only, though.
  > It won't remove old cvs-serv* stuff.
  > Maybe extending it to do that would be good.  What is the danger of
  > doing it?
At the worst, the client side would abort if the cvs-serv files went away
from under it.  Consider if someone accidentally stopped a cvs update, then
realized it a few days later and restarted it (been there, done that :-)

I won't corrupt the repo on either end as far as I know.
jeff

/sourceware/cvs-tmp FULL!!

[Andrew Cagney]

[cagney@sourceware cvs-tmp]$ df -k /sourceware/cvs-tmp
Filesystem           1k-blocks      Used Available Use% Mounted on
/dev/sdd2               303243    287585         0 100%
/sourceware/cvs-tmp

	Andrew