Tag Info

New answers tagged

1

You performed your bind mount backwards. Unmount it, swap the two paths in your fstab, and then mount again.


0

Are you running RHEL/CentOS? Confirm your file system in /etc/fstab. Assuming you are using ext3 or ext4, you should confirm how much space is reserved for the partition(s) by running tune2fs -l /path/to/partition | grep -i "reserve". For example; /dev/xvda1 | grep -i "reserve" Usually 5 - 10% is not usable because it is reserved. Calculate the reserved ...


1

I found the answer to my question of "how to fix this scenario". I don't know all the details of how this came to be, but I know enough to put out an answer. Short answer: unmounting the disk, running chkdsk -f on it, and mounting back again solves and prevents the issue from reoccurring. As an alternative, creating a new disk (remember we're on AWS) and ...


0

To display the biggest top-20 directories in the current folder, use the following one-liner: du -ah . | sort -rh | head -20 or: du -a . | sort -rn | head -20 For the top-20 biggest files in the current directory (recursively): ls -1Rs | sed -e "s/^ *//" | grep "^[0-9]" | sort -nr | head -n20 or with human readable sizes: ls -1Rhs | sed -e "s/^ ...


0

This is an interesting problem. My suspicion here is that this is some artifact from the physical system that got virtualized, but is undetectable because whatever physical cause is no longer present. Two examples could be: bad blocks on the physical drive that VMware Converter was able to recognize and get around but now the bad blocks are part of the ...



Top 50 recent answers are included