You are not logged in. Login Now
 0-24   25-49   50-65        
 
Author Message
valerie
Help! The disks are going to fill up! Mark Unseen   Apr 28 03:31 UTC 2003

This item has been erased.

65 responses total.
valerie
response 1 of 65: Mark Unseen   Apr 28 03:35 UTC 2003

This response has been erased.

valerie
response 2 of 65: Mark Unseen   Apr 28 03:36 UTC 2003

This response has been erased.

carson
response 3 of 65: Mark Unseen   Apr 28 03:56 UTC 2003

(my $.02:  inbound FTP probably isn't as useful as it once was, and likely
only serves to bring things onto Grex that won't necessarily make their
way off.  outbound FTP, however, presumably remains useful for moving
archives, mail, etc. off of Grex.  is it possible to affect one process
without affecting the other?)

(other thought:  if disk quotas will be available on the next Grex, would
it make sense to suspend FTP until that time, instead of permanently?)

(BTW, what's involved in manual disk policing?  I'm curious about
volunteering, if only for the interim.)
cross
response 4 of 65: Mark Unseen   Apr 28 04:13 UTC 2003

I once posted quite a few suggestions about this, but they almost all
got shot down.  Among them were moving mail delivery to home directories,
turning off FTP and access to lynx for new users for 24 hours, or otherwise
limiting the size of files that could be brought in, and using quotas for
new users for a short time until they proved they wanted to stick around.
I still think all of these are reasonable, and not difficult to implement.
robh
response 5 of 65: Mark Unseen   Apr 28 05:35 UTC 2003

I do use ftp a lot to handle my files, but I could certainly live
with outbound-only ftp, for what that's worth.
carson
response 6 of 65: Mark Unseen   Apr 28 05:37 UTC 2003

(my understanding was & is that 1) moving mail to home directories
wouldn't actually alleviate disk usage; rather, it would aggravate the
existing problem [i.e., home directory overuse], 2) creating a
"probationary" period for FTP & lynx would require software not present
on the current Grex, 3) limiting the size of files transferable via FTP
is not possible under Grex's current FTP set-up, and would require
creating some sort of hack, and 4) see 2).  it's certainly possible that
I'm wrong on each and every one of those points because I'm Not A
Techie [tm], and I hope I'm wrong on *at least* one because nearly
anything would be an improvement over the present situation as
described.)
krj
response 7 of 65: Mark Unseen   Apr 28 05:43 UTC 2003

I vote for turning off inbound FTP as an interim measure until the 
new machine is installed.
mary
response 8 of 65: Mark Unseen   Apr 28 10:31 UTC 2003

Has Scott said he'd not be staying on staff or wouldn't be 
logging in once he moves?  I assume this job doesn't need
physical access to the computer.

mary
response 9 of 65: Mark Unseen   Apr 28 10:53 UTC 2003

But ultimately it's probably time for some new staff
members to pick up some of the slack despite our
moving to a new machine.

I can think of one person immediately who would be 
a good fit.  I'm sure there must be others.
dah
response 10 of 65: Mark Unseen   Apr 28 11:22 UTC 2003

HEy, I'm trustworthy, and will gladly spend hours aiding a volunteer
organisation, pick me.
cross
response 11 of 65: Mark Unseen   Apr 28 12:14 UTC 2003

