Re: Size of /var worries me
in message [EMAIL PROTECTED], wrote Roger 'Rocky' Vetterberg thusly... I apologize for replying so late. parv wrote: ...only thing that i desire(d) is/was to give / much less than 128MB, but couldn't (during the space slicing). That and to combine /usr2 /usr3 now. But default inode space allocation of 8%/slice will kill me anyway. I really have to remember about the newfs options next time. Do you really mean inode space, or the 8% minimum free space treshold? Yes, i was refererring to the inode space. I have few large files... Filesystem 1K-blocksUsed Avail Capacity iused ifree %iused /dev/ad0s2g 3106182 2532670 32501889% 60186 329188 15% /dev/ad0s3f984654 856366 4951695% 66158 57488 54% If its the later, try this: umount /usr tunefs -m 0 /dev/ad-whatever mount /usr Something to be aware of. If nothing, i need to at least print out the newfs, mount, and tunefs man pages. Thanks. - Parv -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Size of /var worries me
parv wrote: ...only thing that i desire(d) is/was to give / much less than 128MB, but couldn't (during the space slicing). That and to combine /usr2 /usr3 now. But default inode space allocation of 8%/slice will kill me anyway. I really have to remember about the newfs options next time. Do you really mean inode space, or the 8% minimum free space treshold? If its the later, try this: umount /usr tunefs -m 0 /dev/ad-whatever mount /usr -- R ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Size of /var worries me
On Wed, Jan 07, 2004 at 01:38:35AM -0800, Dino Vliet wrote: Hi there, I've installed freebsd 4.9 and am currently busy with installing third party apps through the ports collection. What worries me however is the size of my /var directory. You might consider symlinking /var to /usr/var perhaps - unless you have any other spare space that you can allocate to the /var fs - 67MB is quite small, especially if you intend to use any databases at any point in time. The best way to go about symlinking /var to somewhere else is to go into single user mode at boot time (or kill all processes that use anything under /var), move /var to /usr/var and then symlink /var to /usr/var. This isn't really the best solution in terms of performance (although you wouldn't notice on a low load system), but unless you have extra free disk space you can allocate to /var or are prepared to reinstall - allocating more space to /var in the installation - then the symlinking option is viable. I also had to get rid of a pkg.db file in the /var/db/pkg directory because it took a lot of space. As a note, the pkg.db file is quite important - port installations register themselves in the /var/db/pkg/pkg.db database and this is used to check on dependencies etc, a little bit like the windows registry is used (only a little!). Generally deleting files from under /var isn't the best solution :P q1) Do I have to worry about my /vardirectory Yes, FreeBSD uses the /var filesystem to log things to (/var/log), to keep check on the state of daemons (/var/state, /var/run), to lock files (/var/lock) and numerous other things. Not to mention that databases are by default installed into /var/db/mysql for example in the case of mysql. Generally the /var filesystem is very important for the day-to-day running of a FreeBSD system. q2) How can I get rid of files I don't need (like XFree86.0.log..) As mentioned above it's generally not a good idea to delete files from /var/ on an ad-hoc basis. A better plan: organize a logfile rotation policy so that old logfiles are rotated out of /var/log into a backup location which has enough space. See the manpage on newsyslog for info on this. configure daemons so that they only log what is absolutely necessary for your needs. -- Jez Hancock - System Administrator / PHP Developer http://munk.nu/ http://jez.hancock-family.com/ - personal weblog http://ipfwstats.sf.net/- ipfw peruser traffic logging ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Size of /var worries me
in message [EMAIL PROTECTED], wrote Dino Vliet thusly... I've installed freebsd 4.9 and am currently busy with installing third party apps through the ports collection. What worries me however is the size of my /var directory. Take a look at my disk geometry (below) I also had to get rid of a pkg.db file in the /var/db/pkg directory because it took a lot of space. Unless that file os part of the core pkg* facilities, you have shot your foot. q2) How can I get rid of files I don't need (like XFree86.0.log..) Other suggestions are welcome... See syslogd(8), syslog(3), syslog.conf(5) newsyslog(8). Filesystem Size Used Avail Capacity Mounted on /dev/ad0s2a 126M 35M 81M 30% / /dev/ad0s2f 98M 10.0K 91M 0% /tmp /dev/ad0s2g 6.6G 1.5G 4.5G 25% /usr /dev/ad0s2e 74M 67M 978K 99% /var How do you feel about merging /tmp w/ /var and mounting /tmp on swap partition, that you did not list, as memory file system? Mind that core '/usr', here, occupies ~263 MB, minus perl, sendmail, and fortran part of the base compiler suite. You could divide your current '/usr' to be ~400MB slice for only core components, move '/var' to rest of the '/usr' slice, say '/usr2'. That will left you w/... swap at least as much as RAM (/tmp on swap) /~100 MB /usr ~400 MB /usr2 rest MB (/var symlinked to /usr2/var) ...but that is just one way to organize. Your pattern of usage will/should control if /tmp can be mounted on swap, and if to keep /var as a directory not a slice. Some would say just to keep separate / and combine everything else, resulting in three slices: swap, /, /usr. Also, newfs'ing procedure might itself constrain the space allocated to a slice. == xx == Here is my current layout... Filesystem 1K-blocksUsed Avail Capacity Mounted on /dev/ad0s2a128990 82322 3635069%/ /dev/ad0s2e516062 453968 2081096%/usr /dev/ad0s2g 3106182 2569086 28860290%/usr2 /dev/ad0s3f984654 859182 4670095%/usr3 /dev/ad0s3e 1753902 466558 114703229%/cdrw mfs:15 372846 6 343014 0%/tmp Device 1K-blocks UsedAvail Capacity Type /dev/ad0s2b37730451740 32556414%Interleaved ...only thing that i desire(d) is/was to give / much less than 128MB, but couldn't (during the space slicing). That and to combine /usr2 /usr3 now. But default inode space allocation of 8%/slice will kill me anyway. I really have to remember about the newfs options next time. Here is the holding pattern of each slice... /- usual stuff /usr - large ports -- erlang, gcc, java -- related files besides core components as listed above /usr2 - 'home', 'local' 'X11R6', and some ports related files /usr3 - 'sup' tree for cvsup ports tree. /cdrw - keeps 'src' tree used for world building; works as port building space now that space on /usr3 is diminishing /tmp - mounted on swap; rarely gets heavy use. - Parv -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
