Pascal via ntfs-3g-devel wrote:
Thank you. I can confirm the truncate trick works. Unfortunately, I
suspect I will end up with a heavily fragmented disk if I use truncate
to create 50,000 files and then ntfsfallocate to expand them all at
once.
No, applying truncate to a void file yields a
Thank you. I can confirm the truncate trick works. Unfortunately, I suspect I
will end up with a heavily fragmented disk if I use truncate to create 50,000
files and then ntfsfallocate to expand them all at once. It would be nice if
ntfsfallocate was able to create files too.
There is a wri
There is indeed a bug in ntfsfallocate when there is initially
no allocation at all.
In your example a possible workaround is to allocate a sparse
cluster after the touch ("truncate -s 4096 /12tb/test/6")
Of course, in a real situation you would have to insert a
test to avoid truncating valid data
I can't seem to get ntfsfallocate to do anything:
# mount /dev/sdq1 /12tb/
# ll /12tb/test/6
ls: cannot access /12tb/test/6: No such file or directory
# touch /12tb/test/6
# umount /12tb
# ntfsinfo -v /dev/sdq1 -F test/6 > 0
# ntfsfallocate -l 537308676 /dev/sdq1 test/6
ntfsfallocate v2017.3.23 (
