New answers tagged error-handling
Install ntfs-3g by following command : sudo apt-get install ntfs-3g Then run the ntfsfix command on your NTFS partition. For example: ntfsfix /dev/sda1 Then try removing folders sudo rm -rf folder or sudo rm -Rf folder
The partition table might have become corrupted. You can check this with fdisk: fdisk -l /dev/sdb If fdisk output shows a message like this: This doesn't look like a partition table Probably you selected the wrong device. and you don't wish to keep the data in it, you can try formatting it with gparted: sudo gparted /dev/sdb
Assuming that the drive hardware is functional, you should start with a file-system check. Open a terminal with CTRLALTT or your preferred method. Issue the command: sudo fsck /dev/sdb1 If prompted to repair, do so. If you get: No such file or directory while trying to open /dev/sdb1 Possibly non-existent device? Refer to @DavidFoerster comment "Your ...
The problem you are having is due to the fact that the percentage of inode used for /(/dev/sda4) is at 100%. When you create a file, an inode is generated for that file to keep the metadata. So, no matter how big or small the file is one file will result in one associated inode. By the size of the actual disk space free i am guessing that you may have many ...
Top 50 recent answers are included