1 |
Michael Higgins wrote: |
2 |
> So, in setting up a huge repository of junk, I mean, important |
3 |
> business documents, I nearly ran out of disk space on rootfs. Much of |
4 |
> it was living in /var, like half the disk's worth. |
5 |
> |
6 |
> I'd just dropped a new disk in for /home... to move some Outlook |
7 |
> files to IMAP & maildir folders. Had I been thinking ahead, I would |
8 |
> have partitioned it for /var as well, but I didn't. |
9 |
> |
10 |
> So, I rsyncd /var to /home/varlink, moved /var to /oldvar, 'soft' |
11 |
> linked /var to /home/varlink/var and restarted some services that |
12 |
> were less than happy with the change, like the mail servers, mysql. |
13 |
> Everything seems to work now. |
14 |
> |
15 |
> Now, was that a stupid thing to do, or should everything under /var |
16 |
> continue to work still, without issues? |
17 |
|
18 |
I've done it that way and don't remember running into any issues. I also |
19 |
did the "shut all services down, rsync var to somewhere, change mounts, |
20 |
sync it back" trick without taking the machine down. No long term issues |
21 |
with that other than having to rebuild the qmail queue at the time. |
22 |
qmail is weird and inodes are tied into the queue mechanism so that was |
23 |
expected. Modern MTAs shouldn't have the issue. Mysql Innodb can be a |
24 |
bit odd if you move the database around, but as long as nothing changes |
25 |
relative the mysql datadir it will also be fine. |
26 |
|
27 |
You might want to check your Mysql install and purge bin logs if you |
28 |
haven't lately. That tends to be the silent /var filler-upper in many |
29 |
systems. |
30 |
|
31 |
expire_logs_days = 7 is your friend. |
32 |
|
33 |
kashani |