On Thu, Jan 01, 2004 at 06:00:23PM -0600, Eric F Crist wrote:Advice- leave /var and / the size they are, they're fine if the box stays up as a server and runs any public services- apache logs and even messages log files can fill up /var relatively quickly, and if you add a database or any other service that can potentially log verbosely if it encounters any problems (or if you enable debug logging), /var can grow quickly.
How big is necessary for a /usr partition? Mine keeps filling up and I've deleted /usr/obj and /usr/ports/distfiles regularly.
Here's my df -h readout:
$ df -h
Filesystem Size Used Avail Capacity Mounted on
/dev/ad0s3a 1008M 92M 835M 10% /
/dev/ad0s2 1020M 19M 1001M 2% /dos
/dev/ad0s3g 4.8G 69M 4.3G 2% /home
/dev/ad0s3e 3.9G 3.9G -260.5M 107% /usr
/dev/ad0s3f 1008M 27M 900M 3% /var
/dev/ad0s1 24G 22G 2.9G 88% /nt
procfs 4.0K 4.0K 0B 100% /proc
/dev/da0s1 61M 61M 632K 99% /umass
I don't think you need such big / and /var partitions... And you could merge /home and /usr and make home dirs on /usr/home
Gautam
_______________________________________________ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
If you routinely delete rotated log files, and grow /usr to be 'big enough' (meaning don't merge it into / ), you can probably get away with half of what you're using for / and /var, but I wouldn't go smaller.
You can migrate /home if need be as suggested into /usr/home and update your home dirs in /etc/passwd, or you can also move the entire ports tree into your /home partition via symlink, which may sound funny but it a bit more 'traditional' on other *nixes- keeping generally static programs only in the /usr partition, and normally growing/changing contents in seperate disks (/var, /home). The ports collection and size is changing by nature, and sometimes significantly (building X, KDE, OpenOffice, Mozilla and others from source).
You can do the following if you'd like: mkdir /home/ports cd /usr/ports tar cpf - . | (cd /home/ports ; tar xvf - )
to copy the ports tree over to it's new 'home' (bad pun), then:
diff -R /usr/ports /home/ports
for your sanity, but unnescessary unless someone is doing a cvsup or build while you're copying files..
Then go ahead and blow away the original ports tree: rm -fr /usr/ports
and symlink to it's new home....
ln -s /home/ports /usr/ports
My ports tree is currently taking up ~715M: (Ignore the df output, home/mail/ports are currently on a single RAID volume via NFS), with the /usr filesystem at 2.8G with a fair number of packages installed, but no KDE, GNOME, etc, so it can grow by a fair amount yet...
[0] # du -hs /usr/ports 717M /usr/ports [EMAIL PROTECTED] /var/log/ [0] # df -h Filesystem Size Used Avail Capacity Mounted on /dev/ipsd0s1a 1.4G 157M 1.1G 12% / devfs 1.0K 1.0K 0B 100% /dev /dev/ipsd0s1e 965M 22K 888M 0% /tmp /dev/ipsd0s2d 4.0G 2.8G 900M 76% /usr /dev/ipsd0s1d 965M 31M 857M 4% /var procfs 4.0K 4.0K 0B 100% /proc sol:/export/home 182G 63G 117G 35% /usr/home sol:/export/mail 182G 63G 117G 35% /var/spool/mail sol:/export/ports 182G 63G 117G 35% /usr/ports
Scott
_______________________________________________ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
