Disk Usage
hello people
i've been reciveing these emails in my root account: Message 1: From root@localhost.localdomain Mon Oct 11 14:10:32 2004 Date: Sat, 25 Sep 2004 21:01:01 -0700 To: root@localhost.localdomain From: "Disk Usage Monitor" <root@localhost.localdomain> Subject: Low disk space warning - res1n-403-1.res.unbc.ca Disk usage for res1n-403-1.res.unbc.ca: Inodes: /dev/hda1 (/mnt/windows) is 100% full -- 56K of 56K used, 47 remain & Message 2: From root@localhost.localdomain Mon Oct 11 14:10:32 2004 Date: Sat, 25 Sep 2004 23:01:06 -0700 To: root@localhost.localdomain From: "Disk Usage Monitor" <root@localhost.localdomain> Subject: Low disk space warning - res1n-403-1.res.unbc.ca Disk usage for res1n-403-1.res.unbc.ca: Inodes: /dev/hda1 (/mnt/windows) is 100% full -- 56K of 56K used, 47 remain & is there anyway i can stop this or increase the size .... thank you very much |
If you are running out of inodes it means you have too many files, even tho' there may be plenty of space left on the disk. The inodes are part of the data structure making up the filesystem. As far as I know this is something that has to be set when the filesystem is created and can't be altered while preserving the data. Some linux filesystem types (e.g. ReiserFS) can create inodes as needed.
But if this is a windows partition I don't know what you can do. If you have a lot of small files maybe you could archive them into a single tar file and free up some inodes that way? Or maybe you can set something via windows? |
have you actually mounted /dev/hda1?
sl mritch. |
yes its mounted
i've mounted the /dev/hda and if there's no way other than using tar would you be kind and gimme an example of how doin it....
thank you very much |
i'd mean, was hda1 mounted when the cron job ran?
first, lets be sure we really have a problem: do (some as root): "df -i /dev/hda1" "mount | grep /dev/hda1" "cat /etc/fstab | grep /dev/hda1" "cat /proc/sys/fs/inode-state" "cat /proc/sys/fs/file-nr" and post results. the error message could also mean that the script you run from cron doesn't know how to handle the ms partitions correct and believes there is a problem with the number of inodes allocated. so if it's not to long, please post it. sl mritch. |
here is the result
[root@localhost karan]# df -i /dev/hda1
Filesystem Inodes IUsed IFree IUse% Mounted on /dev/hda1 60464 59352 1112 99% /mnt/windows [root@localhost karan]# cat /etc/fstab |grep /dev/hda1 /dev/hda1 /mnt/windows ntfs ro,defaults,umask=0222 0 0 [root@localhost karan]# cat /proc/sys/fs/file-nr 2740 0 65536 [root@localhost karan]# thank you verymuch karan |
there should be no trouble if you leave it mounted readonly. write access for ntfs is imho not 100% stable yet and i don't suggest using it if you care for your data.
if you really need your windows partition writeable keep (a small) fat32 for now. ..if you want to get rid of the mail you'll have to edit the script or disable that cronjob at all. sl mritch. |
umm would you explain how i can edit my cronjob
thank you |
crontab -e
|
All times are GMT -5. The time now is 12:36 PM. |