Tag Info

New answers tagged

1

I had this exact same problem where the files on my drive were relatively small, but disk space was 100% used up. I had an issue where my primary boot disk was filling up after I performed a sync of backup drives. >rsync -avxHAXW /media/backup1 /media/backup2 After this sync my primary disk was full.... which baffled me. It turns out I was ...


1

I found the cause of the problem - I used a tool called SpaceSniffer. Turns out there was about 19 GB of log files in the C:\Windows\system32 folder. I have no idea why they didn't show up in Treesize or WinDirStat, but regardless of why, I found the culprit. I have now deleted those files and voilĂ  - 22 GB free space!


-1

Could you download the following software and check? I hope this helps as this is a server just be careful before you clean the junk files out (Click the Analyse button and check how much you are gonna save from your hard drive) https://www.piriform.com/ccleaner


0

It might be trashes from users, or System Restore information, or something similar. WinDirStat or TreeSize wont be able to access those directories, at least if you don't run them with elevated privileges. And even then, you can't enter System Volume Information (that contains among others the restore points) because even not the administrator account is ...


1

Searching for the same thing, I found your question with no answers yet. For me, the following thing has worked: shut down the guest (in my case, a debian 7.0) in the usual way. extend the "original" LV (in the host's VG, of course), e.g., by 5G. For this, you have to be root/sudo on the host: lvextend -L +5G ...


1

First, some space is reserved for rootuser. You can check how much space is reserved for root,with: tune2fs -l /dev/mapper/vg_bgsvn-lv_root This will give you the block count reserved for root user, multiply it by the block size and you will get the size of reserved space (in bytes). Second, most probably some file descriptors are still in use. That ...


1

Either your filesystem is somehow corrupted or there's a huge sparse file or multiple sparse files in the Sports directory. Check this out: jaba@jaba-ubuntu:~$ dd if=/dev/zero of=I_am_a_huge_sparse_file bs=1M count=1000000 conv=sparse 1000000+0 records in 1000000+0 records out 1048576000000 bytes (1,0 TB) copied, 173,006 s, 6,1 GB/s jaba@jaba-ubuntu:~$ ls ...


0

That's what I'd try: df -a. df /mnt/a_share. stat -f /mnt/a_share.



Top 50 recent answers are included