Thadeu Lima de Souza Cascardo <cascardo@xxxxxxxxxx> writes: >> Can you share the image somehow? And fsck (chkdsk, etc.) works without >> any complain? > > Checking the filesystem on Windows runs without any complains, but it turns the > directory into an useless lump of data. Without checking the filesystem, > creating and reading files from that directory works just fine. > > I tried to use gzip or xz to compress the very sparse filesystem image that I > got, but they made it larger on disk than it really was. So here is a script > and pieces of the filesystem that will create a sparse 8GB image. I tested a your image with some tweaks. Windows's chkdsk complains about "BADDIR" directory, and it was fixed by converting it to normal file. Probably, chkdsk thought that "BADDIR" got ATTR_DIR bit by corruption. IOW, Windows FATFS driver may accept this image, but Windows also think this image as corrupt, like chkdsk says. I think the app that make this should be fixed. Windows accepts more than linux though, it looks also think as corrupt. If we really want to accept this image, we have to change the fat driver without affecting good image. And your patch affects to good image, because that patch doesn't count directory correctly, so bad link count. Thanks. -- OGAWA Hirofumi <hirofumi@xxxxxxxxxxxxxxxxxx>
