relan

It's a good idea to mention other implementations. But > If you are using the exFAT kernel driver you should use [exfatprogs][14] instead of exfat-utils. why? Any exFAT driver should...

Thanks for your effort! This is a useful tool indeed, but your code needs some improvements: 1. The coding style should match the rest of the project. 2. There should...

Thanks for the patch! You mean the POSIXLY_CORRECT case, right? A user can call mount.exfat-fuse directly and is in full right to put device and mountpoint after other options. Your...

> plug out it from PC when do write operation，and then this issue is occurred，fsck.exfat can find this issue but can not fix this issue, is there some advices of...

> I can see V1.3.0 can repair some errors, do u have a method to repair this issue? Not this one. > we hope have a repair method on Linux...

> is there a manual solution possible here? You can try to zero out the offending entries. Look for 0x85 followed by 0x48. > What does 1/150 refer to? The...

> My issue is that I only found this byte combination within what looked like data, how would I locate it? Get the source code, remove [this line](https://github.com/relan/exfat/blob/master/fsck/main.c#L29), compile fsck...

Looks like SELinux-related options just need to be passed through to fuse: https://github.com/libfuse/libfuse/commit/9448849b568bf430950463fb70dab81a139b29bd

> How can this problem be resolved? This may be solved by compiling fuse-exfat with profiling enabled, gathering the profile data under your workload and analyzing it :)

Looks like `bmap` and `ioctl` FUSE ops should be implemented for this. Need more research. > But how to figure out what blocks are free or not? There's clusters bitmap...