Re: /tmp filesystem full
Hi everybody! Thanks for answering my questions and helping me out with this problem. It's been fixed now and I managed to locate the problem with the find / -type d | awk 'length > 900' command. What caused it was something that looked like a directory loop or at least a very deep list of sub directories from two old backups of src + kernel compilations that recently got moved to this server from another one (accidentally and in a hurry due to disk failure on the other server). I think I counted 12 full lines in my terminal window for the directory bash path... I deleted them and now it works great again. Thanks again for great help! Best regards, Andy ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
/tmp filesystem full
Andy Wodfer wodfer at gmail.com Thu Aug 23 09:04:08 UTC 2012 > Can't seem to figure out the problem with MAXPATHLEN. > locate: integer out of +-MAXPATHLEN (1024): 1029 Your database may be corrupted. I would suggest you delete it and recreate. jb ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: /tmp filesystem full
On Thu, 23 Aug 2012 09:54:08 -0400, kpn...@pobox.com wrote:
> On Thu, Aug 23, 2012 at 11:04:02AM +0200, Andy Wodfer wrote:
> > Can't seem to figure out the problem with MAXPATHLEN.
> >
> > locate: integer out of +-MAXPATHLEN (1024): 1029
> >
> >
> > In my /etc/locate.rc I have pruned several directories (even the most
> > obvious) - still the locate DB exeeds well over 1GB before outputting this
> > error message.
> >
> > I have moved the tmp dir for locate to /usr/tmp which works fine (changed
> > in locate script) and there is no problems with diskspace here.
> >
> > the find awk command suggested earlier in this thread didn't give me a
> > better clue about what's happening.
> >
> > Anyone have any other ideas what I can try to find out why locate fails?
>
> I'm starting to wonder if you have a corrupt filesystem. Do you have
> a large number of files or something? My locate database is about three
> megs in size. Granted, I don't have that much data to index.
On my home system, it's 16 GB, but that's still far away from
any gigabyte "barrier"...
> A loop in the filesystem will eventually result in a path that is
> too long. Use fsck to diagnose a corrupt filesystem if you are using
> UFS/UFS2.
Performing a file system check is a good advice, just to make
sure there's not a file system inconsistency that triggers some
abnormal behaviour. Note that _repairing_ a potential defect
should be done in single user mode ("boot -s") on the unmounted
partitions.
> If you don't mind a teeny bit of scripting then you can get close to
> the problem with a find command that runs a short python script:
>
> find / -exec scriptname {} \;
>
> Where scriptname is an executable file with contents something like this:
>
> # /usr/local/bin/python
>
> import sys
>
> for x in sys.argv[1:]:
>if len(x) > 900:# make higher or lower as needed
> sys.stdout.write(x + "\n")
> sys.stdout.flush()
>
> This script takes all command line arguments to it and prints them
> out if the length of the argument exceeds 900 characters. The find
> command I gave above should run this script and give it each
> filename as it comes across it.
In short and which system tools only:
% find / -type d | awk 'length > 900'
And with storing a list for further reference:
% find / -type d | awk 'length > 900' > /tmp/longpaths.txt
Also note that this test only considers path names. In case
you have long _file_ names (or names containing corrupt characters
maybe), that could also be a problem, as the locate command also
records those, if I remember correctly. You can change the "-type d"
to "-type f" to test for file names (_including_ the path).
See "man find" for details.
--
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: /tmp filesystem full
On Wed, 22 Aug 2012 21:24:47 -0700 Michael Sierchio wrote: > On Wed, Aug 22, 2012 at 7:17 PM, RW > wrote: > > > tmpfs and "swap" md devices don't actually need swap. I don't seen > > any advantage in your way of creating an md device for /tmp. > > Then you don't understand. ;-) The advantage of my approach is > avoiding a kernel panic when writing to the tmpfs md device > when you haven't > pre-allocated all the filesystem space at creation time. If that > happens to matter to you... It's the other way around, "malloc" md devices can cause kernel panics. "swap" md device use ordinary VM memory. If you set the limit too high without swap you can slow performance, but it shouldn't cause a kernel panic. The default of 2MB isn't going to make a significant difference on any normal install. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: /tmp filesystem full
Btw, is /etc/locate.rc being read at all? /Andy On Thu, Aug 23, 2012 at 11:04 AM, Andy Wodfer wrote: > Can't seem to figure out the problem with MAXPATHLEN. > > > locate: integer out of +-MAXPATHLEN (1024): 1029 > > > In my /etc/locate.rc I have pruned several directories (even the most > obvious) - still the locate DB exeeds well over 1GB before outputting this > error message. > > I have moved the tmp dir for locate to /usr/tmp which works fine (changed > in locate script) and there is no problems with diskspace here. > > the find awk command suggested earlier in this thread didn't give me a > better clue about what's happening. > > Anyone have any other ideas what I can try to find out why locate fails? > > Thanks! > Andy > > > On Thu, Aug 23, 2012 at 6:24 AM, Michael Sierchio wrote: > >> On Wed, Aug 22, 2012 at 7:17 PM, RW wrote: >> >> > tmpfs and "swap" md devices don't actually need swap. I don't seen any >> > advantage in your way of creating an md device for /tmp. >> >> Then you don't understand. ;-) The advantage of my approach is >> avoiding a kernel panic when writing to the tmpfs when you haven't >> pre-allocated all the filesystem space at creation time. If that >> happens to matter to you... >> ___ >> freebsd-questions@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-questions >> To unsubscribe, send any mail to " >> freebsd-questions-unsubscr...@freebsd.org" >> > > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: /tmp filesystem full
Can't seem to figure out the problem with MAXPATHLEN. locate: integer out of +-MAXPATHLEN (1024): 1029 In my /etc/locate.rc I have pruned several directories (even the most obvious) - still the locate DB exeeds well over 1GB before outputting this error message. I have moved the tmp dir for locate to /usr/tmp which works fine (changed in locate script) and there is no problems with diskspace here. the find awk command suggested earlier in this thread didn't give me a better clue about what's happening. Anyone have any other ideas what I can try to find out why locate fails? Thanks! Andy On Thu, Aug 23, 2012 at 6:24 AM, Michael Sierchio wrote: > On Wed, Aug 22, 2012 at 7:17 PM, RW wrote: > > > tmpfs and "swap" md devices don't actually need swap. I don't seen any > > advantage in your way of creating an md device for /tmp. > > Then you don't understand. ;-) The advantage of my approach is > avoiding a kernel panic when writing to the tmpfs when you haven't > pre-allocated all the filesystem space at creation time. If that > happens to matter to you... > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to " > freebsd-questions-unsubscr...@freebsd.org" > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: /tmp filesystem full
On Wed, Aug 22, 2012 at 7:17 PM, RW wrote: > tmpfs and "swap" md devices don't actually need swap. I don't seen any > advantage in your way of creating an md device for /tmp. Then you don't understand. ;-) The advantage of my approach is avoiding a kernel panic when writing to the tmpfs when you haven't pre-allocated all the filesystem space at creation time. If that happens to matter to you... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: /tmp filesystem full
On Wed, 22 Aug 2012 17:35:29 -0700 Michael Sierchio wrote: > On Wed, Aug 22, 2012 at 3:29 PM, RW > wrote: > > > Sorry I misread the previous post which *was* referring to an md > > device, but the rest is right. > > Not really. ;-) The one compelling reason to use an md filesystem for > /tmp or /var is when you have no swap, and/or your root fs is > read-only tmpfs and "swap" md devices don't actually need swap. I don't seen any advantage in your way of creating an md device for /tmp. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: /tmp filesystem full
On Wed, Aug 22, 2012 at 5:43 PM, Polytropon wrote: > For the mentioned appliances, that would not be a problem. > However there's a distinction between /tmp and /var/tmp > that can be summarized like this: The content of /tmp may > disappear after a reboot (see clear_tmp_enable="YES" in > /etc/rc.conf), whereas /var/tmp is to be preserved during > reboot. Some programs rely on this behavior when putting > "delete-temporary" and "keep-temporary" files into the > respective directories. You are quite right - most of what's in /var is expected to be persistent. In the case where /var/tmp is on a mfs, it's hard to oblige. On these same systems, I do have rc scripts that save parts of /var (those listed in an rc.conf variable) for shutdown, and populate those dirs (after /etc/rc.d/var does its mtree stuff) on start up. - M ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: /tmp filesystem full
On Wed, 22 Aug 2012 17:35:29 -0700, Michael Sierchio wrote: > On Wed, Aug 22, 2012 at 3:29 PM, RW wrote: > > > Sorry I misread the previous post which *was* referring to an md device, > > but the rest is right. > > Not really. ;-) The one compelling reason to use an md filesystem for > /tmp or /var is when you have no swap, and/or your root fs is read > only (or read mostly), as with embedded computers, Soekris boxes > booting from CF, USB stick, or even mSATA (I wouldn't swap on a > partition on an MLC mSATA device). > > In that case, you most certainly want to reserve the space for the > filesystem at creation time. Usually > /tmp -> /var/tmp is that case. For the mentioned appliances, that would not be a problem. However there's a distinction between /tmp and /var/tmp that can be summarized like this: The content of /tmp may disappear after a reboot (see clear_tmp_enable="YES" in /etc/rc.conf), whereas /var/tmp is to be preserved during reboot. Some programs rely on this behavior when putting "delete-temporary" and "keep-temporary" files into the respective directories. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: /tmp filesystem full
On Wed, Aug 22, 2012 at 3:29 PM, RW wrote: > Sorry I misread the previous post which *was* referring to an md device, > but the rest is right. Not really. ;-) The one compelling reason to use an md filesystem for /tmp or /var is when you have no swap, and/or your root fs is read only (or read mostly), as with embedded computers, Soekris boxes booting from CF, USB stick, or even mSATA (I wouldn't swap on a partition on an MLC mSATA device). In that case, you most certainly want to reserve the space for the filesystem at creation time. Usually /tmp -> /var/tmp is that case. - M ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: /tmp filesystem full
On Wed, 22 Aug 2012 23:21:12 +0100 RW wrote: > On Wed, 22 Aug 2012 14:14:17 -0700 > Michael Sierchio wrote: > > > This will happen automatically if you go to multiuser without a > > writeable /tmp. See /etc/rc.d/tmp > > It doesn't, the default is an old-fashioned md device, not tmpfs. Sorry I misread the previous post which *was* referring to an md device, but the rest is right. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: /tmp filesystem full
On Wed, 22 Aug 2012 14:14:17 -0700
Michael Sierchio wrote:
> This will happen automatically if you go to multiuser without a
> writeable /tmp. See /etc/rc.d/tmp
It doesn't, the default is an old-fashioned md device, not tmpfs.
> I have a problem with the semantics of the rc scripts for this and
> var, though - if you are going to use a memory-backed filesystem, you
> should reserve all the space at the outset.
It defaults to 20MB. There's no such thing as an unlimited md-backed
device
> "Bad things" can occur as
> you approach the memory limit (like a kernel panic) otherwise.
Provided that you have swap you can have a /tmp that's much bigger
than memory with either md or tmpfs.
> I'd prefer something like this:
>
> _mdunit=`mdconfig -a -n -t malloc -o reserve -s ${tmpsize}`
It's a bad idea to use a malloc device as it uses wired kernel memory, the
default allows the files to be written out
to swap rather than panic the kernel.
> newfs /dev/md${_mdunit} > /dev/null 2>&1
> mount -o ${tmpmfs_flags} /dev/md${_mdunit} /tmp
>
> But that's just me. mount_md doesn't quite do this.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: /tmp filesystem full
This will happen automatically if you go to multiuser without a
writeable /tmp. See /etc/rc.d/tmp
I have a problem with the semantics of the rc scripts for this and
var, though - if you are going to use a memory-backed filesystem, you
should reserve all the space at the outset. "Bad things" can occur as
you approach the memory limit (like a kernel panic) otherwise.
I'd prefer something like this:
_mdunit=`mdconfig -a -n -t malloc -o reserve -s ${tmpsize}`
newfs /dev/md${_mdunit} > /dev/null 2>&1
mount -o ${tmpmfs_flags} /dev/md${_mdunit} /tmp
But that's just me. mount_md doesn't quite do this.
-M
On Wed, Aug 22, 2012 at 12:48 PM, Sergio de Almeida Lenzi
wrote:
> If you use zfs, that is easy... zfs set quota=NNG pool/tmp
>
> if not
> try to mount tmp in memory...
> in /etc/rc.conf
>
> tmpmfs="YES"
> tmpsize="400m"
>
> reboot
> this would create a /tmp in memory (swap)
> size=400 Megabytes
>
> Sergio
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: /tmp filesystem full
If you use zfs, that is easy... zfs set quota=NNG pool/tmp if not try to mount tmp in memory... in /etc/rc.conf tmpmfs="YES" tmpsize="400m" reboot this would create a /tmp in memory (swap) size=400 Megabytes Sergio ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: /tmp filesystem full
> From owner-freebsd-questi...@freebsd.org Wed Aug 22 08:27:59 2012 > Date: Wed, 22 Aug 2012 14:25:51 +0100 > From: "Steve O'Hara-Smith" > To: freebsd-questions@freebsd.org > Subject: Re: /tmp filesystem full > > On Wed, 22 Aug 2012 08:14:35 -0500 (CDT) > Robert Bonomi wrote: > > > > From owner-freebsd-questi...@freebsd.org Wed Aug 22 05:59:52 2012 > > > Date: Wed, 22 Aug 2012 12:59:13 +0200 > > > From: Andy Wodfer > > > To: freebsd-questions > > > Subject: /tmp filesystem full > > > > > > Hi, > > > I have about 500MB in my /tmp and it seems to be too small when the > > > periodic LOCATE script runs every week. > > > > > > What's the best way to increase the size of /tmp ? Could I simply > > > remove it and create a symbolic link ln -s to say /usr/tmp instead > > > (where I have several hundred GBs free)? > > > > That is a BAD IDEA(tm)! > > > > There are appliations that assume /tmp, /var/tmp, and /usr/tmp are > > _distinct_ directories. They will create files _with_the_same_name_ in > > two of those 'temp' locations, expecting them to be unique.o > > /usr/tmp usually does not exist so creating it and > symlinking /tmp to it is OK. I've used enough different versions of Unix wher '/usr/tmp/ _was_ a standard diretory to be *very* leery. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: /tmp filesystem full
Andy Wodfer wrote at 12:59 +0200 on Aug 22, 2012: > Hi, > I have about 500MB in my /tmp and it seems to be too small when the > periodic LOCATE script runs every week. > > What's the best way to increase the size of /tmp ? Could I simply remove it > and create a symbolic link ln -s to say /usr/tmp instead (where I have > several hundred GBs free)? > > PS! This is on a live server and I would like to keep downtime and > problems to a minimum. :-) One way is to work around your problem is to add 'TMPDIR=/path/to/bigger/filesystem' in /etc/crontab and/or 'export TMPDIR=/path/...' in /etc/periodic.conf. No downtime for that. But yes, you can make /tmp a sym link. You may have to worry about edge cases regarding booting (like if the filesystem you point to is not available early enough at boot time). In the typical case (e.g., locally mounted ufs), it should work fine. There may be very rare cases of software that gets confused by a sym link for /tmp, but certainly the stock periodic scripts should work with it. Depending on what processes have files open on /tmp, you may decide to use some down time to make the sym link. You can't use mv(1) to rename a mounted mount point. If you can umount /tmp, then you can rename it and make the sym link. But it's possible some processes have files open in /tmp preventing a normal umount (see lsof(8), fstat(1)). You would have to convince those processes to close the /tmp file descriptors. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: /tmp filesystem full
On Wed, 22 Aug 2012 08:14:35 -0500 (CDT) Robert Bonomi wrote: > > From owner-freebsd-questi...@freebsd.org Wed Aug 22 05:59:52 2012 > > Date: Wed, 22 Aug 2012 12:59:13 +0200 > > From: Andy Wodfer > > To: freebsd-questions > > Subject: /tmp filesystem full > > > > Hi, > > I have about 500MB in my /tmp and it seems to be too small when the > > periodic LOCATE script runs every week. > > > > What's the best way to increase the size of /tmp ? Could I simply > > remove it and create a symbolic link ln -s to say /usr/tmp instead > > (where I have several hundred GBs free)? > > That is a BAD IDEA(tm)! > > There are appliations that assume /tmp, /var/tmp, and /usr/tmp are > _distinct_ directories. They will create files _with_the_same_name_ in > two of those 'temp' locations, expecting them to be unique.o /usr/tmp usually does not exist so creating it and symlinking /tmp to it is OK. > It _is_ OK to symlink /tmp to 'somewhere else', with the caveat that it > "should" be on the '/' filesystem -- one may need it in single-user mode > befoe other filesystems are mounted. You can 'live dangerously' and > symlink to a dir on a different filesystem and _probably_ not have > problems. A null mount would be a safer way of pushing /tmp onto /usr or indeed any other filesystem - that way when the null mount fails the mount point is still a directory. There's really no point in linking it elsewhere on the same filesystem. -- Steve O'Hara-Smith | Directable Mirror Arrays C:>WIN | A better way to focus the sun The computer obeys and wins.|licences available see You lose and Bill collects. |http://www.sohara.org/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: /tmp filesystem full
On Wed, 22 Aug 2012 14:12:25 +0200, Andy Wodfer wrote: > How can I find which directories break the MAXPATHLEN variable? It's easy to do this with find and awk: % find / -type d | awk 'length > LIMIT' where LIMIT is the numerical value you want to be exceeded (in your case, MAXPATHLEN). You can add "> /tmp/longpaths.txt" to obtain a list file for further reference. > or can I somehow run the periodic script in verbose mode to see the output? You could manually run it. Note that it's output is tailored to "generate mail messages" about success or failure which is then mailed to the system administrator. See /etc/defaults/periodic.conf for various *_verbose variables to make the scripts themselves be more verbose. But I only can see those: daily_clean_tmps_verbose="YES" # Mention files deleted daily_clean_preserve_verbose="YES" # Mention files deleted daily_clean_rwho_verbose="YES" # Mention files deleted You could however (temporarily) add your own debugging statements to the script in question. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: /tmp filesystem full
> From owner-freebsd-questi...@freebsd.org Wed Aug 22 05:59:52 2012 > Date: Wed, 22 Aug 2012 12:59:13 +0200 > From: Andy Wodfer > To: freebsd-questions > Subject: /tmp filesystem full > > Hi, > I have about 500MB in my /tmp and it seems to be too small when the > periodic LOCATE script runs every week. > > What's the best way to increase the size of /tmp ? Could I simply remove it > and create a symbolic link ln -s to say /usr/tmp instead (where I have > several hundred GBs free)? That is a BAD IDEA(tm)! There are appliations that assume /tmp, /var/tmp, and /usr/tmp are _distinct_ directories. They will create files _with_the_same_name_ in two of those 'temp' locations, expecting them to be unique.o It _is_ OK to symlink /tmp to 'somewhere else', with the caveat that it "should" be on the '/' filesystem -- one may need it in single-user mode befoe other filesystems are mounted. You can 'live dangerously' and symlink to a dir on a different filesystem and _probably_ not have problems. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: /tmp filesystem full
On Wed, 22 Aug 2012 12:59:13 +0200, Andy Wodfer wrote: Hi, I have about 500MB in my /tmp and it seems to be too small when the periodic LOCATE script runs every week. What's the best way to increase the size of /tmp ? Could I simply remove it and create a symbolic link ln -s to say /usr/tmp instead (where I have several hundred GBs free)? PS! This is on a live server and I would like to keep downtime and problems to a minimum. :-) Cheers, Andy If it's just locate.updatedb filling it up temporarily, perhaps you can solve this by ommitting part of your filesystem from the locate index. See /etc/locate.rc Regards, Michael ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: /tmp filesystem full
Le 22/08/2012 12:59, Andy Wodfer a écrit : Hi, I have about 500MB in my /tmp and it seems to be too small when the periodic LOCATE script runs every week. What's the best way to increase the size of /tmp ? Could I simply remove it and create a symbolic link ln -s to say /usr/tmp instead (where I have several hundred GBs free)? PS! This is on a live server and I would like to keep downtime and problems to a minimum. :-) Cheers, Andy ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" Removing /tmp and replacing it with a link is a bad idea, it might have unexpected effects if you have to go into single user mode for maintenance - especially if /usr cannot be mounted at that time. A solution would be to create a /usr/tmp BEFORE mounting /usr If the problem comes from locate, the best option is to move locate database and temp files on another drive - take a look at locate.rc for information - this should cause 0 downtime. If the problem is that the tmp file is really too small for a number of operation including locate (for example compile also fails due to lack of space) you will need to either configure each and every failing program to use a different temp directory or move temp directory ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: /tmp filesystem full
How can I find which directories break the MAXPATHLEN variable? or can I somehow run the periodic script in verbose mode to see the output? /Andy On Wed, Aug 22, 2012 at 2:04 PM, Andy Wodfer wrote: > Thanks to all for your input! > > Editing /etc/periodic.rc seem to do the trick, but now I faced a different > problem which I've never seen before: > > locate: integer out of +-MAXPATHLEN (1024): 1029 > > > There are some directories that contains A LOT of small files I think. > Need to investigate. > > Also thanks for the tip on omitting parts of the filesystem. Perhaps I > need to do that. > > /Andy > > > > On Wed, Aug 22, 2012 at 1:56 PM, Michael Ross wrote: > >> On Wed, 22 Aug 2012 12:59:13 +0200, Andy Wodfer wrote: >> >> Hi, >>> I have about 500MB in my /tmp and it seems to be too small when the >>> periodic LOCATE script runs every week. >>> >>> What's the best way to increase the size of /tmp ? Could I simply remove >>> it >>> and create a symbolic link ln -s to say /usr/tmp instead (where I have >>> several hundred GBs free)? >>> >>> PS! This is on a live server and I would like to keep downtime and >>> problems >>> to a minimum. :-) >>> >>> Cheers, >>> Andy >>> >> >> If it's just locate.updatedb filling it up temporarily, >> perhaps you can solve this by ommitting part of your filesystem from the >> locate index. >> >> See /etc/locate.rc >> >> >> Regards, >> >> Michael >> > > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: /tmp filesystem full
Thanks to all for your input! Editing /etc/periodic.rc seem to do the trick, but now I faced a different problem which I've never seen before: locate: integer out of +-MAXPATHLEN (1024): 1029 There are some directories that contains A LOT of small files I think. Need to investigate. Also thanks for the tip on omitting parts of the filesystem. Perhaps I need to do that. /Andreas On Wed, Aug 22, 2012 at 1:56 PM, Michael Ross wrote: > On Wed, 22 Aug 2012 12:59:13 +0200, Andy Wodfer wrote: > > Hi, >> I have about 500MB in my /tmp and it seems to be too small when the >> periodic LOCATE script runs every week. >> >> What's the best way to increase the size of /tmp ? Could I simply remove >> it >> and create a symbolic link ln -s to say /usr/tmp instead (where I have >> several hundred GBs free)? >> >> PS! This is on a live server and I would like to keep downtime and >> problems >> to a minimum. :-) >> >> Cheers, >> Andy >> > > If it's just locate.updatedb filling it up temporarily, > perhaps you can solve this by ommitting part of your filesystem from the > locate index. > > See /etc/locate.rc > > > Regards, > > Michael > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: /tmp filesystem full
El día Wednesday, August 22, 2012 a las 12:59:13PM +0200, Andy Wodfer escribió: > Hi, > I have about 500MB in my /tmp and it seems to be too small when the > periodic LOCATE script runs every week. > > What's the best way to increase the size of /tmp ? Could I simply remove it > and create a symbolic link ln -s to say /usr/tmp instead (where I have > several hundred GBs free)? > > PS! This is on a live server and I would like to keep downtime and problems > to a minimum. :-) Hi, See the script /usr/sbin/periodic, it supports TMPDIR env var and you could direct this to some place with more space; HIH matthias -- Matthias Apitz e - w http://www.unixarea.de/ UNIX since V7 on PDP-11, UNIX on mainframe since ESER 1055 (IBM /370) UNIX on x86 since SVR4.2 UnixWare 2.1.2, FreeBSD since 2.2.5 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: /tmp filesystem full
RW writes: > > I have about 500MB in my /tmp and it seems to be too small when the > > periodic LOCATE script runs every week. > > There's also a periodic script to remove older files from /tmp which > may help. My gut reaction is: what's taking up so much room? My /tmp contains 6 mbytes. Even back when it was sharing space on a 500 mbyte /, it only filled up on the rare occasions when something went Horribly Wrong(tm) with a large compilation or backup. To the OP: See what you can delete. Then figure out what's filling it up. Respoectfully, Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: /tmp filesystem full
On Wed, 22 Aug 2012 12:59:13 +0200 Andy Wodfer wrote: > Hi, > I have about 500MB in my /tmp and it seems to be too small when the > periodic LOCATE script runs every week. > > What's the best way to increase the size of /tmp ? Could I simply > remove it and create a symbolic link ln -s to say /usr/tmp instead > (where I have several hundred GBs free)? > Either that or you could use tmpfs. You could also change the locate tmp directory in /etc/locate.rc. There's also a periodic script to remove older files from /tmp which may help. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: /tmp filesystem full
Hi, On Wed, 22 Aug 2012 12:59:13 +0200 Andy Wodfer wrote: > Hi, > I have about 500MB in my /tmp and it seems to be too small when the > periodic LOCATE script runs every week. > > What's the best way to increase the size of /tmp ? Could I simply > remove it and create a symbolic link ln -s to say /usr/tmp instead > (where I have several hundred GBs free)? > > PS! This is on a live server and I would like to keep downtime and > problems to a minimum. :-) > downtime will be kept to a minimum with this method. Can't you put another drive into this machine? Erich ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
/tmp filesystem full
Hi, I have about 500MB in my /tmp and it seems to be too small when the periodic LOCATE script runs every week. What's the best way to increase the size of /tmp ? Could I simply remove it and create a symbolic link ln -s to say /usr/tmp instead (where I have several hundred GBs free)? PS! This is on a live server and I would like to keep downtime and problems to a minimum. :-) Cheers, Andy ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
mutt-devel freezes with "filesystem full", ends up in wdrain cpu state
On ia64 8.0-beta1 SMP mutt-devel-1.5.20_1 freezes on some folders with /tmp: write failed, filesystem is full Could not copy message top shows that mutt is in "wdrain" state and in /var/log/messages I see kernel: pid 43702 (mutt), uid 1001 inumber 23554 on /tmp: filesystem full /tmp has lots of free space Anybody else is seeing this? What could be the problem? -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 928 8233 Fax: +44 (0)117 929 4423 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: How to recover disk space after "filesystem full"
On Fri, 22 May 2009, Steve Bertrand wrote: Luke Dean wrote: I ended up rebooting the box. Was there any other possible solution I could've tried? You have to restart the service that was holding the log file(s) open. The system does not release the space while an application is 'using' the file, even after it's been deleted. Oh yeah! I forgot. I've got it configured to use syslogd to handle the dhcp logging, so I probably just needed to restart that one. I probably could've left dhcpd running. This kind of emergency always seems to happen before I get a chance to make coffee. Thank you. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: How to recover disk space after "filesystem full"
On Friday 22 May 2009 18:19:25 Steve Bertrand wrote: > # pkg_add -r lsof Or use the native fstat(1). -- Mel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: How to recover disk space after "filesystem full"
On Fri, May 22, 2009 at 9:14 AM, Luke Dean wrote: > > Yes, it sounds like a stupid question, but let me tell the story. > > The log for my dhcp server filled up /var last night, which meant that > dhcpd was also unable to hand out new leases, which meant that I had > effectively been DOSed. I'll have to look into changing my logging > policies. > > So, to correct the problem, I log into the router, removed the big > log and several other files in /var to free up some space, and assumed > this would correct the problem. > > It did not. > Several minutes after freeing up a lot of space on /var, I continued > to get "filesystem full" messages and "df" continued to show the > capacity at >100%. I checked "df -i" for the inodes too. That was > fine. I ran a quick fsck to see if that might shock the system into > seeing all the space that I'd freed up, but no good. > > I ended up rebooting the box. > > Was there any other possible solution I could've tried? > > Why wouldn't the free space immediately appear as free? Because unlinking the file does not close the file. Restarting the dhcp daemon probably would have done the trick. The filesystem will free the disk space only when all references to the file have gone away. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: How to recover disk space after "filesystem full"
Luke Dean writes: > Yes, it sounds like a stupid question, but let me tell the story. > > The log for my dhcp server filled up /var last night, which meant that > dhcpd was also unable to hand out new leases, which meant that I had > effectively been DOSed. I'll have to look into changing my logging > policies. > > So, to correct the problem, I log into the router, removed the big > log and several other files in /var to free up some space, and assumed > this would correct the problem. > > It did not. > Several minutes after freeing up a lot of space on /var, I continued > to get "filesystem full" messages and "df" continued to show the > capacity at >100%. I checked "df -i" for the inodes too. That was > fine. I ran a quick fsck to see if that might shock the system into > seeing all the space that I'd freed up, but no good. > > I ended up rebooting the box. > > Was there any other possible solution I could've tried? > > Why wouldn't the free space immediately appear as free? http://www.freebsd.org/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 "freebsd-questions-unsubscr...@freebsd.org"
Re: How to recover disk space after "filesystem full"
Luke Dean wrote: > > Yes, it sounds like a stupid question, but let me tell the story. > > The log for my dhcp server filled up /var last night, which meant that > dhcpd was also unable to hand out new leases, which meant that I had > effectively been DOSed. I'll have to look into changing my logging > policies. > > So, to correct the problem, I log into the router, removed the big > log and several other files in /var to free up some space, and assumed > this would correct the problem. > > It did not. > Several minutes after freeing up a lot of space on /var, I continued > to get "filesystem full" messages and "df" continued to show the > capacity at >100%. I checked "df -i" for the inodes too. That was > fine. I ran a quick fsck to see if that might shock the system into > seeing all the space that I'd freed up, but no good. > > I ended up rebooting the box. > > Was there any other possible solution I could've tried? You have to restart the service that was holding the log file(s) open. The system does not release the space while an application is 'using' the file, even after it's been deleted. > Why wouldn't the free space immediately appear as free? Because technically, the space is not freed. "lsof" will help identify which process(es) are holding a particular file open, if you see that disk space is not recovered as expected after deletion: # pkg_add -r lsof pearl# lsof | grep auth.log syslogd 850 root 15wVREG 0,127 75199 237484 /var/log/auth.log Steve smime.p7s Description: S/MIME Cryptographic Signature
How to recover disk space after "filesystem full"
Yes, it sounds like a stupid question, but let me tell the story. The log for my dhcp server filled up /var last night, which meant that dhcpd was also unable to hand out new leases, which meant that I had effectively been DOSed. I'll have to look into changing my logging policies. So, to correct the problem, I log into the router, removed the big log and several other files in /var to free up some space, and assumed this would correct the problem. It did not. Several minutes after freeing up a lot of space on /var, I continued to get "filesystem full" messages and "df" continued to show the capacity at >100%. I checked "df -i" for the inodes too. That was fine. I ran a quick fsck to see if that might shock the system into seeing all the space that I'd freed up, but no good. I ended up rebooting the box. Was there any other possible solution I could've tried? Why wouldn't the free space immediately appear as free? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Help! locate.code /tmp: filesystem full
On Thu, 22 Jan 2009 10:24:39 -0900, Mel wrote: > In short: reboot in single user mode, then run fsck -y at the prompt. > > Never ever run fsck -y on a live filesystem. A very good hint. Didn't I mention it? No? Bad idea. Background concept: The fsck utility does changes to the file system when repairing it, and the kind of these changes implies that the file system is not mounted, so there's no unexpected interruption by maybe a write operation from a program. That's what downtime is good for - letting fsck doing its job well. -- Polytropon >From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Help! locate.code /tmp: filesystem full
On Thursday 15 January 2009 13:37:06 Polytropon wrote: > On Thu, 15 Jan 2009 21:37:24 +0100, "Andy Wodfer" wrote: Added context: > > Here's the output of fsck (this was a new command to me): > > > > # fsck > > ** /dev/ar0s1a (NO WRITE) > > Should I run fsck -y? Is it safe to do so? > > At least, fsck will do its best to repair the defective file system. > As you have seen from the messages, you will surely lose some files > when their information gets cleared. If you use -y, fsck is allowed > to do anything it considers neccessary doing. fsck on a live filesystem (hint: NO WRITE) is a bad idea. Doing an fsck that is supposed to repair stuff, always requires downtime, unless you use background_fsck. However, many people discourage it's usage as it can leave some errors unfixed. In short: reboot in single user mode, then run fsck -y at the prompt. Never ever run fsck -y on a live filesystem. -- Mel Problem with today's modular software: they start with the modules and never get to the software part. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Help! locate.code /tmp: filesystem full
On Thu, 15 Jan 2009 21:37:24 +0100, "Andy Wodfer" wrote: > Should I run fsck -y? Is it safe to do so? At least, fsck will do its best to repair the defective file system. As you have seen from the messages, you will surely lose some files when their information gets cleared. If you use -y, fsck is allowed to do anything it considers neccessary doing. You could use fsck in preen mode (-p) to have less defects corrected. If it's possible, try to backup all important data. If fsck deletes something, you could restore it afterwards. Your goal should be to get your file system into a consistent state again. Worse kinds of data loss can follow. It hurts, I know it... :-( -- Polytropon >From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Help! locate.code /tmp: filesystem full
On Wed, Jan 14, 2009 at 7:34 PM, Andy Wodfer wrote: > Hi, > I'm getting an error message every week and I can't seem to understand why > nor manage to fix it. Here it is: > > #dmesg > [snip] > pid 54753 (locate.code), uid 65534 inumber 23557 on /tmp: filesystem full > > # df -h > Filesystem SizeUsed Avail Capacity Mounted on > /dev/ar0s1a989M 53M857M 6%/ > devfs 1.0K1.0K 0B 100%/dev > /dev/ar0s1g 48G8.5G 36G19%/backup > /dev/ar0s1d989M 44K910M 0%/tmp > /dev/ar0s1f387G168G189G47%/usr > /dev/ar0s1e7.7G398M6.7G 5%/var > > As you see there's 910MB free space in /tmp. Should be plenty to run the > weekly locate script? > > # uname -a > FreeBSD host.domain.com 6.3-PRERELEASE FreeBSD 6.3-PRERELEASE #5: Sat Jan > 12 03:20:02 CET 2008 r...@host.domain.com:/usr/obj/usr/src/sys/MYOWN > i386 > > Does anyone have a suggestion what I can do to fix this problem? > > Thanks a lot! > > Best, > Andy > Here's the output of fsck (this was a new command to me): # fsck ** /dev/ar0s1a (NO WRITE) ** Last Mounted on / ** Root file system ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups 1565 files, 27379 used, 479108 free (1204 frags, 59738 blocks, 0.2% fragmentation) ** /dev/ar0s1g (NO WRITE) ** Last Mounted on /backup ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups 873 files, 4467162 used, 20921355 free (891 frags, 2615058 blocks, 0.0% fragmentation) ** /dev/ar0s1d (NO WRITE) ** Last Mounted on /tmp ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups 119 files, 67 used, 506420 free (28 frags, 63299 blocks, 0.0% fragmentation) ** /dev/ar0s1f (NO WRITE) ** Last Mounted on /usr ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames UNALLOCATED I=7961594 OWNER=www MODE=100620 SIZE=69292 MTIME=Jan 15 21:06 2009 FILE=/local/www/[removed]/data/scripts/forum/cache/sql_021151d1a377d62dbfaa89a4d1acc716.php UNEXPECTED SOFT UPDATE INCONSISTENCY REMOVE? no UNALLOCATED I=7961584 OWNER=www MODE=100620 SIZE=4784 MTIME=Jan 15 21:06 2009 FILE=/local/www/[removed]/data/scripts/forum/cache/data_search_results_c34cf621be1e424bde185cb6b71bf55f.php UNEXPECTED SOFT UPDATE INCONSISTENCY REMOVE? no UNALLOCATED I=7961588 OWNER=www MODE=100620 SIZE=317 MTIME=Jan 15 21:06 2009 FILE=/local/www/[removed]/data/scripts/forum/cache/sql_de3e82ec3f05e04f8caecf9cecb70fe5.php UNEXPECTED SOFT UPDATE INCONSISTENCY REMOVE? no UNALLOCATED I=7961590 OWNER=www MODE=100620 SIZE=343 MTIME=Jan 15 21:06 2009 FILE=/local/www/[removed]/data/scripts/forum/cache/sql_45386e120e999630d18124e757c15cd5.php UNEXPECTED SOFT UPDATE INCONSISTENCY REMOVE? no UNALLOCATED I=7961593 OWNER=www MODE=100620 SIZE=155 MTIME=Jan 15 21:06 2009 FILE=/local/www/[removed]/data/scripts/forum/cache/data_search_results_a770f781f984926682ad24b828d1568c.php UNEXPECTED SOFT UPDATE INCONSISTENCY REMOVE? no UNALLOCATED I=7961595 OWNER=www MODE=100620 SIZE=317 MTIME=Jan 15 21:07 2009 FILE=/local/www/[removed]/data/scripts/forum/cache/sql_f60c9f27d5a394bc6e9a70185d29ccf2.php UNEXPECTED SOFT UPDATE INCONSISTENCY REMOVE? no UNALLOCATED I=7961597 OWNER=www MODE=100620 SIZE=223 MTIME=Jan 15 21:07 2009 FILE=/local/www/[removed]/data/scripts/forum/cache/data_search_results_99f04705815fd4978b0d47911d8b44ad.php UNEXPECTED SOFT UPDATE INCONSISTENCY REMOVE? no UNALLOCATED I=7961599 OWNER=www MODE=100620 SIZE=343 MTIME=Jan 15 21:08 2009 FILE=/local/www/[removed]/data/scripts/forum/cache/sql_46c003bc334cf0386554f73d8bb37688.php UNEXPECTED SOFT UPDATE INCONSISTENCY REMOVE? no UNALLOCATED I=7961600 OWNER=www MODE=100620 SIZE=343 MTIME=Jan 15 21:09 2009 FILE=/local/www/[removed]/data/scripts/forum/cache/sql_0c5aeb430c03186f1c1cd9c56cd3320c.php UNEXPECTED SOFT UPDATE INCONSISTENCY REMOVE? no UNALLOCATED I=7961601 OWNER=www MODE=100620 SIZE=317 MTIME=Jan 15 21:09 2009 FILE=/local/www/[removed]/data/scripts/forum/cache/sql_1bbabc64d41b06401b3f49122429cfb8.php UNEXPECTED SOFT UPDATE INCONSISTENCY REMOVE? no UNALLOCATED I=7961602 OWNER=www MODE=100620 SIZE=241 MTIME=Jan 15 21:09 2009 FILE=/local/www/[removed]/data/scripts/forum/cache/data_search_results_708ac649d78e7e8f4912da48dbb2f0d3.php UNEXPECTED SOFT UPDATE INCONSISTENCY REMOVE? no UNALLOCATED I=10086553 OWNER=www MODE=100660 SIZE=5572 MTIME=Jan 15 21:09 2009 FILE=/local/www/[removed]/data/scripts/forum/images/avatars/upload/f3bd348b1ce8f9503d1d63b34905349d_3218.jpg UNEXPECTED SOFT UPDATE INCONSISTENCY REMOVE? no *
Re: Help! locate.code /tmp: filesystem full
On Wed, Jan 14, 2009 at 8:27 PM, Glen Barber wrote: > On Wed, Jan 14, 2009 at 1:34 PM, Andy Wodfer wrote: > > Hi, > > I'm getting an error message every week and I can't seem to understand > why > > nor manage to fix it. Here it is: > > > > [snip] > > > > > # df -h > > Filesystem SizeUsed Avail Capacity Mounted on > > /dev/ar0s1a989M 53M857M 6%/ > > devfs 1.0K1.0K 0B 100%/dev > > /dev/ar0s1g 48G8.5G 36G19%/backup > > /dev/ar0s1d989M 44K910M 0%/tmp > > /dev/ar0s1f387G168G189G47%/usr > > /dev/ar0s1e7.7G398M6.7G 5%/var > > > > As you see there's 910MB free space in /tmp. Should be plenty to run the > > weekly locate script? > > > > Have you recently had disk failures? When was your last `fsck' ? > > What is the output of `du -h /tmp' ? > > To rule out if 910M is not enough, you could `mv' /tmp to /tmp.bak and > do a hard link pointing a new /tmp somewhere with more space, for > example /usr/faketmp. > > I don't know how this will affect fstab or mount, however. Thanks for your replies. The requested outputs are: # df -i /tmp Filesystem 1K-blocks Used Avail Capacity iused ifree %iused Mounted on /dev/ar0s1d 1012974 134 931804 0% 119 1411910% /tmp # du -h /tmp 2.0K/tmp/.snap 2.0K/tmp/.XIM-unix 2.0K/tmp/ssh-fc3AdQjUmT 2.0K/tmp/.X11-unix 2.0K/tmp/.ICE-unix 2.0K/tmp/.font-unix 134K/tmp I have never done a fsck. Didn't really know of this command. I'm running it now and will post the result when it's finished. I have had one diskproblem a few months ago. This was the output of that: ad6: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly ad6: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly ad6: WARNING - SETFEATURES ENABLE RCACHE taskqueue timeout - completing request directly ad6: WARNING - SETFEATURES ENABLE WCACHE taskqueue timeout - completing request directly ad6: WARNING - SET_MULTI taskqueue timeout - completing request directly ad6: TIMEOUT - READ_DMA retrying (1 retry left) LBA=52327168 ad6: FAILURE - SMART status=51 error=4 ad4: FAILURE - SMART status=51 error=4 ad8: FAILURE - SMART status=51 error=4 Haven't had any trouble since and the server is still running on the same disks and with the same RAID setup. The server has been up for almost 200 days now. Ofcoure I'm worried that one or more disks are having trouble. Look forward to your replies. Thanks! Andy ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Help! locate.code /tmp: filesystem full
On 01/14/2009 10:34 AM, Andy Wodfer wrote: > Hi, > I'm getting an error message every week and I can't seem to understand why > nor manage to fix it. Here it is: > > #dmesg > [snip] > pid 54753 (locate.code), uid 65534 inumber 23557 on /tmp: filesystem full > > # df -h > Filesystem SizeUsed Avail Capacity Mounted on > /dev/ar0s1a989M 53M857M 6%/ > devfs 1.0K1.0K 0B 100%/dev > /dev/ar0s1g 48G8.5G 36G19%/backup > /dev/ar0s1d989M 44K910M 0%/tmp > /dev/ar0s1f387G168G189G47%/usr > /dev/ar0s1e7.7G398M6.7G 5%/var > > As you see there's 910MB free space in /tmp. Should be plenty to run the > weekly locate script? [...] What is the output of 'df -i /tmp'? -- Benjamin Lee http://www.b1c1l1.com/ signature.asc Description: OpenPGP digital signature
Re: Help! locate.code /tmp: filesystem full
On Wed, Jan 14, 2009 at 1:34 PM, Andy Wodfer wrote: > Hi, > I'm getting an error message every week and I can't seem to understand why > nor manage to fix it. Here it is: > [snip] > > # df -h > Filesystem SizeUsed Avail Capacity Mounted on > /dev/ar0s1a989M 53M857M 6%/ > devfs 1.0K1.0K 0B 100%/dev > /dev/ar0s1g 48G8.5G 36G19%/backup > /dev/ar0s1d989M 44K910M 0%/tmp > /dev/ar0s1f387G168G189G47%/usr > /dev/ar0s1e7.7G398M6.7G 5%/var > > As you see there's 910MB free space in /tmp. Should be plenty to run the > weekly locate script? > Have you recently had disk failures? When was your last `fsck' ? What is the output of `du -h /tmp' ? To rule out if 910M is not enough, you could `mv' /tmp to /tmp.bak and do a hard link pointing a new /tmp somewhere with more space, for example /usr/faketmp. I don't know how this will affect fstab or mount, however. -- Glen Barber ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Help! locate.code /tmp: filesystem full
Hi, I'm getting an error message every week and I can't seem to understand why nor manage to fix it. Here it is: #dmesg [snip] pid 54753 (locate.code), uid 65534 inumber 23557 on /tmp: filesystem full # df -h Filesystem SizeUsed Avail Capacity Mounted on /dev/ar0s1a989M 53M857M 6%/ devfs 1.0K1.0K 0B 100%/dev /dev/ar0s1g 48G8.5G 36G19%/backup /dev/ar0s1d989M 44K910M 0%/tmp /dev/ar0s1f387G168G189G47%/usr /dev/ar0s1e7.7G398M6.7G 5%/var As you see there's 910MB free space in /tmp. Should be plenty to run the weekly locate script? # uname -a FreeBSD host.domain.com 6.3-PRERELEASE FreeBSD 6.3-PRERELEASE #5: Sat Jan 12 03:20:02 CET 2008 r...@host.domain.com:/usr/obj/usr/src/sys/MYOWN i386 Does anyone have a suggestion what I can do to fix this problem? Thanks a lot! Best, Andy ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: FreeBSD 5.4 - filesystem full
On Thu, Nov 13, 2008 at 02:05:28PM +0300, Varshavchick Alexander wrote: >> Booting into single-user via serial console, KVM, KVM-over-IP, or >> iLO/LOM (if HP/Compaq) is sufficient. If you have servers which are >> remote and you lack any of these features, I'm both surprised and not >> sure what to tell you. You'll encounter this problem with any OS, not >> just FreeBSD. > > I'm looking for something similar to /forcefsck file on the linux > systems. Ideally this should be handled either nextboot(8), via a special flag passed to boot(8). However, I see no such capability in the man pages, so you might be out of luck. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD 5.4 - filesystem full
Booting into single-user via serial console, KVM, KVM-over-IP, or iLO/LOM (if HP/Compaq) is sufficient. If you have servers which are remote and you lack any of these features, I'm both surprised and not sure what to tell you. You'll encounter this problem with any OS, not just FreeBSD. I'm looking for something similar to /forcefsck file on the linux systems. Alexander Varshavchick, Metrocom Joint Stock Company Phone: (812)718-3322, 718-3115(fax) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD 5.4 - filesystem full
On Wed, 12 Nov 2008, Adrian Penisoara wrote: What kind of applications are you running on the machine ? Are they mmap'ing files on the filesystem in quesiton (which one ?) ? mainly apache, sphinx's search daemon and several perl scripts AFAIR even if you delete a big file the disk space may not be reclaimed if a process still has the file open. but even if you run df -ki in the exact moment of when the filesystem full messages are appearing in the logs, it reports of having 40G free and a lot of free inodes. If you reboot the machine or restart some of the applications, does the issue disappear ? after rebooting during several days the issue doesn't arise, then it repeats again. Alexander Varshavchick, Metrocom Joint Stock Company Phone: (812)718-3322, 718-3115(fax) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD 5.4 - filesystem full
Le Wednesday 12 November 2008, Varshavchick Alexander a écrit : > I have an old enough server with FreeBSD 5.4 which from time to time > complains about filesystem full. But the problem is that the partition > in question has about 15G free space and more than 1000 free inodes. > Then all by itself the error dissapears, only to be repeated several hours > later. What can it be and where to look? The server runs mainly apache and > sendmail, nothing special. Hello, I saw a full disk because of a runaway background fsck : bg_fsck built some image of the disk in the top-level ".snap" directory, which grew and grew and grew the workaround was to reboot in single-user, then fsck in foreground, and finally switch to Zfs (but obviously, only for a Releng7 machine) TfH > > Thanks and regards > > > Alexander Varshavchick, Metrocom Joint Stock Company > Phone: (812)718-3322, 718-3115(fax) > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > 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: FreeBSD 5.4 - filesystem full
Hi, What kind of applications are you running on the machine ? Are they mmap'ing files on the filesystem in quesiton (which one ?) ? AFAIR even if you delete a big file the disk space may not be reclaimed if a process still has the file open. If you reboot the machine or restart some of the applications, does the issue disappear ? Regards, Adrian. On Wed, Nov 12, 2008 at 1:05 PM, Varshavchick Alexander <[EMAIL PROTECTED]> wrote: > I have an old enough server with FreeBSD 5.4 which from time to time > complains about filesystem full. But the problem is that the partition in > question has about 15G free space and more than 1000 free inodes. Then > all by itself the error dissapears, only to be repeated several hours later. > What can it be and where to look? The server runs mainly apache and > sendmail, nothing special. > > Thanks and regards > > > Alexander Varshavchick, Metrocom Joint Stock Company > Phone: (812)718-3322, 718-3115(fax) > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > 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: FreeBSD 5.4 - filesystem full
On Wed, Nov 12, 2008 at 03:34:11PM +0300, Varshavchick Alexander wrote: > I have an old enough server with FreeBSD 5.4 which from time to time > complains about filesystem full. But the problem is that the partition in > question has about 15G free space and more than 1000 free inodes. Then > all by itself the error dissapears, only to be repeated several hours > later. What can it be and where to look? The server runs mainly apache and > sendmail, nothing special. There is a FAQ, numerous questions threads and several articles in online publications on this issue. I am sure you can easily find them with some basic searching. Most of the problems/confusions come from two places. The first is that an amount - normally 8% - is held out for root. The second is processes that open/create a file to write and then delink it but do not release it and continue to write to it. It doesn't show up, but is still taking space. The processes do this so if they get killed, the space is automatically released. jerry > > Thanks and regards > > > > Alexander Varshavchick, Metrocom Joint Stock Company > Phone: (812)718-3322, 718-3115(fax) > ___ > 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: FreeBSD 5.4 - filesystem full
Varshavchick Alexander wrote: > > I have an old enough server with FreeBSD 5.4 which from time to time > complains about filesystem full. But the problem is that the partition > in question has about 15G free space and more than 1000 free inodes. > Then all by itself the error dissapears, only to be repeated several hours > later. What can it be and where to look? The server runs mainly apache and > sendmail, nothing special. I vaguely remember that there was an issue with softupdates that didn't report blocks as free until the filesystem was synced, and with intense disk activity the filesystem was not syncing by itself often enough. -SB ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD 5.4 - filesystem full
On Wed, Nov 12, 2008 at 05:26:58PM +0300, Varshavchick Alexander wrote: >> I would start by taking the machine down, booting it into single-user, >> and running fsck -y. background fsck does not catch all errors. > > Okay then, are there any ways of performing it remotely, without my going > to the data center and standing near the server for an hour while it > checks? I mean are there any civil ways, or only running reboot -qn and > praying? :) Booting into single-user via serial console, KVM, KVM-over-IP, or iLO/LOM (if HP/Compaq) is sufficient. If you have servers which are remote and you lack any of these features, I'm both surprised and not sure what to tell you. You'll encounter this problem with any OS, not just FreeBSD. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD 5.4 - filesystem full
I would start by taking the machine down, booting it into single-user, and running fsck -y. background fsck does not catch all errors. Okay then, are there any ways of performing it remotely, without my going to the data center and standing near the server for an hour while it checks? I mean are there any civil ways, or only running reboot -qn and praying? :) Alexander Varshavchick, Metrocom Joint Stock Company Phone: (812)718-3322, 718-3115(fax) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD 5.4 - filesystem full
On Wed, 12 Nov 2008, Jeremy Chadwick wrote: I would start by taking the machine down, booting it into single-user, and running fsck -y. background fsck does not catch all errors. Background fsck has been turned off from the beginning, and a couple of weeks ago when there was a power break, full fsck -y was done all the same. But you're right, running fsck -y once again will not harm. Also, how soon do you check the box to see how much space/free inodes it has after receiving a "filesystem full" error? Are we talking "I checked it 4-5 hours later", or "I checked it 30 seconds after"? I checked it several minutes after. Alexander Varshavchick, Metrocom Joint Stock Company Phone: (812)718-3322, 718-3115(fax) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD 5.4 - filesystem full
On Wed, Nov 12, 2008 at 03:34:11PM +0300, Varshavchick Alexander wrote: > I have an old enough server with FreeBSD 5.4 which from time to time > complains about filesystem full. But the problem is that the partition in > question has about 15G free space and more than 1000 free inodes. > Then all by itself the error dissapears, only to be repeated several > hours later. What can it be and where to look? The server runs mainly > apache and sendmail, nothing special. I'm not sure you'll get much support here (or anywhere) for FreeBSD 5.x. I would start by taking the machine down, booting it into single-user, and running fsck -y. background fsck does not catch all errors. Also, how soon do you check the box to see how much space/free inodes it has after receiving a "filesystem full" error? Are we talking "I checked it 4-5 hours later", or "I checked it 30 seconds after"? -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
FreeBSD 5.4 - filesystem full
I have an old enough server with FreeBSD 5.4 which from time to time complains about filesystem full. But the problem is that the partition in question has about 15G free space and more than 1000 free inodes. Then all by itself the error dissapears, only to be repeated several hours later. What can it be and where to look? The server runs mainly apache and sendmail, nothing special. Thanks and regards Alexander Varshavchick, Metrocom Joint Stock Company Phone: (812)718-3322, 718-3115(fax) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
FreeBSD 5.4 - filesystem full
I have an old enough server with FreeBSD 5.4 which from time to time complains about filesystem full. But the problem is that the partition in question has about 15G free space and more than 1000 free inodes. Then all by itself the error dissapears, only to be repeated several hours later. What can it be and where to look? The server runs mainly apache and sendmail, nothing special. Thanks and regards Alexander Varshavchick, Metrocom Joint Stock Company Phone: (812)718-3322, 718-3115(fax) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Filesystem full......
On Mon, Apr 21, 2008 at 12:10:03PM -0400, Robert Huff wrote: > > Leslie Jensen writes: > > > /: write failed, filesystem is full > > install: /boot/kernel/wlan_tkip.ko.symbols: No space left on device > > *** Error code 71 > > > > My question is can I get around this or have I made my / slice to > > small? Just to keep this clear. Your root file system is on a FreeBSD partition - partition 'a' Robert Huff uses the term correctly below, but you do not above. jerry > > Yes. :-) > Start by cleaning up /; usually that starts with /tmp ... but > you've already got that on a separate partition, > As for the size - the machine I'm currently on shows: > > huff@> du /boot | sort -nr | head > 210558 /boot > 93642 /boot/kernel > 93002 /boot/kernel.old > 22978 /boot/GENERIC > 22 /boot/defaults > 2 /boot/zfs > 2 /boot/modules > 2 /boot/firmware > > That's 220mb just for kernels. There's no reason I can't > delete kernel.old or GENERIC ... but having fall-backs lets me sleep > better. > Add 13m for /sbin, 20m for /lib, and you're pretty much done. > (That machine has a 500mb /.) > > > Robert Huff > > > > > ___ > 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: Filesystem full......
On Mon, Apr 21, 2008 at 06:08:39PM +0200, Leslie Jensen wrote: > > > Bill Moran skrev: > >In response to Leslie Jensen <[EMAIL PROTECTED]>: > > > >>During "make installkernel KERNCONF=GENERIC" I get > >> > >>/: write failed, filesystem is full > >>install: /boot/kernel/wlan_tkip.ko.symbols: No space left on device > >>*** Error code 71 > >> > >>output of df -H gives > >> > >>Filesystem SizeUsed Avail Capacity Mounted on > >>/dev/ad0s1a260M259M-20M 108%/ > >>devfs 1.0k1.0k 0B 100%/dev > >>/dev/ad0s1g127G 30G 87G25%/home > >>/dev/ad0s1e260M 26M213M11%/tmp > >>/dev/ad0s1f 26G6.0G 18G25%/usr > >>/dev/ad0s1d260M209M 30M87%/var > >>/dev/ad4s1d387G119G237G33%/backup > >>linprocfs 4.1k4.1k 0B 100%/usr/compat/linux/proc > >> > >>It's a system I've had for a few years, and it has been upgreded a few > >>times before. > >> > >>My question is can I get around this or have I made my / slice to small? > > > >Your / is too small for modern version of FreeBSD. > > > >However, you probably can get around this. My / partition on a 7.X > >system is only 160M, so there's probably some stuff you can clean out > >to make room. Do you have a /boot/kernel.old file that would free up > >some space if removed? > > > > Thank you :-) I removed kernel.old and it gave space to do what I wanted. > > A follow up question: Is there a utility like gparted for Linux, that > can resize bsd slices? Well, gparted will work with FreeBSD slices. They just call them primary partitions instead of slices because that is what Microsloth calls them. But, fdisk is what manupulated slices in FreeBSD. It does it by brute force - rewriting the slice table and not preserving what was there before. So, you would need to use dump/restore to carry your stuff over.But they you would have a clean slice or set of slices with the latest filesystem type. Just to make sure we are talking about the same thing: In FreeBSD the slice is the primary division of the disk labeled 1..4. and a partiton is a subdivision of a slice labeled a..h. Microsloth and some others use the word partition to mean other things. jerry > > /Leslie > ___ > 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: Filesystem full......
quoth the darren kirby: > quoth the Martin Tournoij: > > On Mon, Apr 21, 2008 at 05:44:43PM +0200, Leslie Jensen wrote: > > > During "make installkernel KERNCONF=GENERIC" I get > > > > > > /: write failed, filesystem is full > > > install: /boot/kernel/wlan_tkip.ko.symbols: No space left on device > > > *** Error code 71 > > > > > > output of df -H gives > > > > > > Filesystem SizeUsed Avail Capacity Mounted on > > > /dev/ad0s1a260M259M-20M 108%/ > > > devfs 1.0k1.0k 0B 100%/dev > > > /dev/ad0s1g127G 30G 87G25%/home > > > /dev/ad0s1e260M 26M213M11%/tmp > > > /dev/ad0s1f 26G6.0G 18G25%/usr > > > /dev/ad0s1d260M209M 30M87%/var > > > /dev/ad4s1d387G119G237G33%/backup > > > linprocfs 4.1k4.1k 0B 100%/usr/compat/linux/proc > > > > > > It's a system I've had for a few years, and it has been upgreded a few > > > times before. > > > > > > My question is can I get around this or have I made my / slice to > > > small? > > > > > > Thanks > > > > > > /Leslie > > > > 256M should be enough. > > Might not be. I have a brand new install here of 7.0 Release (I did build a > second kernel), and df is reporting my '/' is 267M. I have /usr and /var > (not /tmp) mounted elsewhere. My /tmp is only using 10K right now, and > /home has nothing but .cshrc et al so if you want a backup kernel you may > need more than 256M. > > Did the install yesterday so there is no cruft yet... Ahhh Disregard this. I copied GENERIC kernel to kernel.good, plus the kernel install made kernel.old for total of three kernels. After removing one my '/' is 155M Sorry, -d -- darren kirby :: Part of the problem since 1976 :: http://badcomputer.org "...the number of UNIX installations has grown to 10, with more expected..." - Dennis Ritchie and Ken Thompson, June 1972 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Filesystem full......
quoth the Martin Tournoij: > On Mon, Apr 21, 2008 at 05:44:43PM +0200, Leslie Jensen wrote: > > During "make installkernel KERNCONF=GENERIC" I get > > > > /: write failed, filesystem is full > > install: /boot/kernel/wlan_tkip.ko.symbols: No space left on device > > *** Error code 71 > > > > output of df -H gives > > > > Filesystem SizeUsed Avail Capacity Mounted on > > /dev/ad0s1a260M259M-20M 108%/ > > devfs 1.0k1.0k 0B 100%/dev > > /dev/ad0s1g127G 30G 87G25%/home > > /dev/ad0s1e260M 26M213M11%/tmp > > /dev/ad0s1f 26G6.0G 18G25%/usr > > /dev/ad0s1d260M209M 30M87%/var > > /dev/ad4s1d387G119G237G33%/backup > > linprocfs 4.1k4.1k 0B 100%/usr/compat/linux/proc > > > > It's a system I've had for a few years, and it has been upgreded a few > > times before. > > > > My question is can I get around this or have I made my / slice to small? > > > > Thanks > > > > /Leslie > > 256M should be enough. Might not be. I have a brand new install here of 7.0 Release (I did build a second kernel), and df is reporting my '/' is 267M. I have /usr and /var (not /tmp) mounted elsewhere. My /tmp is only using 10K right now, and /home has nothing but .cshrc et al so if you want a backup kernel you may need more than 256M. Did the install yesterday so there is no cruft yet... > You probably have some "junk" on the root filesystem, you may want to > check /boot/kernel.old and /root > > You can use du -hxd1 to check the sizes of directories, and see which > are taking up so much space. > > Regards, > Martin Tournoij -d -- darren kirby :: Part of the problem since 1976 :: http://badcomputer.org "...the number of UNIX installations has grown to 10, with more expected..." - Dennis Ritchie and Ken Thompson, June 1972 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Filesystem full......
On Mon, Apr 21, 2008 at 05:44:43PM +0200, Leslie Jensen wrote: > > During "make installkernel KERNCONF=GENERIC" I get > > /: write failed, filesystem is full > install: /boot/kernel/wlan_tkip.ko.symbols: No space left on device > *** Error code 71 > > output of df -H gives > > Filesystem SizeUsed Avail Capacity Mounted on > /dev/ad0s1a260M259M-20M 108%/ > devfs 1.0k1.0k 0B 100%/dev > /dev/ad0s1g127G 30G 87G25%/home > /dev/ad0s1e260M 26M213M11%/tmp > /dev/ad0s1f 26G6.0G 18G25%/usr > /dev/ad0s1d260M209M 30M87%/var > /dev/ad4s1d387G119G237G33%/backup > linprocfs 4.1k4.1k 0B 100%/usr/compat/linux/proc > > It's a system I've had for a few years, and it has been upgreded a few > times before. > > My question is can I get around this or have I made my / slice to small? > > Thanks > > /Leslie 256M should be enough. You probably have some "junk" on the root filesystem, you may want to check /boot/kernel.old and /root You can use du -hxd1 to check the sizes of directories, and see which are taking up so much space. Regards, Martin Tournoij ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Filesystem full......
Leslie Jensen writes: > /: write failed, filesystem is full > install: /boot/kernel/wlan_tkip.ko.symbols: No space left on device > *** Error code 71 > > My question is can I get around this or have I made my / slice to > small? Yes. :-) Start by cleaning up /; usually that starts with /tmp ... but you've already got that on a separate partition, As for the size - the machine I'm currently on shows: huff@> du /boot | sort -nr | head 210558 /boot 93642 /boot/kernel 93002 /boot/kernel.old 22978 /boot/GENERIC 22 /boot/defaults 2 /boot/zfs 2 /boot/modules 2 /boot/firmware That's 220mb just for kernels. There's no reason I can't delete kernel.old or GENERIC ... but having fall-backs lets me sleep better. Add 13m for /sbin, 20m for /lib, and you're pretty much done. (That machine has a 500mb /.) 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: Filesystem full......
Bill Moran skrev: In response to Leslie Jensen <[EMAIL PROTECTED]>: During "make installkernel KERNCONF=GENERIC" I get /: write failed, filesystem is full install: /boot/kernel/wlan_tkip.ko.symbols: No space left on device *** Error code 71 output of df -H gives Filesystem SizeUsed Avail Capacity Mounted on /dev/ad0s1a260M259M-20M 108%/ devfs 1.0k1.0k 0B 100%/dev /dev/ad0s1g127G 30G 87G25%/home /dev/ad0s1e260M 26M213M11%/tmp /dev/ad0s1f 26G6.0G 18G25%/usr /dev/ad0s1d260M209M 30M87%/var /dev/ad4s1d387G119G237G33%/backup linprocfs 4.1k4.1k 0B 100%/usr/compat/linux/proc It's a system I've had for a few years, and it has been upgreded a few times before. My question is can I get around this or have I made my / slice to small? Your / is too small for modern version of FreeBSD. However, you probably can get around this. My / partition on a 7.X system is only 160M, so there's probably some stuff you can clean out to make room. Do you have a /boot/kernel.old file that would free up some space if removed? Thank you :-) I removed kernel.old and it gave space to do what I wanted. A follow up question: Is there a utility like gparted for Linux, that can resize bsd slices? /Leslie ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Filesystem full......
In response to Leslie Jensen <[EMAIL PROTECTED]>: > > During "make installkernel KERNCONF=GENERIC" I get > > /: write failed, filesystem is full > install: /boot/kernel/wlan_tkip.ko.symbols: No space left on device > *** Error code 71 > > output of df -H gives > > Filesystem SizeUsed Avail Capacity Mounted on > /dev/ad0s1a260M259M-20M 108%/ > devfs 1.0k1.0k 0B 100%/dev > /dev/ad0s1g127G 30G 87G25%/home > /dev/ad0s1e260M 26M213M11%/tmp > /dev/ad0s1f 26G6.0G 18G25%/usr > /dev/ad0s1d260M209M 30M87%/var > /dev/ad4s1d387G119G237G33%/backup > linprocfs 4.1k4.1k 0B 100%/usr/compat/linux/proc > > It's a system I've had for a few years, and it has been upgreded a few > times before. > > My question is can I get around this or have I made my / slice to small? Your / is too small for modern version of FreeBSD. However, you probably can get around this. My / partition on a 7.X system is only 160M, so there's probably some stuff you can clean out to make room. Do you have a /boot/kernel.old file that would free up some space if removed? -- Bill Moran http://www.potentialtech.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Filesystem full......
During "make installkernel KERNCONF=GENERIC" I get /: write failed, filesystem is full install: /boot/kernel/wlan_tkip.ko.symbols: No space left on device *** Error code 71 output of df -H gives Filesystem SizeUsed Avail Capacity Mounted on /dev/ad0s1a260M259M-20M 108%/ devfs 1.0k1.0k 0B 100%/dev /dev/ad0s1g127G 30G 87G25%/home /dev/ad0s1e260M 26M213M11%/tmp /dev/ad0s1f 26G6.0G 18G25%/usr /dev/ad0s1d260M209M 30M87%/var /dev/ad4s1d387G119G237G33%/backup linprocfs 4.1k4.1k 0B 100%/usr/compat/linux/proc It's a system I've had for a few years, and it has been upgreded a few times before. My question is can I get around this or have I made my / slice to small? Thanks /Leslie ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: filesystem full after many mmap/munmap cycles
I have an app server that uses mmap a lot. After running a long batch (four hours, 5,100+ transactions), I got the message filesystem full (/usr--ufs, local, soft-updates). df -i says plenty of space. I restarted the batch process, and watched app server process carefully with fstat -p, and it looks to be behaving responsibly. The open file list is short, and when I looked up the file names by inum, they were correct. Each transaction does a mmap/munap cycle with a (big ?) file (79M), then copies another smaller file, using mmap to do the copy. fwrite failed on the copy operation; FreeBSD said no space. (When fwrite failed, I called abort, so I have a core and can see where it happened.) probably the program doesn't unmap/close files that it deletes. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
filesystem full after many mmap/munmap cycles
Hi, I'm running FreeBSD 7.0 RC1 on AMD 64, dual Opteron with h/w raid1 (scsi). I have an app server that uses mmap a lot. After running a long batch (four hours, 5,100+ transactions), I got the message filesystem full (/usr--ufs, local, soft-updates). df -i says plenty of space. I restarted the batch process, and watched app server process carefully with fstat -p, and it looks to be behaving responsibly. The open file list is short, and when I looked up the file names by inum, they were correct. Each transaction does a mmap/munap cycle with a (big ?) file (79M), then copies another smaller file, using mmap to do the copy. fwrite failed on the copy operation; FreeBSD said no space. (When fwrite failed, I called abort, so I have a core and can see where it happened.) pid 29990 (r.fcgi), uid 1001 inumber 359181 on /usr: filesystem full pid 29990 (r.fcgi), uid 1001: exited on signal 11 Filesystem 1K-blocksUsed Avail Capacity iused ifree %iused Mounted on /dev/da0s1g 6297070 3380066 241324058% 183869 640449 22% /usr Is there some file system delay (maybe something related to softupdates) that could accumulate in some way that would cause the file system full message? Please CC me, as I'm not a subscriber. Thanks, m ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Urgent: filesystem "full", though space is available
Matthew Seaman wrote: > David Kelly wrote: >> On Mon, Mar 17, 2008 at 06:11:47PM +0100, Erwan David wrote: >>> I use lsof to get the list of removed files still open (lsof +L1, >>> useful after a port upgrade to check wether all upgraded daemons >>> indeed restarted). It seems it's not possible with fstat. >> >> ... which is exactly what Jennifer needs at this moment (if she has room >> to install lsof). She has removed files yet not freed space and needs a >> tool to figure out who/what has these files open. > > fstat(1). It comes with the system. > > Cheers, > > Matthew Don't forget to check out all the snapshot files as well, I've had a similar issue and after deleting the snapshots the disk space was back in normal. Cheers, Peter ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Urgent: filesystem "full", though space is available
David Kelly wrote: On Mon, Mar 17, 2008 at 06:11:47PM +0100, Erwan David wrote: I use lsof to get the list of removed files still open (lsof +L1, useful after a port upgrade to check wether all upgraded daemons indeed restarted). It seems it's not possible with fstat. ... which is exactly what Jennifer needs at this moment (if she has room to install lsof). She has removed files yet not freed space and needs a tool to figure out who/what has these files open. fstat(1). It comes with the system. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: Urgent: filesystem "full", though space is available
On Mon, Mar 17, 2008 at 06:11:47PM +0100, Erwan David wrote: > > I use lsof to get the list of removed files still open (lsof +L1, > useful after a port upgrade to check wether all upgraded daemons > indeed restarted). It seems it's not possible with fstat. ... which is exactly what Jennifer needs at this moment (if she has room to install lsof). She has removed files yet not freed space and needs a tool to figure out who/what has these files open. Early in this thread I recommended a reboot. What, 4 hours ago and the server still ailing? A 5 minute reboot might have been a minor inconvenience in retrospect. -- David Kelly N4HHE, [EMAIL PROTECTED] Whom computers would destroy, they must first drive mad. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Urgent: filesystem "full", though space is available
On Mar 17, 2008, at 11:34 AM, Dr. Jennifer Nussbaum wrote:
Hi, Ive got a big problem now on a production server.
When i do various things, i am getting "write failed, file system
full"
messages all over the place. Ive gone through and deleted
things i can, and i should have the space now, but its just
not available:
$ df -m
Filesystem 1M-blocks Used Avail Capacity Mounted on
/dev/da0s1a 2015 1858-3 100%/
/dev/da0s1e 14061 9002 393370%/usr/local
procfs 00 0 100%/proc
I dont know what kind of math lets you do 2015-1858 and gives
you an answer of -3!
I have softupdates, or whatever, but i dont know how to get
it to release this space. I cant reboot the running server.
I am planning on adding a disc to this system but right now
i need to get this space released ASAP! Can anyone help?
The math used in df is a compromise. The system reserves about 8% of
the blocks in the filesystem for root to write only. This is because
back in the day if the filesystem truely completely filled up the
situation would go from bad to worse pretty quickly. If I recall
correctly The filesystem performance falls off of the cliff once the
filesystem fills up.
In your particular case I can see that you have about 150Mb free on
the system. You do have the option of getting at this space using the
tunefs command:
man tunefs
to change the percentage of free space reserved for root but as I
inferred before expect performance to suffer.
A thread poster suggested that you remove the contents of /usr/ports/
distfiles to free up some space. If you built the system from scratch
and have built a bunch of ports this is a good place to go but if that
is the case you probably want to clean out any work directories first:
# find /usr/ports -type d -name work -print
Will generate a list of the work directories for any ports you have
built. In general you can completely recreate this data by building
the port again so if you have a lot of space tied up here you can
easily reclaim it with this command:
# find /usr/ports -type d -name work -exec rm -rf {} \;
This will remove just the work directories from the ports tree. It
costs you extract, patch, and compile time but it's quicker than:
# cd /usr/ports
# make clean
If you haven't built the system from ports then you have to identify
what action filled up the filesystem and make the appropriate
correction.
-- Chris
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Urgent: filesystem "full", though space is available
Le Mon 17/03/2008, Bill Moran disait > In response to Dan Nelson <[EMAIL PROTECTED]>: > > > In the last episode (Mar 17), Bill Moran said: > > > In response to "Armando Cambra" <[EMAIL PROTECTED]>: > > > > > > > Or try to find the culprit with lsof (can't remember the options). > > > > You will see some processes using files you don't have --> kill > > > > that process and your space will be freed. > > > > > > You can also use fstat if you don't wan to install Linux software on your > > > BSD system. > > > > The l in lsof doesn't stand for Linux :) lsof is bsd-licensed > > actaully. > > True, but not my point. > > lsof is like wget ... it's built into almost every Linux distro. Thus > you see lots of people suggesting your install lsof and wget on BSD > systems with no mention of fstat and fetch. Even if lsof is BSD > licensed, it's really a Linux program on account of how it's used. > > fstat, in particular, is just as useful as lsof in every case I've needed > it. I use lsof to get the list of removed files still open (lsof +L1, useful after a port upgrade to check wether all upgraded daemons indeed restarted). It seems it's not possible with fstat. -- Erwan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Urgent: filesystem "full", though space is available
In response to Dan Nelson <[EMAIL PROTECTED]>: > In the last episode (Mar 17), Bill Moran said: > > In response to "Armando Cambra" <[EMAIL PROTECTED]>: > > > > > Or try to find the culprit with lsof (can't remember the options). > > > You will see some processes using files you don't have --> kill > > > that process and your space will be freed. > > > > You can also use fstat if you don't wan to install Linux software on your > > BSD system. > > The l in lsof doesn't stand for Linux :) lsof is bsd-licensed > actaully. True, but not my point. lsof is like wget ... it's built into almost every Linux distro. Thus you see lots of people suggesting your install lsof and wget on BSD systems with no mention of fstat and fetch. Even if lsof is BSD licensed, it's really a Linux program on account of how it's used. fstat, in particular, is just as useful as lsof in every case I've needed it. I'm just being pedantic :) -- Bill Moran http://www.potentialtech.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Urgent: filesystem "full", though space is available
In the last episode (Mar 17), Bill Moran said: > In response to "Armando Cambra" <[EMAIL PROTECTED]>: > > > Or try to find the culprit with lsof (can't remember the options). > > You will see some processes using files you don't have --> kill > > that process and your space will be freed. > > You can also use fstat if you don't wan to install Linux software on your > BSD system. The l in lsof doesn't stand for Linux :) lsof is bsd-licensed actaully. -- Dan Nelson [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: Urgent: filesystem "full", though space is available
In response to "Armando Cambra" <[EMAIL PROTECTED]>: > Or try to find the culprit with lsof (can't remember the options). You will > see some processes using files you don't have --> kill that process and your > space will be freed. You can also use fstat if you don't wan to install Linux software on your BSD system. -- Bill Moran http://www.potentialtech.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Urgent: filesystem "full", though space is available
Or try to find the culprit with lsof (can't remember the options). You will see some processes using files you don't have --> kill that process and your space will be freed. I hope this helps. Regards and good luck. On Mon, Mar 17, 2008 at 5:10 PM, Jerry McAllister <[EMAIL PROTECTED]> wrote: > On Mon, Mar 17, 2008 at 08:34:18AM -0700, Dr. Jennifer Nussbaum wrote: > > This is a FAQ and has to do with space reserved for root(system). > > Check the FAQs on the FreeBSD web site. > > jerry > > > > > Hi, Ive got a big problem now on a production server. > > > > When i do various things, i am getting "write failed, file system full" > > messages all over the place. Ive gone through and deleted > > things i can, and i should have the space now, but its just > > not available: > > > > $ df -m > > Filesystem 1M-blocks Used Avail Capacity Mounted on > > /dev/da0s1a 2015 1858-3 100%/ > > /dev/da0s1e 14061 9002 393370%/usr/local > > procfs 00 0 100%/proc > > > > I dont know what kind of math lets you do 2015-1858 and gives > > you an answer of -3! > > > > I have softupdates, or whatever, but i dont know how to get > > it to release this space. I cant reboot the running server. > > I am planning on adding a disc to this system but right now > > i need to get this space released ASAP! Can anyone help? > > > > Thanks, > > > > Jen > > > > > > - > > Never miss a thing. Make Yahoo your homepage. > > ___ > > 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]" > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Urgent: filesystem "full", though space is available
On Mon, Mar 17, 2008 at 08:34:18AM -0700, Dr. Jennifer Nussbaum wrote: This is a FAQ and has to do with space reserved for root(system). Check the FAQs on the FreeBSD web site. jerry > > Hi, Ive got a big problem now on a production server. > > When i do various things, i am getting "write failed, file system full" > messages all over the place. Ive gone through and deleted > things i can, and i should have the space now, but its just > not available: > > $ df -m > Filesystem 1M-blocks Used Avail Capacity Mounted on > /dev/da0s1a 2015 1858-3 100%/ > /dev/da0s1e 14061 9002 393370%/usr/local > procfs 00 0 100%/proc > > I dont know what kind of math lets you do 2015-1858 and gives > you an answer of -3! > > I have softupdates, or whatever, but i dont know how to get > it to release this space. I cant reboot the running server. > I am planning on adding a disc to this system but right now > i need to get this space released ASAP! Can anyone help? > > Thanks, > > Jen > > > - > Never miss a thing. Make Yahoo your homepage. > ___ > 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: Urgent: filesystem "full", though space is available
Well try deleting /usr/ports/distfiles/* it looks like your / is the whole system and except /usr/local/ Also try sync to sync your disks right away Regards, Johan -Oorspronkelijk bericht- Van: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Namens Dr. Jennifer Nussbaum Verzonden: maandag 17 maart 2008 16:34 Aan: freebsd-questions@freebsd.org Onderwerp: Urgent: filesystem "full", though space is available Hi, Ive got a big problem now on a production server. When i do various things, i am getting "write failed, file system full" messages all over the place. Ive gone through and deleted things i can, and i should have the space now, but its just not available: $ df -m Filesystem 1M-blocks Used Avail Capacity Mounted on /dev/da0s1a 2015 1858-3 100%/ /dev/da0s1e 14061 9002 393370%/usr/local procfs 00 0 100%/proc I dont know what kind of math lets you do 2015-1858 and gives you an answer of -3! I have softupdates, or whatever, but i dont know how to get it to release this space. I cant reboot the running server. I am planning on adding a disc to this system but right now i need to get this space released ASAP! Can anyone help? Thanks, Jen - Never miss a thing. Make Yahoo your homepage. ___ 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: Urgent: filesystem "full", though space is available
> > i need to get this space released ASAP! Can anyone help? > > Please see the FreeBSD FAQ entries on "The du and df commands show > different amounts of disk space available. What is going on?" and "How > is it possible for a partition to be more than 100% full?" Also be sure to: $ alias df="/bin/df -hi". Inodes at 100% capacity (such as a sendmail clusterfuck) can cause file system-full error messages. This is why you should have partitioned off /var ~BAS -- Brian A. Seklecki <[EMAIL PROTECTED]> Collaborative Fusion, Inc. IMPORTANT: This message contains confidential information and is intended only for the individual named. If the reader of this message is not an intended recipient (or the individual responsible for the delivery of this message to an intended recipient), please be advised that any re-use, dissemination, distribution or copying of this message is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Urgent: filesystem "full", though space is available
On Mon, Mar 17, 2008 at 08:34:18AM -0700, Dr. Jennifer Nussbaum wrote: > > Hi, Ive got a big problem now on a production server. > > When i do various things, i am getting "write failed, file system full" > messages all over the place. Ive gone through and deleted > things i can, and i should have the space now, but its just > not available: Deleted files only disappear from the directory listings. File space is not freed until the last process closes the open file. A programming "trick" is to create/open temporary file(s) when program is launched then unlink (delete) the file(s) while they are still open. As long as one has an open file handle the files are perfectly usable. When program terminates normally or by exception, the OS cleans up and no mess is left. > $ df -m > Filesystem 1M-blocks Used Avail Capacity Mounted on > /dev/da0s1a 2015 1858-3 100%/ > /dev/da0s1e 14061 9002 393370%/usr/local > procfs 00 0 100%/proc > > I dont know what kind of math lets you do 2015-1858 and gives > you an answer of -3! There is an 8% reserve that only root can eat into. You are 3 MB into your 8% reserve. This is BSD Unix 101. > I have softupdates, or whatever, but i dont know how to get > it to release this space. I cant reboot the running server. > I am planning on adding a disc to this system but right now > i need to get this space released ASAP! Can anyone help? A reboot is the fastest way to close open files and release their space. -- David Kelly N4HHE, [EMAIL PROTECTED] Whom computers would destroy, they must first drive mad. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Urgent: filesystem "full", though space is available
At 10:34 AM 3/17/2008, Dr. Jennifer Nussbaum wrote: Hi, Ive got a big problem now on a production server. When i do various things, i am getting "write failed, file system full" messages all over the place. Ive gone through and deleted things i can, and i should have the space now, but its just not available: $ df -m Filesystem 1M-blocks Used Avail Capacity Mounted on /dev/da0s1a 2015 1858-3 100%/ /dev/da0s1e 14061 9002 393370%/usr/local procfs 00 0 100%/proc I dont know what kind of math lets you do 2015-1858 and gives you an answer of -3! I have softupdates, or whatever, but i dont know how to get it to release this space. I cant reboot the running server. I am planning on adding a disc to this system but right now i need to get this space released ASAP! Can anyone help? Thanks, Jen If you have deleted files, you probably need to reboot the server. -Derek -- 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]"
Re: Urgent: filesystem "full", though space is available
"Dr. Jennifer Nussbaum" <[EMAIL PROTECTED]> writes: > Hi, Ive got a big problem now on a production server. > > When i do various things, i am getting "write failed, file system full" > messages all over the place. Ive gone through and deleted > things i can, and i should have the space now, but its just > not available: > > $ df -m > Filesystem 1M-blocks Used Avail Capacity Mounted on > /dev/da0s1a 2015 1858-3 100%/ > /dev/da0s1e 14061 9002 393370%/usr/local > procfs 00 0 100%/proc > > I dont know what kind of math lets you do 2015-1858 and gives > you an answer of -3! > > I have softupdates, or whatever, but i dont know how to get > it to release this space. I cant reboot the running server. > I am planning on adding a disc to this system but right now > i need to get this space released ASAP! Can anyone help? Please see the FreeBSD FAQ entries on "The du and df commands show different amounts of disk space available. What is going on?" and "How is it possible for a partition to be more than 100% full?" -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Urgent: filesystem "full", though space is available
Hi, Ive got a big problem now on a production server. When i do various things, i am getting "write failed, file system full" messages all over the place. Ive gone through and deleted things i can, and i should have the space now, but its just not available: $ df -m Filesystem 1M-blocks Used Avail Capacity Mounted on /dev/da0s1a 2015 1858-3 100%/ /dev/da0s1e 14061 9002 393370%/usr/local procfs 00 0 100%/proc I dont know what kind of math lets you do 2015-1858 and gives you an answer of -3! I have softupdates, or whatever, but i dont know how to get it to release this space. I cant reboot the running server. I am planning on adding a disc to this system but right now i need to get this space released ASAP! Can anyone help? Thanks, Jen - Never miss a thing. Make Yahoo your homepage. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: /tmp: filesystem full
Be sure to make a backup of /etc/mail/sendmail.cf. Then, should be able to add the line to /etc/mail/freebsd.mc, run make, and copy /ett/mail/freebsd.cf to /etc/mail/sendmail.cf. o.k. it seems it worked, hope don´t get that messages anymore. thank you very much. regards!!! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: /tmp: filesystem full
On Thu, Dec 13, 2007 at 11:35:57AM -0600, Cesar Amaya wrote: > Do I create the sendmail.mc file from scratch because I don´t have any? > I just have a freebsd.mc file. > Be sure to make a backup of /etc/mail/sendmail.cf. Then, should be able to add the line to /etc/mail/freebsd.mc, run make, and copy /ett/mail/freebsd.cf to /etc/mail/sendmail.cf. -- John D. "Trix" Farrar __\\|//__ Basement.NET [EMAIL PROTECTED] (` o-o ') http://www.basement.net/ ---ooO-(_)-Ooo-- pgpCkBlVg7lVb.pgp Description: PGP signature
Re: /tmp: filesystem full
I think you want to put it in sendmail.mc and then run the make in /ec/sendmail rather than modify sendmail.cf directly. Do I create the sendmail.mc file from scratch because I don´t have any? I just have a freebsd.mc file. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: /tmp: filesystem full
On Thu, Dec 13, 2007 at 11:10:33AM -0600, Cesar Amaya wrote: > > > > >Huh??? Where else would you put it? > > > > > > > In /etc/mail/sendmail.cf I think you want to put it in sendmail.mc and then run the make in /ec/sendmail rather than modify sendmail.cf directly. jerry ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: /tmp: filesystem full
Huh??? Where else would you put it? In /etc/mail/sendmail.cf ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: /tmp: filesystem full
On Thu, Dec 13, 2007 at 10:08:08AM -0600, Cesar Amaya wrote: > > >You should add something like this to your sendmail.mc config: > > > > define(`confMAX_MESSAGE_SIZE', `2100')dnl > > > >...which will set a maximum message size that your SMTP server is > >willing to accept. The recommended max size in the RFCs was something > >like 10 MB, but season to taste. > Do I have to follow the /usr/share/sendmail/cf/cf/README file in order > to configure sendmail as you said? or can I just put the above line in > some other config file? Huh??? Where else would you put it? > > P.D. the server had 2 files of 4.1 G each in /var/spool/mqueue, I > deleted this files and no more error messages appeared. Good. That, for now, solved your problem.Probably some attempted virus or denial of service attack. jerry > ___ > 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: /tmp: filesystem full
You should add something like this to your sendmail.mc config: define(`confMAX_MESSAGE_SIZE', `2100')dnl ...which will set a maximum message size that your SMTP server is willing to accept. The recommended max size in the RFCs was something like 10 MB, but season to taste. Do I have to follow the /usr/share/sendmail/cf/cf/README file in order to configure sendmail as you said? or can I just put the above line in some other config file? P.D. the server had 2 files of 4.1 G each in /var/spool/mqueue, I deleted this files and no more error messages appeared. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: /tmp: filesystem full
On Dec 12, 2007, at 2:19 PM, Jerry McAllister wrote: [EMAIL PROTECTED] wrote: I even restarted the server but the problem is still there. this is what I got every amount of time (not always). root mail.local 89873 /tmp 4 -rw--- 616886272 rw I don´t understand why mail.local is gathering a file that big Apparently someone out there keeps trying to resend that awful huge mail file, so whenever you restart, it gets stuck in that same condition. If you can track down the source of the file, either nuke it or block it. You should add something like this to your sendmail.mc config: define(`confMAX_MESSAGE_SIZE', `2100')dnl ...which will set a maximum message size that your SMTP server is willing to accept. The recommended max size in the RFCs was something like 10 MB, but season to taste. -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: /tmp: filesystem full
>> Apparently someone out there keeps trying to resend that awful >> huge mail file, so whenever you restart, it gets stuck in that >> same condition. If you can track down the source of the file, >> either nuke it or block it. In addition to finding the actual cause of the problem, you may want to consider symlinking /tmp under a larger partition until the problem is resolved. Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: /tmp: filesystem full
On Wed, Dec 12, 2007 at 05:56:23PM -0600, Cesar Amaya wrote: > > > > >Apparently someone out there keeps trying to resend that awful > >huge mail file, so whenever you restart, it gets stuck in that > >same condition. If you can track down the source of the file, > >either nuke it or block it. > > > >jerry > > > > > >>___ > >>freebsd-questions@freebsd.org mailing list > >>http://lists.freebsd.org/mailman/listinfo/freebsd-questions > >>To unsubscribe, send any mail to > >>"[EMAIL PROTECTED]" > >> > > > I´m gonna do so. > > Thank you very much you all guys!!! One thing you can do is to look in /var/spool/mqueue and see if there are any really large files in there. If there are, that is the one that is messing you up.Delete both the date file and the queue header file. jerry ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: /tmp: filesystem full
Apparently someone out there keeps trying to resend that awful huge mail file, so whenever you restart, it gets stuck in that same condition. If you can track down the source of the file, either nuke it or block it. jerry ___ 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]" I´m gonna do so. Thank you very much you all guys!!! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: /tmp: filesystem full
--On Wednesday, December 12, 2007 16:11:24 -0600 Cesar Amaya <[EMAIL PROTECTED]> wrote: Looks like something, maybe your mail program has a large file open - maybe trying to receive a huge file. Killing the process could get that file closed and either it would be gone or would finally show how much space it is holding. jerry I even restarted the server but the problem is still there. this is what I got every amount of time (not always). root mail.local 89873 /tmp 4 -rw--- 616886272 rw I don´t understand why mail.local is gathering a file that big Yikes! Looks like whatever that message is is being retried by the sending MTA. Perhaps you could try deleting the message from the queue. (I assume it will sit in there until delivery is successful.) I think, if you shut the mail server down and then restart it later, you're going to continue to have this problem. You may have to figure out where the message is coming from and try to stop it at the other end. Possibly you could configure your server to reject messages larger than a certain size, then restart it and let it reject it rather than trying to receive it. I know you can do that with Postfix. Don't know about other MTAs. One thing I would do is stop the mail server, wait a minute or two, and then check /tmp. This would positively confirm that the problem is coming from the mail server *if* the problem goes away when the server is stopped. -- Paul Schmehl ([EMAIL PROTECTED]) Senior Information Security Analyst The University of Texas at Dallas http://www.utdallas.edu/ir/security/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: /tmp: filesystem full
On Wed, Dec 12, 2007 at 04:11:24PM -0600, Cesar Amaya wrote: > > >Looks like something, maybe your mail program has a large file open - > >maybe trying to receive a huge file. Killing the process could get > >that file closed and either it would be gone or would finally show > >how much space it is holding. > > > >jerry > > > > > > I even restarted the server but the problem is still there. > this is what I got every amount of time (not always). > > root mail.local 89873 /tmp 4 -rw--- 616886272 rw > > I don´t understand why mail.local is gathering a file that big Apparently someone out there keeps trying to resend that awful huge mail file, so whenever you restart, it gets stuck in that same condition. If you can track down the source of the file, either nuke it or block it. jerry > ___ > 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: /tmp: filesystem full
Looks like something, maybe your mail program has a large file open - maybe trying to receive a huge file. Killing the process could get that file closed and either it would be gone or would finally show how much space it is holding. jerry I even restarted the server but the problem is still there. this is what I got every amount of time (not always). root mail.local 89873 /tmp 4 -rw--- 616886272 rw I don´t understand why mail.local is gathering a file that big ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: /tmp: filesystem full
--On Wednesday, December 12, 2007 16:13:42 -0500 Jerry McAllister <[EMAIL PROTECTED]> wrote: On Wed, Dec 12, 2007 at 03:08:50PM -0600, Cesar Amaya wrote: Robert Huff wrote: > Cesar Amaya writes: > > >> napstats# fstat | grep "/tmp" >> www httpd 1739 15 /tmp 4 -rw--- 0 rw >> > >Can you afford to shut down the web server (Apache ?)? > > >Robert Huff > > Nothing is shown if I shut down the web server. But I saw something weird when I run # fstat | grep "/tmp", was something like this: mail.local 1739 15 /tmp 4 -rw--- 73917491734 rw Looks like something, maybe your mail program has a large file open - maybe trying to receive a huge file. Killing the process could get that file closed and either it would be gone or would finally show how much space it is holding. Yep. Trying to stuff a 73GB file into a 1GB filesystem isn't going to work very well. At this point I think your only option is to restart the mailserver. Hopefully that will release the file from memory. Then you can delete whatever pieces of it are left in /tmp. I'd also look at your maillog to see what the filename and type of that message was (huge zip attachment?) and suggest to your user that he get the file some other way. -- Paul Schmehl ([EMAIL PROTECTED]) Senior Information Security Analyst The University of Texas at Dallas http://www.utdallas.edu/ir/security/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: /tmp: filesystem full
On Wed, Dec 12, 2007 at 03:08:50PM -0600, Cesar Amaya wrote: > Robert Huff wrote: > >Cesar Amaya writes: > > > > > >> napstats# fstat | grep "/tmp" > >> www httpd 1739 15 /tmp 4 -rw--- 0 rw > >> > > > > Can you afford to shut down the web server (Apache ?)? > > > > > > Robert Huff > > > > > Nothing is shown if I shut down the web server. But I saw something > weird when I run # fstat | grep "/tmp", was something like this: > > mail.local 1739 15 /tmp 4 -rw--- > 73917491734 rw Looks like something, maybe your mail program has a large file open - maybe trying to receive a huge file. Killing the process could get that file closed and either it would be gone or would finally show how much space it is holding. jerry > ___ > 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]"
