Commands fail with disk full messages, but df says I've got plenty of space
I've been getting error messages indicating my disk might be full, but I don't really think it is. It is so bad that I could not log on via Gnome, but fortunately I was able SSH into my box. Once in, however, I can't even create a directory!
So I did the df command: Code:
vree:~/tmp$ df -h Any ideas? TIA, -Bob |
fsck the partitions
Get full info on the relevant partitions incl inodes ext4? |
Exactly what are the error messages saying? Also, just for kicks and giggles, post the results of:
fdisk -l Is this a new install? What distro are you using? |
Also, post the output of mount and df -i.
You may have a read-only filesystem, which the fsck could probably evaluate and repair. (Likely cause.) Or... you could be out of inodes. (Unlikely.) |
Definitely post the exact error msgs. You can also check the inodes
df -i |
your df command shows / mounted on /dev/sdb1. What is on /dev/sda?
|
What "error" are you receiving
Quote:
|
Wow! Thanks for all the responses! Here are my replies...
1. Sorry I wasn't clear on ther actual error messages. Here is one example; basically, I get the same "No space left on device" regardless of what I try: Code:
mkdir: cannot create directory `testdir': No space left on device 3. After rebooting, I was able to log on in a fail-safe terminal, and by deleting a few files, I was able to do the following, as suggested by several posts I've found: Code:
sudo touch /forcefsck 4. fdisk -l and mount results Code:
vree:~$ fdisk -l Code:
vree:~$ df -i Thanks! |
RESOLVED Commands fail with disk full messages, but df says I've got plenty of space
I found my problem! I have been using BackInTime (a poor man's Time Machine) on my workstation, and it was taking snapshots on the server; I haven't constrained it a bit, and so it has generated quite a few files - I'm currently counting them, and it's up to almost 4 million - and counting!
That's what you get with "set and forget" tools! (No, that's not a criticism of BackInTime!). Thanks, -Bob |
An inode is a data structure that is associated with each file. With ext3 the max number of inodes is set when the filesystem is created and the only way to increase the number is to reformat. You can not manage them i.e if you run out of inodes you can not create more files. There are other filesystems that can dynamically allocate inodes like jfs, xfs or ext4.
|
Quote:
Quote:
Cheers, -Bob |
Also, there's not much point in backing up to the same disk; what happens if the disk goes bad?
:) |
Quote:
|
Quote:
Later... -- Rick |
You can add a cron job to check the disk space, both filespace & inode cnt and email you if you exceed specified values.
You can even use quotas, eg soft limit at warning level, hard limit at full disk. Quotas have both diskspace and inode settings. |
All times are GMT -5. The time now is 10:03 AM. |