It seems to me to be a problem if single user jobs are dumping 500+ megs in
/home and then just leaving them there.
Do job outputs "hang around" in the particular /home output directories
until they are retrieved by a user?
Does this not suggest that there is going to be an aweful lot of NFS traffic
between wherever /home is commonly mounted and the particular WNs? Does
this also not mean that there will be double NFS traffic from a local SE to
the /home machine and then on to the WN?
Ian.
--
Ian Stokes-Rees [log in to unmask]
Particle Physics, Oxford http://www-pnp.physics.ox.ac.uk/~stokes/
> -----Original Message-----
> From: Steve Traylen [mailto:[log in to unmask]]
> Sent: 05 March 2003 21:29
> To: [log in to unmask]
> Subject: Re: /home
>
>
> Ian,
>
> I run a simple
>
> find /home -mindepth 1 -depth -atime +25 \
> ! -name .bashrc ! -name .bash_profile -exec rm {} \;
>
> as a daily cron but that wont help in this case.
>
> The 25 days needs last from when the job arrived to when a job
> finishes.
>
> LHCb jobs are causing these problems elsewhere.
>
> As for better solutions there is a hack to make the working directory
> /tmp on the WN which I keep meaning to implement but have not
> got arround to it yet. There is also zambo but that does not
> exist yet.
>
> Steve
>
>
> On Wed, 5 Mar 2003, Stephen Burke wrote:
>
> > On Wed, 5 Mar 2003, Ian Stokes-Rees wrote:
> > > We had 10 gigs allocated to /home space on our CE. In
> the past two weeks
> > > these have been filled up:
> >
> > What are they filled up with? Real files, or things left over by the
> > job submission? With the latter I know there have been problems with
> > running out of inodes, but AFAIR it was mostly directories and not
> > that much in space terms. If lhcb jobs are leaving files in the home
> > directories it's a mistake, any permanent files should go to an SE.
> >
> > Stephen
> >
>
> --
> Steve Traylen
> [log in to unmask]
> http://www.gridpp.ac.uk/
>
|