Why are fdisk & df reporting different sizes for encrypted disk?
Here's the problem I'm having. I cannot determine slice size for dar, because I cannot figure out exactly what the slice size should be.
My output from fdisk -l seems to clash with my output from df. I didn't create any partitions when I encrypted the drive, so I believed that they should match. Alas, they do not. Code:
# fdisk -l Code:
# df -B1 |
fdisk looks at disks/partitions. df looks at filesystems. This seems to make sense on the face of it, since you encrypted the whole partition (which you referred to as a drive - it's not). The "extra" bytes fdisk sees are a function of the encryption and not useable - stick with what df reports.
FWIW, what does Code:
tune2fs -l /dev/mapper/realcrypt1 |
Another possibility can be space allocated to the root user (5%).
|
You are overlooking the file system overhead -- the space occupied by inodes, group descriptors, and the like. For an ext2/3/4 file system with the default parameters, this is around 1.5%. The report from df shows only the number of available data blocks after formatting.
|
Thanks for the information.
|
All times are GMT -5. The time now is 11:30 PM. |