Re: File system full
Giorgos Keramidas wrote: On 2006-10-18 07:53, Office of CEO- rithy4u.NET [EMAIL PROTECTED] wrote: Dear All, My firewall server was running out of space on / partition I have try to reboot/fsck and delete all unneccessary files inside / but I still get 12 MB of free space with total 495 MB worth of that partition. Any ideas? First of all, try to track down where all the space has gone, by using `df' and `du' with the -x option. For example, you can get a good idea of which places in your root filesystem are the top-10 users of space with: # cd / # du -xm . | sort -nr | head -10 If this doesn't show up a lot of stuff, then there's probably a rogue process which has opened a file and then removed it, so it's not directly visible by traversing the tree with `du', but you can still look for it with: # fstat -f / | sort -k +8 After you get this sort of information, we can make more informed suggestions about the best way to move forward :) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] I have been trying to track down a similar problem! Using the above method I think I have found 'natd' to be the culprit. Should 'natd' receive a signal when 'alias.log' rolls over? Restarting 'natd' seems to have releases some megabytes. --- avast! Antivirus: Outbound message clean. Virus Database (VPS): 0642-0, 17/10/2006 Tested on: 18/10/2006 7:13:37 AM avast! - copyright (c) 1988-2006 ALWIL Software. http://www.avast.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: File system full
Paul Murphy writes: I have been trying to track down a similar problem! Using the above method I think I have found 'natd' to be the culprit. Should 'natd' receive a signal when 'alias.log' rolls over? Restarting 'natd' seems to have releases some megabytes. That's not actually clear from the man page. Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: File system full
On 2006-10-18 07:13, Paul Murphy [EMAIL PROTECTED] wrote: Giorgos Keramidas wrote: On 2006-10-18 07:53, Office of CEO- rithy4u.NET [EMAIL PROTECTED] wrote: Dear All, My firewall server was running out of space on / partition I have try to reboot/fsck and delete all unneccessary files inside / but I still get 12 MB of free space with total 495 MB worth of that partition. Any ideas? First of all, try to track down where all the space has gone, by using `df' and `du' with the -x option. For example, you can get a good idea of which places in your root filesystem are the top-10 users of space with: # cd / # du -xm . | sort -nr | head -10 If this doesn't show up a lot of stuff, then there's probably a rogue process which has opened a file and then removed it, so it's not directly visible by traversing the tree with `du', but you can still look for it with: # fstat -f / | sort -k +8 After you get this sort of information, we can make more informed suggestions about the best way to move forward :) I have been trying to track down a similar problem! Using the above method I think I have found 'natd' to be the culprit. Should 'natd' receive a signal when 'alias.log' rolls over? Restarting 'natd' seems to have releases some megabytes. Nice catch, Paul! The `alias.log' file is supposed to be in `/var/log', but I guess if you use a single root filesystem for everything, this can end up filling the root filesystem. The file `alias.log' is not rotated by `newsyslog.conf', so maybe we should add it there? Then we can let `newsyslog' signal `natd' by: %%% diff -r 4474abb9619a etc/newsyslog.conf --- a/etc/newsyslog.confFri Oct 13 17:34:54 2006 +0300 +++ b/etc/newsyslog.confWed Oct 18 15:54:52 2006 +0300 @@ -18,6 +18,7 @@ # # logfilename [owner:group]mode count size when flags [/pid_file] [sig_num] /var/log/all.log 600 7 *@T00 J +/var/log/alias.log 600 7 100 * JC /var/run/natd.pid /var/log/amd.log 644 7 100 * J /var/log/auth.log 600 7 100 * JC /var/log/console.log 600 5 100 * J %%% Can you please add this line to your newsyslog.conf file and let it run for a while to see if it prevents the `alias.log' file of `natd' to fill your /var/log filesystem? I don't use `natd', so I can't test this myself for a long enough period. Regards, Giorgos ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: File system full
Giorgos Keramidas wrote: On 2006-10-18 07:13, Paul Murphy [EMAIL PROTECTED] wrote: Giorgos Keramidas wrote: On 2006-10-18 07:53, Office of CEO- rithy4u.NET [EMAIL PROTECTED] wrote: Dear All, My firewall server was running out of space on / partition I have try to reboot/fsck and delete all unneccessary files inside / but I still get 12 MB of free space with total 495 MB worth of that partition. Any ideas? First of all, try to track down where all the space has gone, by using `df' and `du' with the -x option. For example, you can get a good idea of which places in your root filesystem are the top-10 users of space with: # cd / # du -xm . | sort -nr | head -10 If this doesn't show up a lot of stuff, then there's probably a rogue process which has opened a file and then removed it, so it's not directly visible by traversing the tree with `du', but you can still look for it with: # fstat -f / | sort -k +8 After you get this sort of information, we can make more informed suggestions about the best way to move forward :) I have been trying to track down a similar problem! Using the above method I think I have found 'natd' to be the culprit. Should 'natd' receive a signal when 'alias.log' rolls over? Restarting 'natd' seems to have releases some megabytes. Nice catch, Paul! The `alias.log' file is supposed to be in `/var/log', but I guess if you use a single root filesystem for everything, this can end up filling the root filesystem. The file `alias.log' is not rotated by `newsyslog.conf', so maybe we should add it there? Then we can let `newsyslog' signal `natd' by: %%% diff -r 4474abb9619a etc/newsyslog.conf --- a/etc/newsyslog.conf Fri Oct 13 17:34:54 2006 +0300 +++ b/etc/newsyslog.conf Wed Oct 18 15:54:52 2006 +0300 @@ -18,6 +18,7 @@ # # logfilename [owner:group]mode count size when flags [/pid_file] [sig_num] /var/log/all.log 600 7 *@T00 J +/var/log/alias.log 600 7 100 * JC /var/run/natd.pid /var/log/amd.log 644 7 100 * J /var/log/auth.log600 7 100 * JC /var/log/console.log 600 5 100 * J %%% Can you please add this line to your newsyslog.conf file and let it run for a while to see if it prevents the `alias.log' file of `natd' to fill your /var/log filesystem? I don't use `natd', so I can't test this myself for a long enough period. natd doesn't do the close and re-open all filehandles thing on receipt of SIGHUP which pretty much makes it unsuitable for use with newsyslog. (SIGHUP is caught by natd, but the only thing it does is cause natd to update its idea of what the IP address is on the nat'ed interface.) There doesn't seem to be any signal that you can send natd with the usual 'reread all config files and re-open all file descriptors' effect that most daemons understand. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. Flat 3 7 Priory Courtyard PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW, UK signature.asc Description: OpenPGP digital signature
Re: File system full
Matthew Seaman writes: There doesn't seem to be any signal that you can send natd with the usual 'reread all config files and re-open all file descriptors' effect that most daemons understand. The next obvious questions are would that be desirable behavior? and how hard would it be to implement?. Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: File system full
On 2006-10-18 14:34, Matthew Seaman [EMAIL PROTECTED] wrote: Giorgos Keramidas wrote: The file `alias.log' is not rotated by `newsyslog.conf', so maybe we should add it there? Then we can let `newsyslog' signal `natd' by: %%% diff -r 4474abb9619a etc/newsyslog.conf --- a/etc/newsyslog.confFri Oct 13 17:34:54 2006 +0300 +++ b/etc/newsyslog.confWed Oct 18 15:54:52 2006 +0300 @@ -18,6 +18,7 @@ # # logfilename [owner:group]mode count size when flags [/pid_file] [sig_num] /var/log/all.log 600 7 *@T00 J +/var/log/alias.log 600 7 100 * JC /var/run/natd.pid /var/log/amd.log 644 7 100 * J /var/log/auth.log 600 7 100 * JC /var/log/console.log 600 5 100 * J %%% Can you please add this line to your newsyslog.conf file and let it run for a while to see if it prevents the `alias.log' file of `natd' to fill your /var/log filesystem? I don't use `natd', so I can't test this myself for a long enough period. natd doesn't do the close and re-open all filehandles thing on receipt of SIGHUP which pretty much makes it unsuitable for use with newsyslog. (SIGHUP is caught by natd, but the only thing it does is cause natd to update its idea of what the IP address is on the nat'ed interface.) There doesn't seem to be any signal that you can send natd with the usual 'reread all config files and re-open all file descriptors' effect that most daemons understand. That's probably a bug, then, I guess. The fact that natd can keep a file open for an arbitrary amount of time and keep appending to it, until either natd dies or the file fills up an entire partition is not really a good idea :( I'll open a PR for this, and see if the people more knowledgeable with natd's internals can help with the SIGHUP-triggered actions of natd. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: File system full
On 2006-10-18 07:53, Office of CEO- rithy4u.NET [EMAIL PROTECTED] wrote: Dear All, My firewall server was running out of space on / partition I have try to reboot/fsck and delete all unneccessary files inside / but I still get 12 MB of free space with total 495 MB worth of that partition. Any ideas? First of all, try to track down where all the space has gone, by using `df' and `du' with the -x option. For example, you can get a good idea of which places in your root filesystem are the top-10 users of space with: # cd / # du -xm . | sort -nr | head -10 If this doesn't show up a lot of stuff, then there's probably a rogue process which has opened a file and then removed it, so it's not directly visible by traversing the tree with `du', but you can still look for it with: # fstat -f / | sort -k +8 After you get this sort of information, we can make more informed suggestions about the best way to move forward :) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: file system full
`du -h / | grep ...M ' will show you all files that are more than 1.0MB in size. `find /var -type d | sed 's/.*//' | xargs du -sm | sort -g` will do the same thing, but list them with the largest files last. 'df -h' should show you free space, but does not always update immediatly. If that large file doesn't exist in either of the above lists then you shouldn't have a problem. Consider moving your squid log to /usr/log/squid.log and symlinking it to /var/log (assuming you have a large /usr partition) On 5/4/06, Rodrigo Mufalani [EMAIL PROTECTED] wrote: Hi all, My /var is fully 99%, because I create one tar.gz of the squid logs. I was move for smbfs, then network die!!! I try: rm -rf file.tar.gz and don't have more free space oon the file system. Somebody help me? Att, Rodrigo Mufalani This message was sent using IMP, the Internet Messaging Program. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- -- Perfection is just a word I use occasionally with mustard. --Atom Powers-- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: file system full
Hi all, My /var is fully 99%, because I create one tar.gz of the squid logs. I was move for smbfs, then network die!!! I try: rm -rf file.tar.gz and don't have more free space oon the file system. Somebody help me? Do you have any other disk space large enough to hold that big file? Move it there. Can you compress/gzip it to someplace like /tmp? jerry Att, Rodrigo Mufalani This message was sent using IMP, the Internet Messaging Program. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: file system full
Rodrigo Mufalani [EMAIL PROTECTED] writes: Hi all, My /var is fully 99%, because I create one tar.gz of the squid logs. I was move for smbfs, then network die!!! I try: rm -rf file.tar.gz and don't have more free space oon the file system. Somebody help me? You are asking the Frequently Asked Question: The du and df commands show different amounts of disk space available. What is going on? See: http://be-well.ilk.org/FreeBSD/doc/en_US.ISO8859-1/books/faq/disks.html#DU-VS-DF ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: file system full
Hi all, My /var is fully 99%, because I create one tar.gz of the squid logs. I was move for smbfs, then network die!!! I try: rm -rf file.tar.gz and don't have more free space oon the file system. Somebody help me? Also, be sure that no process (ie. squid, syslog, etc.) still has an open file handle on any of the files you think you'v removed/moved. They aren't really gone till you restart those processes and they close/open the file handles... -philip ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: file system full help
On Fri, 21 Apr 2006 02:23:41 +0200, Alex de Kruijff wrote On Thu, Apr 20, 2006 at 06:46:14AM -0800, Noah wrote: I sometimes get reports of file system full but not accurately because when viewing the drive with df -k I find there is adequate space on the drive. Usually this is casused by log files considered larger than the available space on the /var directory. That you don't have adequate space for the task at hand. In this case compressing the log (this means the source needs to be arround wile a new bzip file is created) and create a new fresh file. I would like to see if this in fact the case. Can somebody please remind me what commands I can use to troubleshoot this current condition? Use 'du -s * | sort -n' to find the largest files I was looking for lsof - du only shows written files. -- Alex Please copy the original recipients, otherwise I may not read your reply. Howtos based on my personal use, including information about setting up a firewall and creating traffic graphs with MRTG http://alex.kruijff.org/FreeBSD/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: file system full help
On Thu, Apr 20, 2006 at 06:46:14AM -0800, Noah wrote: I sometimes get reports of file system full but not accurately because when viewing the drive with df -k I find there is adequate space on the drive. Usually this is casused by log files considered larger than the available space on the /var directory. That you don't have adequate space for the task at hand. In this case compressing the log (this means the source needs to be arround wile a new bzip file is created) and create a new fresh file. I would like to see if this in fact the case. Can somebody please remind me what commands I can use to troubleshoot this current condition? Use 'du -s * | sort -n' to find the largest files -- Alex Please copy the original recipients, otherwise I may not read your reply. Howtos based on my personal use, including information about setting up a firewall and creating traffic graphs with MRTG http://alex.kruijff.org/FreeBSD/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: file system full help
On Fri, 21 Apr 2006 02:23:41 +0200, Alex de Kruijff wrote On Thu, Apr 20, 2006 at 06:46:14AM -0800, Noah wrote: I sometimes get reports of file system full but not accurately because when viewing the drive with df -k I find there is adequate space on the drive. Usually this is casused by log files considered larger than the available space on the /var directory. That you don't have adequate space for the task at hand. In this case compressing the log (this means the source needs to be arround wile a new bzip file is created) and create a new fresh file. I would like to see if this in fact the case. Can somebody please remind me what commands I can use to troubleshoot this current condition? Use 'du -s * | sort -n' to find the largest files Hi there, actually du does not give enough information. 'lsof' is the answer I was looking for. I want to look at open files that have not been written to the drive. Cheers, Noah -- Alex Please copy the original recipients, otherwise I may not read your reply. Howtos based on my personal use, including information about setting up a firewall and creating traffic graphs with MRTG http://alex.kruijff.org/FreeBSD/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: File system full?
On Thursday 01 January 2004 11:46 pm, Malcolm Kay wrote: $ df -h FilesystemSize Used Avail Capacity Mounted on /dev/ad0s3a 1008M92M 835M10%/ /dev/ad0s2 1020M19M 1001M 2%/dos /dev/ad0s3g 4.8G69M 4.3G 2%/home /dev/ad0s3e 3.9G 3.9G -260.5M 107%/usr /dev/ad0s3f 1008M27M 900M 3%/var /dev/ad0s1 24G22G 2.9G88%/nt procfs4.0K 4.0K 0B 100%/proc /dev/da0s1 61M61M 632K99%/umass One of the suggested setups is to provide home with its own partition. And even though you don't use it it is not so uncommon. As you can see above, /home is on it's very own partition. The two partitions appear to be adjacent. If they are, Partition Magic (or similar) could merge those two partitions non-destructively, and your problem would be solved. This sounds like a disaster --- partition magic works with MS partitions or in FBSD terms slices -- to the best I my knowledge it does not know about BSD style partitions. Partition Magic can recognize a type 165 (freebsd) partition, but it does not support merging/resizing of these. It does support the linux partition scheme, however. -- Eric F Crist AdTech Integrated Systems, Inc (612) 998-3588 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: File system full?
On Thursday 01 January 2004 10:15 pm, Scott W wrote: Here's my df -h readout: $ df -h FilesystemSize Used Avail Capacity Mounted on /dev/ad0s3a 1008M92M 835M10%/ /dev/ad0s2 1020M19M 1001M 2%/dos /dev/ad0s3g 4.8G69M 4.3G 2%/home /dev/ad0s3e 3.9G 3.9G -260.5M 107%/usr /dev/ad0s3f 1008M27M 900M 3%/var /dev/ad0s1 24G22G 2.9G88%/nt procfs4.0K 4.0K 0B 100%/proc /dev/da0s1 61M61M 632K99%/umass 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. I'm probably going to leave everything as it is. I ran a make clean from the /usr/ports directory, did nothing else, and this is now my df -h readout: $ df -h FilesystemSize Used Avail Capacity Mounted on /dev/ad0s3a 1008M92M 835M10%/ /dev/ad0s3g 4.8G70M 4.3G 2%/home /dev/ad0s3e 3.9G 2.2G 1.4G61%/usr /dev/ad0s3f 1008M27M 900M 3%/var /dev/ad0s1 24G22G 2.9G88%/nt procfs4.0K 4.0K 0B 100%/proc /dev/ad0s2 1020M19M 1001M 2%/dos $ As you can see, there is a massive decrease in parition use after that completed. What I didn't think about was that I compiled all the following 'hog' sources, kde, apsfilter, and x. Thanks for the help/advice! -- Eric F Crist AdTech Integrated Systems, Inc (612) 998-3588 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: File system full?
On Sat, 3 Jan 2004 03:47, Eric F Crist wrote: On Thursday 01 January 2004 11:46 pm, Malcolm Kay wrote: [snip] [not Malcolm Kay] $ df -h FilesystemSize Used Avail Capacity Mounted on /dev/ad0s3a 1008M92M 835M10%/ /dev/ad0s2 1020M19M 1001M 2%/dos /dev/ad0s3g 4.8G69M 4.3G 2%/home /dev/ad0s3e 3.9G 3.9G -260.5M 107%/usr /dev/ad0s3f 1008M27M 900M 3%/var /dev/ad0s1 24G22G 2.9G88%/nt procfs4.0K 4.0K 0B 100%/proc /dev/da0s1 61M61M 632K99%/umass [snip] [not Malcolm Kay] The two partitions appear to be adjacent. If they are, Partition Magic (or similar) could merge those two partitions non-destructively, and your problem would be solved. [The next is Malcolm Kay] This sounds like a disaster --- partition magic works with MS partitions or in FBSD terms slices -- to the best I my knowledge it does not know about BSD style partitions. [The next is Eric F Crist] Partition Magic can recognize a type 165 (freebsd) partition, but it does not support merging/resizing of these. It does support the linux partition scheme, however. Please read my words carefully: Yes, Partition Magic recognises partitions in the MS partitioning scheme, known as slices in FreeBSD, including those labeled as BSD (type 165). These have device names (under FBSD) of the form ad0s1, ad0s2, ads0s3 etc. However, I do not believe it knows anything of BSD partitions which subdivide such a slice. These have device name of the form ad0s3a, ad0s3b, ad0s3e etc. Native Linux uses only slices (MS style partitioning). It knows something of BSD partitioning in order to mount (foreign) BSD file systems. Malcolm Kay ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: File system full?
On Thursday 01 January 2004 06:00 pm, Eric F Crist wrote: 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 FilesystemSize Used Avail Capacity Mounted on /dev/ad0s3a 1008M92M 835M10%/ /dev/ad0s2 1020M19M 1001M 2%/dos /dev/ad0s3g 4.8G69M 4.3G 2%/home /dev/ad0s3e 3.9G 3.9G -260.5M 107%/usr /dev/ad0s3f 1008M27M 900M 3%/var /dev/ad0s1 24G22G 2.9G88%/nt procfs4.0K 4.0K 0B 100%/proc /dev/da0s1 61M61M 632K99%/umass If you have source installed, that takes up a bit. If you don't see yourself doing a makeworld and building kernel - a binary install would have done nicely. -- Best regards, Chris ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: File system full?
On Thu, Jan 01, 2004 at 06:00:23PM -0600, Eric F Crist wrote: 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 FilesystemSize Used Avail Capacity Mounted on /dev/ad0s3a 1008M92M 835M10%/ /dev/ad0s2 1020M19M 1001M 2%/dos /dev/ad0s3g 4.8G69M 4.3G 2%/home /dev/ad0s3e 3.9G 3.9G -260.5M 107%/usr /dev/ad0s3f 1008M27M 900M 3%/var /dev/ad0s1 24G22G 2.9G88%/nt procfs4.0K 4.0K 0B 100%/proc /dev/da0s1 61M61M 632K99%/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]
Re: File system full?
On Thursday 01 January 2004 06:04 pm, Chris wrote: If you have source installed, that takes up a bit. If you don't see yourself doing a makeworld and building kernel - a binary install would have done nicely. I do have source installed, and I do a bi-weekly source update automatically when my laptop is home. I like having the sources there. Any other suggestions on which directories I can squash? -- Eric F Crist AdTech Integrated Systems, Inc (612) 998-3588 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: File system full?
On Thursday 01 January 2004 06:15 pm, Eric F Crist wrote: On Thursday 01 January 2004 06:04 pm, Chris wrote: If you have source installed, that takes up a bit. If you don't see yourself doing a makeworld and building kernel - a binary install would have done nicely. I do have source installed, and I do a bi-weekly source update automatically when my laptop is home. I like having the sources there. Any other suggestions on which directories I can squash? Never mind. I seem to have forgotten you can do a make clean from the /usr/ports and you're fine! Sorry for the unnecessary traffic. -- Eric F Crist AdTech Integrated Systems, Inc (612) 998-3588 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: File system full?
On Thu, Jan 01, 2004 at 06:23:15PM -0600, Eric F Crist wrote: On Thursday 01 January 2004 06:15 pm, Eric F Crist wrote: On Thursday 01 January 2004 06:04 pm, Chris wrote: If you have source installed, that takes up a bit. If you don't see yourself doing a makeworld and building kernel - a binary install would have done nicely. I do have source installed, and I do a bi-weekly source update automatically when my laptop is home. I like having the sources there. Any other suggestions on which directories I can squash? Never mind. I seem to have forgotten you can do a make clean from the /usr/ports and you're fine! Try `make -DNOCLEANDEPENDS clean` instead, it'll run much quicker. -T -- Page 12: Unix is a set of tools for smart people. - Harley Hahn, _The Unix Companion_ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: File system full?
Chris writes: Here's my df -h readout: $ df -h FilesystemSize Used Avail Capacity Mounted on /dev/ad0s3e 3.9G 3.9G -260.5M 107%/usr If you have source installed, that takes up a bit. If you don't see yourself doing a makeworld and building kernel - a binary install would have done nicely. The source for 5.2-RC runs about 375 Mb. Try this: cd /usr du | sort -nr and see if any directories are suspiciously large. (This is sufficiently useful I have it as a cron job that drops it in my morning mail.) Also check for core dumps: find /usr -name *.core Robert Huff ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: File system full?
Gautam Gopalakrishnan wrote: On Thu, Jan 01, 2004 at 06:00:23PM -0600, Eric F Crist wrote: 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 FilesystemSize Used Avail Capacity Mounted on /dev/ad0s3a 1008M92M 835M10%/ /dev/ad0s2 1020M19M 1001M 2%/dos /dev/ad0s3g 4.8G69M 4.3G 2%/home /dev/ad0s3e 3.9G 3.9G -260.5M 107%/usr /dev/ad0s3f 1008M27M 900M 3%/var /dev/ad0s1 24G22G 2.9G88%/nt procfs4.0K 4.0K 0B 100%/proc /dev/da0s1 61M61M 632K99%/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] 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. 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.1G12%/ devfs 1.0K 1.0K 0B 100%/dev /dev/ipsd0s1e 965M22K 888M 0%/tmp /dev/ipsd0s2d 4.0G 2.8G 900M76%/usr /dev/ipsd0s1d 965M31M 857M 4%/var procfs 4.0K 4.0K 0B 100%/proc sol:/export/home 182G63G 117G35%/usr/home sol:/export/mail 182G63G 117G35%/var/spool/mail sol:/export/ports 182G63G 117G35%/usr/ports Scott ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: File system full?
On Fri, 2 Jan 2004 10:30 am, Eric F Crist wrote: 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 FilesystemSize Used Avail Capacity Mounted on /dev/ad0s3a 1008M92M 835M10%/ /dev/ad0s2 1020M19M 1001M 2%/dos /dev/ad0s3g 4.8G69M 4.3G 2%/home /dev/ad0s3e 3.9G 3.9G -260.5M 107%/usr /dev/ad0s3f 1008M27M 900M 3%/var /dev/ad0s1 24G22G 2.9G88%/nt procfs4.0K 4.0K 0B 100%/proc /dev/da0s1 61M61M 632K99%/umass $ My /home is a link to /usr/home. Isn't yours? If it IS (notwithstanding your creation of a /home partition), that would explain why you have only 69M in /home but 3.9G in /usr. The two partitions appear to be adjacent. If they are, Partition Magic (or similar) could merge those two partitions non-destructively, and your problem would be solved. BTW, on my system, I have separate partitions for /usr/local and /usr. That seems to even the disk space usage quite well. /dev/ad2s1a 394M 249M 113M69%/ /dev/ad2s1f 6.9G 2.7G 3.6G43%/usr /dev/ad2s1e 246M 191M35M84%/var /dev/ad2s1g 6.9G 4.8G 1.5G76%/usr/local HTH -- Regards, Brian ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: File system full?
On Fri, 2 Jan 2004 15:44, Brian Astill wrote: On Fri, 2 Jan 2004 10:30 am, Eric F Crist wrote: 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 FilesystemSize Used Avail Capacity Mounted on /dev/ad0s3a 1008M92M 835M10%/ /dev/ad0s2 1020M19M 1001M 2%/dos /dev/ad0s3g 4.8G69M 4.3G 2%/home /dev/ad0s3e 3.9G 3.9G -260.5M 107%/usr /dev/ad0s3f 1008M27M 900M 3%/var /dev/ad0s1 24G22G 2.9G88%/nt procfs4.0K 4.0K 0B 100%/proc /dev/da0s1 61M61M 632K99%/umass $ My /home is a link to /usr/home. Isn't yours? If it IS (notwithstanding your creation of a /home partition), that would explain why you have only 69M in /home but 3.9G in /usr. One of the suggested setups is to provide home with its own partition. And even though you don't use it it is not so uncommon. The two partitions appear to be adjacent. If they are, Partition Magic (or similar) could merge those two partitions non-destructively, and your problem would be solved. This sounds like a disaster --- partition magic works with MS partitions or in FBSD terms slices -- to the best I my knowledge it does not know about BSD style partitions. I'd also be very surprised if it is able to merge BSD file systems non-destructively. Malcolm Kay ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: File system full?
Malcolm Kay wrote: On Fri, 2 Jan 2004 15:44, Brian Astill wrote: On Fri, 2 Jan 2004 10:30 am, Eric F Crist wrote: 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 FilesystemSize Used Avail Capacity Mounted on /dev/ad0s3a 1008M92M 835M10%/ /dev/ad0s2 1020M19M 1001M 2%/dos /dev/ad0s3g 4.8G69M 4.3G 2%/home /dev/ad0s3e 3.9G 3.9G -260.5M 107%/usr /dev/ad0s3f 1008M27M 900M 3%/var /dev/ad0s1 24G22G 2.9G88%/nt procfs4.0K 4.0K 0B 100%/proc /dev/da0s1 61M61M 632K99%/umass $ My /home is a link to /usr/home. Isn't yours? If it IS (notwithstanding your creation of a /home partition), that would explain why you have only 69M in /home but 3.9G in /usr. One of the suggested setups is to provide home with its own partition. And even though you don't use it it is not so uncommon. The two partitions appear to be adjacent. If they are, Partition Magic (or similar) could merge those two partitions non-destructively, and your problem would be solved. This sounds like a disaster --- partition magic works with MS partitions or in FBSD terms slices -- to the best I my knowledge it does not know about BSD style partitions. I'd also be very surprised if it is able to merge BSD file systems non-destructively. I'm almost positive it doesn't. Partition Magic also needs to understand the underlying filesystem, not just the partition table, as almost any operation aside from expanding a single partition on a disk with only one partition plus unused space would result in actually moving data around.. PM 8.0 (should be the latest I believe) can't touch Linux ReiserFS, so I'd be highly surprised if it understood UFS2. Scott Malcolm Kay ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
