You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi! Thanks to this great crate, my OS supported FAT32 file system in 1 day. But today, when I was trying to read a user program from the disk, I found out that the read function of the file structure only reads the current cluster. Then I read the source code, and I also found out that the write function does the same thing. It only writes the current cluster. I thought that my builder program uses this crate as well, but it works pretty good. I checked it. Then I found the reason. It uses the core::io::copy function. To read my user program from my disk, I had to seek every time I read a cluster. It's so cumbersome. Could you please fix this bug?
The text was updated successfully, but these errors were encountered:
zzjrabbit
changed the title
The Read and Write Function of the File Structure Only Reads the Current Cluster
The Read and Write Function of the File Structure Only Reads or Writes the Current Cluster
Jul 21, 2024
Are you talking about the necessity to seek to the beginning of a partition before opening a filesystem (FileSystem::new)? If not could you provide an example code that demonstrates the problem?
Hi! Thanks to this great crate, my OS supported FAT32 file system in 1 day. But today, when I was trying to read a user program from the disk, I found out that the read function of the file structure only reads the current cluster. Then I read the source code, and I also found out that the write function does the same thing. It only writes the current cluster. I thought that my builder program uses this crate as well, but it works pretty good. I checked it. Then I found the reason. It uses the core::io::copy function. To read my user program from my disk, I had to seek every time I read a cluster. It's so cumbersome. Could you please fix this bug?
The text was updated successfully, but these errors were encountered: