Cannot get any space freed up when removing files

tripkip · 09-04-2012, 04:48 AM

Running OpenMediaVault (Debian Squeeze).

Removed tons of files and folders (at least 50GB's).
Tried, fsck, lsop, reboot.

Still df shows 100% capacity usage and I cannot add any more files.

There is no .trash file/folder or any other weird file/folder on the drive.

Code:

root@NAS:/# du -sk /media/39d5d45e-6744-435a-8308-a7680b233d13/TV\ Shows/
1376436496   /media/39d5d45e-6744-435a-8308-a7680b233d13/TV Shows/
root@NAS:/# df -k /media/39d5d45e-6744-435a-8308-a7680b233d13/TV\ Shows/
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/sdf1            1463622108 1398113888         0 100% /media/39d5d45e-6744-435a-8308-a7680b233d13

I have been trying to get this sorted for 6 hours straight. Getting a little wacko here. Any help appreciated! Thanks in advance.

rknichols · 09-04-2012, 07:24 AM

What file system is on that drive? By default, ext2/3/4 file systems keep 5% of the blocks reserved for root, and your "Used" block count is still more than 95% of the total. Keeping those blocks reserved might not be necessary on a non-system drive, though fragmentation will become high on a drive with very little free space. You can use tune2fs (as root) to change the reserved block percentage. You can see the reserved block count with

Code:

tune2fs -l /dev/sdf1 | grep -i 'block count'

tripkip · 09-04-2012, 07:26 AM

Quote:

Originally Posted by rknichols

What file system is on that drive? By default, ext2/3/4 file systems keep 5% of the blocks reserved for root, and your "Used" block count is still more than 95% of the total. Keeping those blocks reserved might not be necessary on a non-system drive, though fragmentation will become high on a drive with very little free space. You can use tune2fs (as root) to change the reserved block percentage.

It's an ext4 file system.

Quote:

Originally Posted by rknichols

Code:

tune2fs -l /dev/sdf1 | grep -i 'block count'

I'll do this as soon as I get home (in 3.5 hours). Let me know if you need any more information.

Quote:

Originally Posted by rknichols

What if this weren't a rhetorical question?

In that case I would answer it, but now I sh-wouldn't.

tripkip · 09-04-2012, 11:24 AM

root@OPENMEDIAVAULT:~# tune2fs -l /dev/sdf1 | grep -i 'block count'
Block count: 366284288
Reserved block count: 18314214

If I am not mistaken, that is about 20% :-S

Is it safe to set the reserved block count to 0? (tune2fs -m 0 /dev/sdf1)
Note that this disk is for data storage only and that it potentially gets filled to the max.

rknichols · 09-04-2012, 12:06 PM

Quote:

Originally Posted by tripkip

Block count: 366284288
Reserved block count: 18314214

If I am not mistaken, that is about 20% :-S

No, that's 5%, which is the default for mkkfs.ext4.

Yes, you can safely set the reserve block count to zero. The only downside will be increased fragmentation due to the kernel having to store a file into whatever bits and pieces of free space it can find.

tripkip · 09-04-2012, 12:22 PM

Thank you, this solved my issue.