Changes between Initial Version and Version 1 of Ticket #10336, comment 58


Ignore:
Timestamp:
Jan 17, 2021, 1:43:59 PM (4 years ago)
Author:
pulkomandy

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #10336, comment 58

    initial v1  
    4444I have annotated a line with {{{***}}}. As you can see, BFS tries to read at an offset that was erased by the trimming. So it looks like there indeed is a problem in the BFS code or in the partitionning system manager (which I understand should translate BFS requests into offsets on the raw disk). The trimming seems to have worked: the data is no longer there, and BFS fails to mount the partition.
    4545
    46 I will make tests with smaller partitions to see if I can more easily analyze what's going on.
     46Then I made a test with 4 smaller partitions on the SD card, and ran fstrim on each of them. For all 4 of them, fstrim ends up erasing data about 4MB into the disk (so it always start erasing data that's in the first partition). It really looks like the partition start offset isn't taken into account?