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]
File system full
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? Rgds, -- *Rithy Ray, RCSA* Chief Executive Officer Web: www.rithy4u.net http://www.rithy4u.net Email: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] Phone: (855) 12 403 001 -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
File system full
Office of CEO- rithy4u.NET writes: 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? du -x / | sort -nr | head -n 50 | more Longer version: you should know what lives on directly under / and roughly how much space it takes. If some directory which used to take 27.4 mb suddenly has 311 mb 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: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]
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? 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]
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]
file system full help
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. 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? thanks in advance, Noah ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
file system full help
Noah writes: 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. 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? lsof? 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: [freebsd-questions] file system full help
On 20 Apr 2006 11:46:18 -0400, Lowell Gilbert wrote Noah [EMAIL PROTECTED] writes: 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. 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? I'm not sure I understand what you're asking correctly, but these FAQ entries may help explain what the filesystem is doing: http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/disks.html#DU- VS-DF http://www.freebsd.org/doc/en_US.ISO8859- 1/books/faq/disks.html#DISK-MORE-THAN-FULL you know I found those pages and they were completely unhelpful. lsof looks a lot deeper and sees reserved space that df and du does not show. read my original post. I already explained that. cheers, Naoh ___ 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]
cvsup File System Full
Hi all, cvsup failed on me ( filled up a 3.0 G /usr dir). I am in the proces of moving /usr to a sub dir under /home/ which has 30 G. Hopefully, I can rerun cvsup with success. I will create a soft link from /usr - /home/usr. At some point, I will want to move /usr back to its proper place. But it wont fit! Any ideas one what can me deleted afterwards? -Grant ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: cvsup File System Full
On Saturday 17 September 2005 13:44, Grant Peel wrote: Hi all, cvsup failed on me ( filled up a 3.0 G /usr dir). I am in the proces of moving /usr to a sub dir under /home/ which has 30 G. Hopefully, I can rerun cvsup with success. I will create a soft link from /usr - /home/usr. At some point, I will want to move /usr back to its proper place. But it wont fit! Any ideas one what can me deleted afterwards? -Grant You sould only mov /usr/src and /usr/obj then just set soft links to them, example: mv /usr/src /home mv /usr/obj /home ln -sv /home/src /usr/src ln -sv /home/obj /usr/obj -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: /root file system full
Yes, Bob you are right. The real problem was running KDE while logged in as root, not installing ports. I deleted all the files that KDE placed in / and now everything is fine. Once again, thanks Ron -Original Message- From: Bob Johnson [SMTP:[EMAIL PROTECTED] Sent: Saturday, 6 March 2004 3:24 PM To: Ron Joordens Subject: Re: /root file system full On Wednesday 03 March 2004 11:55 pm, you wrote: Bob, Thanks for taking the time to answer my query. My filesystem setup is the default one as suggested during the installation. IE. 128mb for /root, 512mb for /swap, 256mb for /var, 256mb for /tmp and the rest of the 6gb partition (slice) for /usr. A detail: / and /root are not the same thing. The root partition is /, while /root is a directory named root in that partition. I currently think as a result of some of the answers I have received, that the problem is that I have been logging in as root to install ports etc, when I should have been logging in as a user and doing an su to root to install. I don't believe this is your problem. It is a good security precaution, but AFAIK, it won't affect where files end up when you install ports. Some of the security issues are: doing routine operations as root creates the risk that a minor typing error will do major damage that an unprivileged user wouldn't be able to do; if an attacker manages to steal your password, hijack a remote login session, or whatever, they still won't have root access (make them work for it); on multi-administrator systems it provides some degree of accountability; it lets you prohibit remote logins by root (the FreeBSD default, by the way); and more that don't come to mind at the moment. Also running KDE etc while logged in as root may have written KDE files to me / directory. I know, silly boy, but to a beginner when the handbook says that ports can only be installed while logged in as root then I log in as root. The subtle difference between the two is nowhere explained. At least I haven't seen it. This part is accurate. Logging in to KDE as root will add some cruft to your / partition. And KDE always writes stuff into /var/tmp (or /tmp in older versions), regardless of which user invokes it. I shall certainly take note of your advice and have a look at deleting any temp and uneccessary files, creating symlinks and making the filesystems larger when I reinstall, as I inevitably will. Probably sooner rather than later. The whole point to this installation was to evaluate and learn Linux and BSD OSes. I have started with FreeBSD (in at the deep end -:) and will soon try out some of the Linuxes such as Redhat, Slackware, Mandrake and Gentoo. I will then choose a couple I like and reinstall in a more permanent manner. Thus I will have more space to play with later. So far I really like FreeBSD and plan to stick with it. I'll upgrade to 5.2 next install though. Thanks again, Ron Good luck. - Bob ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /root file system full
On Wed, Mar 03, 2004 at 04:50:32PM -0500, Jerry McAllister wrote: Good Morning, I have recently installed FreeBSD 4.9 and have thoroughly enjoyed my first foray into the BSD world. Indeed my first foray into any non-windows OS. So far I have encountered quite a few problems but have always managed to find an answer in the handbook or by searching through the extensive resources available on the net. Great documentaion! This is the first time I have needed to ask a question. Good. My / filesystem is full. 109%. I want to know what is on the / filesystem, what I can get rid of, how to get rid of it and how to make sure that it doesn't happen again. First, use the program to check usage of a disk. Since it is / that is overfull, log in or su to root cd / du -sk * Then find out which directory trees or files are using up all the space. CD in to those directories and do the same thing until you find some things that seem unexpectedly large or unnecessary. Then you can delete unneeded things. In spite of a pretty good system, upgrades and installs can use up space and leave extra stuff lying around. Some of them clean up after themselves well and some don't do so well. As for the amount of space you need in a / filesystem, I think that the 128 MB is unrealistic. If you have just a base system and stay right on top of it all the time, you can get by with that amount. With disks being so much larget nowdays, I let myself have more, maybe double or so. But, on the machine I am on at the moment, although I have a bigger root, only 43 MB of it is used. I agree, but don't make it to much bigger. There is a better performance include with a small root, since the start of the disk is faster then the end. Having a small root allow a faster boot and faster writes and read to swap file, since this is then closer to the start. I feel 256M would be appropriate. It migth be that less gives problems when you try to update though the make world process. -- Alex Articles based on solutions that I use: http://www.kruijff.org/alex/index.php?dir=docs/FreeBSD/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
/root file system full
Good Morning, I have recently installed FreeBSD 4.9 and have thoroughly enjoyed my first foray into the BSD world. Indeed my first foray into any non-windows OS. So far I have encountered quite a few problems but have always managed to find an answer in the handbook or by searching through the extensive resources available on the net. Great documentaion! This is the first time I have needed to ask a question. My / filesystem is full. 109%. I want to know what is on the / filesystem, what I can get rid of, how to get rid of it and how to make sure that it doesn't happen again. Any thoughts? For background information: The / filesystem is the suggested default of 128mb. The handbook says that root is generally about 40mb of data and that 100mb should be enough to allow for future expansion needs, so 128mb should be adequate. During installation I installed everything, sources, ports, documentation, etc. I have CVSuped source to RELENG_4_9. I have CVSuped ports. I have recompiled the kernel 3 or 4 times. I have redirected the /tmp directory to /usr/tmp (these locations are from memory but you get the idea) I got a bit carried away installing ports during installation (a kid in a candy store?) and currently have about 206 installed. I have been updating ports recently using portupgrade with the recursive switches -rR. At the time the first filesystem full error message was seen I was portupgrading arts -Rr which was upgrading a lot of other ports as well. That process stopped with an error message stating that a conflict between xfmail and qt existed and that qt could not be upgraded untill xfmail was deinstalled so there may be a lot of working data still on the system. Would that be on root? Thanks for your help, Ron Joordens Melbourne, Australia ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /root file system full
On Thu, Mar 04, 2004 at 08:51:56AM +1100, Ron Joordens wrote: Good Morning, I have recently installed FreeBSD 4.9 and have thoroughly enjoyed my first foray into the BSD world. Indeed my first foray into any non-windows OS. So far I have encountered quite a few problems but have always managed to find an answer in the handbook or by searching through the extensive resources available on the net. Great documentaion! This is the first time I have needed to ask a question. My / filesystem is full. 109%. I want to know what is on the / filesystem, what I can get rid of, how to get rid of it and how to make sure that it doesn't happen again. Any thoughts? For background information: The / filesystem is the suggested default of 128mb. The handbook says that root is generally about 40mb of data and that 100mb should be enough to allow for future expansion needs, so 128mb should be adequate. During installation I installed everything, sources, ports, documentation, etc. I have CVSuped source to RELENG_4_9. I have CVSuped ports. I have recompiled the kernel 3 or 4 times. I have redirected the /tmp directory to /usr/tmp (these locations are from memory but you get the idea) I got a bit carried away installing ports during installation (a kid in a candy store?) and currently have about 206 installed. I have been updating ports recently using portupgrade with the recursive switches -rR. At the time the first filesystem full error message was seen I was portupgrading arts -Rr which was upgrading a lot of other ports as well. That process stopped with an error message stating that a conflict between xfmail and qt existed and that qt could not be upgraded untill xfmail was deinstalled so there may be a lot of working data still on the system. Would that be on root? Thanks for your help, Ron Joordens Melbourne, Australia Good Evening ;) 128MB is enough for / if you also set up all of the other partitions correctly. If you showed us a df -h we could more easily see your layout. That said, if this is a hobby system as it sounds like, you may be able to get by with fewer partitions. Personally, on desktop systems, I like to put /usr/home on it's own partition and I just throw everythign else on /. It all depends on what you're using the system for, really. That way, I can totally nuke everything, do a full reinstall from scratch, and still have my user environment how I like it without having to goof around with restoring from backups. Regardless of what you decide to do - a reinstall may be in order (sorry). But, chalk it up to experience. You'll have a much cleaner system the second time around :) hth, dan ___ [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]
Re: /root file system full
Good Morning, I have recently installed FreeBSD 4.9 and have thoroughly enjoyed my first foray into the BSD world. Indeed my first foray into any non-windows OS. So far I have encountered quite a few problems but have always managed to find an answer in the handbook or by searching through the extensive resources available on the net. Great documentaion! This is the first time I have needed to ask a question. Good. My / filesystem is full. 109%. I want to know what is on the / filesystem, what I can get rid of, how to get rid of it and how to make sure that it doesn't happen again. First, use the program to check usage of a disk. Since it is / that is overfull, log in or su to root cd / du -sk * Then find out which directory trees or files are using up all the space. CD in to those directories and do the same thing until you find some things that seem unexpectedly large or unnecessary. Then you can delete unneeded things. In spite of a pretty good system, upgrades and installs can use up space and leave extra stuff lying around. Some of them clean up after themselves well and some don't do so well. As for the amount of space you need in a / filesystem, I think that the 128 MB is unrealistic. If you have just a base system and stay right on top of it all the time, you can get by with that amount. With disks being so much larget nowdays, I let myself have more, maybe double or so. But, on the machine I am on at the moment, although I have a bigger root, only 43 MB of it is used. The next thing is to figure out your whole disk partitioning scheme. Generally I make sure that /var and /usr either are separate file systems or at least that the parts of them such as /var/spool and /var/log and /usr/ports and /usr/src and /usr/local are all moved to some big space and symlinked. Without knowing more about what you have where, it isn't possible to say anything more specific. jerry Any thoughts? For background information: The / filesystem is the suggested default of 128mb. The handbook says that root is generally about 40mb of data and that 100mb should be enough to allow for future expansion needs, so 128mb should be adequate. During installation I installed everything, sources, ports, documentation, etc. I have CVSuped source to RELENG_4_9. I have CVSuped ports. I have recompiled the kernel 3 or 4 times. I have redirected the /tmp directory to /usr/tmp (these locations are from memory but you get the idea) I got a bit carried away installing ports during installation (a kid in a candy store?) and currently have about 206 installed. I have been updating ports recently using portupgrade with the recursive switches -rR. At the time the first filesystem full error message was seen I was portupgrading arts -Rr which was upgrading a lot of other ports as well. That process stopped with an error message stating that a conflict between xfmail and qt existed and that qt could not be upgraded untill xfmail was deinstalled so there may be a lot of working data still on the system. Would that be on root? Thanks for your help, Ron Joordens Melbourne, Australia ___ [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]
Re: /root file system full
On Thu, Mar 04, 2004 at 08:51:56AM +1100, Ron Joordens wrote: My / filesystem is full. 109%. I want to know what is on the / filesystem, what I can get rid of, how to get rid of it and how to make sure that it doesn't happen again. Any thoughts? Check for core files (called 'foo.core' for many different values of foo) -- you can just delete these unless you're going to get into debugging in a serious way. Check the contents of root's home directory, /root -- you should never log into the system as root, especially not via a graphical login. You shouldn't run any interactive command as root unless it's absolutely necessary. If you've got a /root/.kde or a /root/.gnome* or a /root/GNUstep or a /root/.mozilla then delete those directories straight away, and give yourself a good slap on the wrist for being a bad boy. There shouldn't be much stuff in /root at all. There probably shouldn't be any subdirectories of /root, except for the stuff under /root/.ssh To search the root partition for files matching certain conditions, use the find(1) command. The '-xdev' option lets you limit the search to just the one partition. Eg. to find all files modified in the last week: # find / -xdev -mtime -7 -print Or to find all files over 1Mb in size and produce a long-format listing: # find / -xdev -size +1048576c -ls (that only produces a list of 39 files on my machine). Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK pgp0.pgp Description: PGP signature
Re: /root file system full
On Thu, 4 Mar 2004 08:51:56 +1100 Ron Joordens [EMAIL PROTECTED] wrote: + Good Morning, + My / filesystem is full. 109%. I want to know what is on the / filesystem,+ what I can get rid of, how to get rid of it and how to make sure that it+ doesn't happen again. + + Any thoughts? I have some so far. You put in your subject that /root file system is full and in the body of your message you put / is full. These are acutally two different things. Are you using the 'root' account to log in to the system? Are you installing ports for the 'root' user or another system user (for ex: your own personal user id)? [snip] + I got a bit carried away installing ports during installation (a kid in a+ candy store?) and currently have about 206 installed. That isn't bad: ([EMAIL PROTECTED]): pkg_info | wc -l [19:25 :: 004-03-03] 218 Would+ that be on root? Again, this raises red flags to me. You want to make sure you are using a different account than 'root'. You should use su(1) to get to superuser access. Read more about it in the documentation. I could be wrong, I just wanted to clarify. Glad every thing has been going well. // Asenchi ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /root file system full
On Wednesday 03 March 2004 04:51 pm, Ron Joordens Ron Joordens [EMAIL PROTECTED] wrote: Good Morning, [...] My / filesystem is full. 109%. I want to know what is on the / filesystem, what I can get rid of, how to get rid of it and how to make sure that it doesn't happen again. Any thoughts? The / filesystem contains all of the other filesystems, either directly, or as mountpoints where other filesystems are mounted. But filesystems being mounted under / would not cause an error message that says / is full, so your first task is to figure out how things are configured on your system (I don't know what the default configuration is these days, or whether you used the defaults). As someone pointed out already, this information is obtained with the df command. If you can post the output of that will narrow down the possibilities. For background information: The / filesystem is the suggested default of 128mb. The handbook says that root is generally about 40mb of data and that 100mb should be enough to allow for future expansion needs, so 128mb should be adequate. During installation I installed everything, sources, ports, documentation, etc. My experience is that the suggested defaults are enough to get a basic system going, but tend to be a bit tight for a system on which you are going to install a lot of stuff and/or use for a long time. My own rule of thumb is to double all of the defaults, and have at least 3 GB for /usr on a workstation where a lot of miscellaneous programs are likely to be installed. My laptop has 4.6GB in /usr, and it's 90% full (but almost 1 GB of that is stuff I stored there temporarily). When you are first learning FreeBSD (or any *nix), there is something to be said for putting EVERYTHING in one partition (/), and using du to check to see how much /var, /usr, /tmp, /home, etc. are using once in a while. Eventually you will have a good idea of what your real needs are, and around that time you will be ready to clean everything up by wiping the system and doing a fresh install. Of course, you will need to figure out where to temporarily store /home and any important configuration files while you do the new installation. My prefered method is to just buy a new, larger hard drive and keep the old one around as a backup. I have CVSuped source to RELENG_4_9. I have CVSuped ports. I have recompiled the kernel 3 or 4 times. I have redirected the /tmp directory to /usr/tmp (these locations are from memory but you get the idea) I got a bit carried away installing ports during installation (a kid in a candy store?) and currently have about 206 installed. I have been updating ports recently using portupgrade with the recursive switches -rR. At the time the first filesystem full error message was seen I was portupgrading arts -Rr which was upgrading a lot of other ports as well. That process stopped with an error message stating that a conflict between xfmail and qt existed and that qt could not be upgraded untill xfmail was deinstalled so there may be a lot of working data still on the system. Would that be on root? The working files for the most part should be in /usr/ports, although I believe some are also in /tmp (that may be your problem). You should be able to delete the contents of /tmp without harm, particularly if you do it while shut down to single user mode, but /usr/tmp is supposed to persist across reboots and some things may get slightly confused when you delete their temp files. Slight confusion is certainly better than a dead system, though. The timing of the error messages also suggests the possibility that /var is part of / rather than being a separate filesystem, and that either the ports database and/or the log files are eating a large chunk of your space. If that is the case, it might be prudent to consider it a learning experience and start over. If necessary (and assuming that really is the problem), you can resurrect the system by some combination of deleting old logs, uninstalling unneeded ports, moving directories to other partitions and using symlinks (soft links) to make them appear in the right place, and don't forget to go back and delete old kernels you don't need any more if you are saving some of them just in case. Thanks for your help, Ron Joordens Melbourne, Australia Good luck, - Bob ___ [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 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]
File system full?
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 $ -- 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: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]
file system full
Hi, I tried to compile and install new kernel with another option (with VLAN support added).But when I makeinstall the kernel,it said file system is full. How do I need to remove the unneceaarry things and from where so that I can make space to teh new kernel.Is there a place where the system gives what all are there from which I can chosse the things to be removed? Thanks shubha __ Do You Yahoo!? Yahoo! Health - Feel better, live better http://health.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message