On Tue, Aug 27, 2013 at 02:00:23PM +0200, Jean-Pierre André wrote:
[snip]
>
> I found that Windows behaves badly when writing to files which have
> preallocated clusters not written to, it may :
>
> - deallocate the clusters not written to,
> - loop to no end,
> - or crash (BSOD)
>
> This could be a bug in Windows, as chkdsk makes no changes and does not
> complain about hidden preallocated clusters with no meaningful data.
>
> ntfs-3g however behaves fine when using preallocated clusters.
>
Hi,
Thanks for the heads up. I have been testing the fallocate and found
that the "Initialized size" is 0:
$ sudo ntfsinfo -F test /dev/sdf1
...
Dumping attribute $DATA (0x80) from mft record 64 (0x40)
Resident: No
Attribute flags: 0x0000
Attribute instance: 2 (0x2)
Compression unit: 0 (0x0)
Data size: 4294967296 (0x100000000)
Allocated size: 4294967296 (0x100000000)
Initialized size: 0 (0x0)
End of inode reached
Thus, when I try to write to it using the ntfs kernel driver. I get the
following:
[ 661.132777] NTFS-fs error (device sdf1): ntfs_write_block(): Writing beyond
initialized size is not supported yet. Sorry.
Is this the expected behavior?
Thanks,
Amit
------------------------------------------------------------------------------
Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies
and advance your career. Get an incredible 1,500+ hours of step-by-step
tutorial videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk
_______________________________________________
ntfs-3g-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ntfs-3g-devel
