I did a dd copy of a drive and saved it to a ntfs mount in a dataset in my mirrored pool prior to me trying to repair the drive. It’s a 2 GB image.dd. when I do a df -T it isn’t recognized and TrueNas still says I have only used 13% of by 7 GB but I can observe the full file size when I do a ls -al. Is this a TrueNAS issue. I wasn’t able to recover anything from the drive so I don’t really care about the data but am a little concerned about how its ignoring this file. How do I detect what is wrong?
I have absolutely no idea what you are describing here, especially where NTFS comes into this since you are doing this on TrueNAS and saving it apparently to a dataset in a mirrored pool.
My best guess is that the drive was an SSD and all the trimmed blocks were read as zeroes, and then ZFS created a sparse file where there were all zero blocks (standard ZFS functionality). But this is only a guess.
Sorry NTFS was a typo. I meant to say NFS mount as this is how I transferred the data. I am very new to ZFS so all this is very foreign to me.
What you say makes sense. It was a HDD, but it is very possible that it was mostly 0 as when I did a deepscan I found nothing to recover
When I do du image.dd it provides a much smaller value of 2GB for that file. So I should disregard what is displayed using ls -al and just trust the du value as it probably just a sparse file?
The sparse is done automatically by ZFS and I have no idea without researching it whether du can see this or not.