relan
relan
> Do you want to see if the patched, non-blkdev mount.exfat will crash given enough repetitions? Yes, I'd like to confirm that the file descriptor has not been closed after...
fuse-exfat doesn't try to sort entries in any way. When it creates a new entry in a directory it allocates the first suitable slot. But fuse-exfat also maintains a per-directory...
Exactly. So, this issue is about making entries order stable across mounts, right? This can be achieved in two ways: 1. Look up a proper place in the list when...
> Is there some means to bypass this warning and mount anyways? I understand the disk is much larger than the file system, but I'd still like to mount and...
You are right, fuse-exfat never supported anything but UTF-8 (iocharset option is ignored). It would indeed be nice if someone implemented support for other encodings. :)
It used to be an error, but several users with buggy cameras were unhappy with that: https://github.com/relan/exfat/commit/fcba4d92e7a78feb263f8ee0374ec5277341cdd3
fsck should probably mark clusters beyond the end as bad. This way, the warning can be turned into an error again.
> After tracking the code, it seem the directory node are all in cache allocated. However, it would release only at unmount phase. Your analysis is correct. This issue existed...
Looks like there's no way to handle O_SYNC in FUSE.
exFAT does not support short names by design. What problem are you trying to solve?