Re: Urgent: filesystem full, though space is available

2008-03-18 Thread Peter Toth
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]


Urgent: filesystem full, though space is available

2008-03-17 Thread Dr. Jennifer Nussbaum

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: Urgent: filesystem full, though space is available

2008-03-17 Thread Lowell Gilbert
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]


Re: Urgent: filesystem full, though space is available

2008-03-17 Thread Derek Ragona

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

2008-03-17 Thread David Kelly
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

2008-03-17 Thread Brian A. Seklecki


  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

2008-03-17 Thread Johan Hendriks
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

2008-03-17 Thread Jerry McAllister
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

2008-03-17 Thread Armando Cambra
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

2008-03-17 Thread Bill Moran
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

2008-03-17 Thread Dan Nelson
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

2008-03-17 Thread Bill Moran
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

2008-03-17 Thread Erwan David
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

2008-03-17 Thread Christopher Sean Hilton


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

2008-03-17 Thread David Kelly
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

2008-03-17 Thread Matthew Seaman

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