On an ext3 filesystem, what would cause the system to claim it is out of disk space for a program writing information to disk, when df -h shows ample GB available and the file is being written to local disk rather than an nfs-mounted filesystem?
I believe the hard drive is good.
Ideas welcome.
Thanks.
Scott
On Sat, 2008-01-12 at 09:23 -0500, Scott Ehrlich wrote:
On an ext3 filesystem, what would cause the system to claim it is out of disk space for a program writing information to disk, when df -h shows ample GB available and the file is being written to local disk rather than an nfs-mounted filesystem?
The percentage "reserved for the super user", perhaps? By default, 5% of ext2/3 disk space are reserved and can only be written by root. You can change this using the tune2fs utility:
tune2fs -m 0 /dev/whatever
Hth, Torsten
Scott Ehrlich wrote:
On an ext3 filesystem, what would cause the system to claim it is out of disk space for a program writing information to disk, when df -h shows ample GB available and the file is being written to local disk rather than an nfs-mounted filesystem?
I believe the hard drive is good.
Ideas welcome.
check that it is not out if inodes.
Scott Ehrlich wrote:
On an ext3 filesystem, what would cause the system to claim it is out of disk space for a program writing information to disk, when df -h shows ample GB available and the file is being written to local disk rather than an nfs-mounted filesystem?
I believe the hard drive is good.
Ideas welcome.
If the application is old it might not have been compiled with large file support.
By default 5% of the disk is going to be allocated for use by the root user. If you are seeing as a non root user that the disk is full, but when you become root you are able to write files, then this could be your issue. You can change the amount of blocks that are allocated for root, but using the -m switch with tune2fs.
Just a thought Joshua Gimer
On Jan 12, 2008, at 7:49 AM, Les Mikesell wrote:
Scott Ehrlich wrote:
On an ext3 filesystem, what would cause the system to claim it is out of disk space for a program writing information to disk, when df -h shows ample GB available and the file is being written to local disk rather than an nfs-mounted filesystem? I believe the hard drive is good. Ideas welcome.
If the application is old it might not have been compiled with large file support.
-- Les Mikesell lesmikesell@gmail.com _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On Saturday 12 January 2008 21:23:13 Scott Ehrlich wrote:
On an ext3 filesystem, what would cause the system to claim it is out of disk space for a program writing information to disk, when df -h shows ample GB available and the file is being written to local disk rather than an nfs-mounted filesystem?
It's a long shot, maybe the impossing filesize limit is the program itself such as apache's 2GB limit?
Scott Ehrlich wrote:
On an ext3 filesystem, what would cause the system to claim it is out of disk space for a program writing information to disk, when df -h shows ample GB available and the file is being written to local disk rather than an nfs-mounted filesystem?
Hi Scott:
I had this exact same problem with a machine just a couple days ago. In my case, unmounting the file system and running e2fsck -f on the partition fixed the problem. At least it might be worth a try.
thanks
Sean
On Sun, 13 Jan 2008, Sean Carolan wrote:
Scott Ehrlich wrote:
On an ext3 filesystem, what would cause the system to claim it is out of disk space for a program writing information to disk, when df -h shows ample GB available and the file is being written to local disk rather than an nfs-mounted filesystem?
Are you out of inodes?? df -i to see
Regards,
-
Fajar Priyanto -
Joshua Gimer -
Les Mikesell -
mouss -
Scott Ehrlich -
Sean Carolan -
Tom Diehl -
Torsten Luettgert