Sorry for asking this problem at here. But since NTFS-3g is a NTFS driver. Maybe some programmer can help me.

It is about compression file.
If a run is not less than 16 clusters, the run is a un-compressed run, all data in run is original data.
I created a text file in NTFS volume. and set it as a compressed file by binary editor(without calling API, just modified the disk data). And write a run streams as follows:

21 15 10 11 11 04 15 11 05 04 11 10 05 11 02 10
And The original run stream is
21 7f 10 11

I flushed data,
and unmount volume,
and re-mount it,
run chkdsk -- it shows volume is ok except some volume bitmap problem.
and I open the file with notepad, all data are text data(original data before I change the file to compressed).
So my problem is :
If I have 3 compressed units with run stream:
21 15 10 05 11 06 15 11 08 06 11 0d 08
Whether all 3 compressed units should be un-compressed data or it just a bug of Windows NTFS driver?

Hi,


This does not look like compressed data, and I cannot tell whose bug, if any, a sequence of 13 bytes out of nowhere could be.

Regards

Jean-Pierre

The Windows driver will not generate this run stream, and I think NTFS3g will not too.
But I generate this run stream by WinHEX, The Windows driver can access this file.

Hi,


So everything is ok.

Regards

Jean-Pierre