As Dustin mentioned, the on-disk footprint is not duplicated when using eCryptfs. The eCryptfs inode, as queried by the `du -h /home/name/9726255eec083aa56dc0449a21b3319`, is an in-memory representation of the actual on-disk inode in the lower filesystem.
Similarly, when df is reporting filesystem usage, the reported usage of any eCryptfs mount is simply the usage amount reported by the filesystem that eCryptfs is mounted upon.
While the output of those commands (and my explanation) may be confusing at first, it is the expected output when dealing with a stacked filesystem like eCryptfs.
Thanks for the report!
As Dustin mentioned, the on-disk footprint is not duplicated when using eCryptfs. The eCryptfs inode, as queried by the `du -h /home/name/ 9726255eec083aa 56dc0449a21b331 9`, is an in-memory representation of the actual on-disk inode in the lower filesystem.
Similarly, when df is reporting filesystem usage, the reported usage of any eCryptfs mount is simply the usage amount reported by the filesystem that eCryptfs is mounted upon.
While the output of those commands (and my explanation) may be confusing at first, it is the expected output when dealing with a stacked filesystem like eCryptfs.