Hi, I have finished upgrading fuse-lite (just copying code from full fuse), and your proposal can now be used with both variants of fuse. I have also adapted your code for use with lowntfs-3g (no code sharing yet).
Also you needed to hack the conflicting definitions in <sys/mount.h> and <linux/fs.h>. This can be solved cleanly by simply not including <sys/mount.h> in volume.h. When needed, <sys/mount.h> is already included in *.c, so no other change is needed (on Linux and Solaris). Regards Jean-Pierre Richard W.M. Jones wrote: > On Tue, Jul 08, 2014 at 03:22:31PM +0200, Jean-Pierre André wrote: >> Richard W.M. Jones wrote: >>> Now copy data to the filesystem and issue an fstrim command, and the >>> underlying loop file should become sparse: >> ... if the underlying fs supports a BLKDISCARD ioctl requests, >> which is not the case for NTFS... > Right, although that would be a little bit strange & rare! > > More commonly you'll be using ntfs-3g backed by a block device (I just > used a loopback because it's very convenient for testing). If you > look at: > > /sys/block/<device_name>/queue/discard* > > you can see if discard is supported by your block device. IIRC > discard_max_bytes must be > 0 for TRIM to be supported at all by the > block device. > > Thanks for the review, I'll see what I can do in a few days. > > Rich. > ------------------------------------------------------------------------------ Infragistics Professional Build stunning WinForms apps today! Reboot your WinForms applications with our WinForms controls. Build a bridge from your legacy apps to the future. http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk _______________________________________________ ntfs-3g-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ntfs-3g-devel
