Open mandree opened 8 years ago
Note that exfat-fuse (see reference above) sees a few more directories than exfat-nofuse, diff -u between sorted "find" results:
--- filelist-exfat-nofuse.txt 2016-07-18 20:32:20.900120100 +0200
+++ filelist-exfat-fuse.txt 2016-07-18 22:53:32.343360700 +0200
@@ -2311,8 +2311,108 @@
./DCIM/12760612/DSC02479.JPG
./DCIM/12760612/DSC02480.ARW
./DCIM/12760612/DSC02480.JPG
-./DCIM/12760612/DSC02481.A
+./DCIM/12760612/DSC02481.ARW
./DCIM/12760612/DSC02481.JPG
+./DCIM/12760612/DSC02482.ARW
[...]
+./DCIM/12760612/DSC02566.ARW
+./DCIM/12760612/DSC02566.JPG
./DCIM/13160619
./DCIM/13160619/DSC02605.ARW
./DCIM/13160619/DSC02605.ARW.xmp
@@ -2410,6 +2510,7 @@
./DCIM/13360622/DSC02717.JPG
./DCIM/13360622/DSC02719.JPG
./DCIM/13360622/DSC02721.JPG
+./DCIM/13460623
./DCIM/13560709
./DCIM/13560709/DSC02725.ARW
./DCIM/13560709/DSC02725.JPG
Possible missing changes to code to fully support linux 4.x.x If any dev with extended knowledge of 4.x.x filesystem changes from 3.x.x like to help with debug and fixes. i will be happy to merge changes. Otherwise consider this driver as not fully stable with latest linux kernel builds.
I think there are several issues I might have reported separately: One is an issue with the interpretation of the file system contents (that chkdsk and Windows 7 appear to find fair enough but that may be corrupted enough for Linux), and the other one with the module interface that prevents the forced kill of the umount or the forced module unload.
Please also see https://github.com/relan/exfat/issues/41 and https://github.com/relan/exfat/issues/42 which stem from the same file system about its interpretation.
So, exfat-fuse v1.2.5 has fixed these issues. How about the kernel driver?
This is the fix made in exfat-fuse binary... https://github.com/relan/exfat/commit/575ba4bca69096d5c795f466f2fdd4600a36fd4f can any one help to adapt this check to kernel driver? idea is to check if dir has valid start cluster, and see if empty files dont have any clusters.
Greetings,
I have a 64 GB SDXC card here (SanDisk) here that was written to with a Sony camera, Linux, and Windows. exfatfsck complains about 0-clusters in a certain directory, but Windows 7 SP1's "chkdsk I: /F" does not find anything worthy of repair or complaint.
Diffing the output of Cygwin find under Windows 7, and a find with exfat-nofuse kernel module yields several differences, one of them
I am getting this kernel log show below from "find". Unmounting the file system is not possible, umount hangs, and cannot be killed with SIGKILL. Trying to "rmmod -f exfat" also gets refused.
exfat-fuse (a different) project behaves in a similar way, but it does not show a broken file.
diff between cygwin find under Windows 7 and Linux find, only relevant parts shown.
kern.log: