[Listwork] partition at 95%
micah at riseup.net
Sun Jan 21 23:32:02 PST 2007
-----BEGIN PGP SIGNED MESSAGE-----
> pietro wrote:
>> Alster wrote:
>>> In contrary to the new server, I think this is an issue we need to solve
>>> short term. We cannot wait until money for a new server was granted. I
>>> assume this issue is related to the new backup script, which stores
>>> compressed copies of the mbox files on this partition (if I recall
>> i agree with you. and you are right about the backups. they are eating
>> 6GB+ of disk space now.
> I moved /mailman/mysql back to /var/backups/mysql. I'm saying 'back' as,
> previously, /var/backups/mysql was a symlink pointing to /mailman/mysql.
> This freed up 5.7G.
> Contents of /var/backups/mysql are just two other directories:
> Oct 2 02:20 hotcopy
> Jan 7 01:01 sqldump
> sqldump seems to be still in use, but I guess the hotcopy data (1.3G) is
> no longer used/needed. Anyone knows?
I know -- you can do mysql backups as either hotcopy or mysqldump method
(or both), we originally were doing both, but the databases are big and
while they are being dumped in both modes, the tables are locked, so
nothing can happen during that time. It didn't make sense to do both
hotcopy and sqldump, and I find sqldump a lot more reliable, so I
disabled the hotcopy method. I didn't remove this directory then, but I
just did now.
> What we could do would be to resize /usr which has only 860M of 5.8G
> used (4.7G free), but this would mean sarai downtime which is
> undesirable. Also, in my opinion, a better solution to our problem would
> be to
> * go through each single directory and determine whether it's still
> needed as I'm sure we have a lot of crap there nobody uses nor knows
> * find ways to reduce the amount of data we're storing. Using Lurker
> instead of pipermail (hint, hint, Ansti!) was one suggestion, but I
> guess there can be others, too.
I would really be against trying to resize /var. I believe I tried this
on sarai once, and the LVM was broken somehow and the resize didn't work
and I thought everything was really screwed up. I don't remember
everything, except that I got it back working and I decided then that I
no longer like LVM (this was the second resize that failed on me, two
times my heart stopped is too much).
>>> I think the options we have are to:
>>> o move sarai into a vserver, but have write access to iptables.
>>> o buy a complete (or almost complete) new server (less power consuming,
>>> a bit more RAM)
>>> Personally I prefer the first one, but write access to iptables and
>>> hosting within a vserver may be somewhat contradictionary, depending on
>>> who adminsters the main server (vserver host) and what else is hosted on
>>> this server.
>> is iptables access really important? can we instead rely on some
>> automated firewall lie shorewall?
I prefer the first one as well. We got a really nice vserver machine
online while I was in seattle, it has big disks and could host sarai. I
do not think it would be that difficult to move. There had been talk
about indymedia buying the disks, or paying for their part of them,
whatever way, I think that it makes the most sense to move to a vserver.
With myself and pietro doing the admin on the vserver host machine, we'd
both have access to the shorewall firewall configuration, and if
necessary we could create some way to have configuration available to
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
-----END PGP SIGNATURE-----
More information about the listwork