Regarding #6; It's not terribly difficult to do either #4 or #3; one
can play around with scripts that `wrap' the current FTP and web
clients, and/or quotas.  Could someone work around that?  Perhaps;
but it stops most of the script kiddies, which gives the biggest
bang for the buck.

As for moving email to home directories.  The benefit is that you
(1) eliminate a partition, and (2) aren't left with a situation
where you have $n$ hundreds of megabytes of free space in the mail
partition, but nothing available on the home directory disks.  It
seems pretty silly to have 700+ megs free in /var/spool/mail if
home is filling up.

But speaking of this....  None of the home directory partitions are
more than 45% full.  It hardly seems like we're running out of disk
space, the sky is falling, we have to fix something RIGHT NOW.
scott
response 12 of 65: Mark Unseen   Apr 28 12:33 UTC 2003

I'm not leaving just yet, and I probably won't ever be totally gone.  But with
a couple months I'll be leaving Ann Arbor, hopefully to find employment which
will keep me much too busy to keep smacking vandals here on Grex.
janc
response 13 of 65: Mark Unseen   Apr 28 13:38 UTC 2003

My recommendation would be to do the same thing on the Sun that we are
planning to do on the new system:  turn on the operating system's hard
disk quotas.

There is a rumor that there are bugs in the quota system in SunOS. 
However, I did some extensive web searching a few years back and
couldn't find a single reference to this.  Lots of people using it, but
none reporting problems.  I suspect these bugs were in some older
version of SunOS and are now long gone.  If there are bugs, likely
they'd be mild enough to be able to live with until we get to the new
system.

Disk quotas would be somewhat negotiable.  If you have some plausible
reason to be using more disk space than the normal quota, contact staff
and we'll increase it.   I would expect us to be fairly liberal with
this, without eggdroppings, we actually do have a *lot* of disk space.

I might suggest that when we do this, we set the hard quotas to
something like double our current limit.  We actually have lots of
disk - there are several 4Meg drives connected to Grex that just need to
be turned on and formatted to make new user partitions.  This wouldn't
help as long as we have no quotas, because the eggdroppers will eat up
any amount of new disk in no time at all, but once we have hard quotas,
it would allow us to set those quotas a bit higher.
aruba
response 14 of 65: Mark Unseen   Apr 28 14:20 UTC 2003

We have lots of spare disk in the Pumpkin.  We could put some of it online.
gull
response 15 of 65: Mark Unseen   Apr 28 16:17 UTC 2003

I think the ultimate solution is going to be quotas.  If we need to turn
off FTP in the interim I'd have no problem with that.  FTP is pretty
much an obsolete protocol anyway.  These days I almost always use scp
instead.
tod
response 16 of 65: Mark Unseen   Apr 28 17:19 UTC 2003

Why not turn on quota rather than degrade available inetd services?
remmers
response 17 of 65: Mark Unseen   Apr 28 23:13 UTC 2003

What I've heard regarding quotas on our current OS is not that
they're buggy, but rather that they'd seriously impact performance.
Offhand I can't cite a source for this.  I'd be in favor of trying
them at this point -- if they work, they're probably the simplest
solution, and if they cause too many new problems, we can always
back off.
valerie
response 18 of 65: Mark Unseen   Apr 29 02:23 UTC 2003

This response has been erased.

aruba
response 19 of 65: Mark Unseen   Apr 29 03:39 UTC 2003

Thanks, Valerie (and Scott), for all your hard work keeping the system
usable.
cross
response 20 of 65: Mark Unseen   Apr 29 04:13 UTC 2003

Regarding #18; Just how many hundreds and hundreds of megabytes did you
reclaim?  And how close to full were the disks?
steve
response 21 of 65: Mark Unseen   Apr 29 05:18 UTC 2003

   My personal best in terms of reclaming was about 360M; this happaned
when a new version of either acidblood or psybnc came out and we had
hordes of them streaming in, constantly.

   We do not want to implement disk quotas on SunOS.  If we mess anything
up, we'll pay for it in terms of staff time on a new emergency.
jp2
response 22 of 65: Mark Unseen   Apr 30 15:01 UTC 2003

This response has been erased.

mynxcat
response 23 of 65: Mark Unseen   Apr 30 15:16 UTC 2003

uh oh
valerie
response 24 of 65: Mark Unseen   Apr 30 15:32 UTC 2003

This response has been erased.

 0-24   25-49   50-65        
Response Not Possible: You are Not Logged In
 

- Backtalk version 1.3.30 - Copyright 1996-2006, Jan Wolter and Steve Weiss