Lines Matching refs:t
53 Filesystems that don't take wear into account can easily burn through blocks
56 1. **Bounded RAM/ROM** - If the above requirements weren't enough, these
128 appends. And if that wasn't good enough, their cyclic nature means that
221 problems. Because updates to a COW filesystem don't stop until they've
239 can't avoid these costs, _but_ if we put an upper bound on the size we can at
245 Let's say that our COW structure doesn't copy after a single write, but instead
246 copies after _n_ writes. This doesn't change most COW properties (assuming you
314 metadata pair independently, and we don't reduce our block granularity for
359 we don't overwrite the original entries (remember rewriting flash requires
381 Note that littlefs doesn't maintain a checksum for each entry. Many logging
441 3. If our block is full of entries _and_ we can't find any garbage, then what?
444 isn't really an error condition.
726 doesn't need to touch the disk, so the practical impact is minimal.
755 Unfortunately, the popcount function is non-injective, so we can't solve this
853 resilience, keeping these structures consistent becomes difficult. It doesn't
903 works well because bitmaps are surprisingly compact. We can't use the same
973 Recovery from bad blocks doesn't actually have anything to do with the block
1173 cycle we'll eventually find a new block where a write succeeds. If we don't,
1182 Read errors, on the other hand, are quite a bit more complicated. We don't have
1239 means is that we don’t actively track wear, instead we rely on a uniform
1247 The harder part is what to do when the device loses power. We can't just
1334 However, this doesn't work well when files are small, which is common for
1483 store an unlimited number of files in each directory, and we don't need to
1513 [RAM]. The directory tree is a tree, and the unfortunate fact is you can't
1823 In littlefs we can atomically commit to directories, but we can't create
1833 - We definitely can't just let power-loss result in duplicated or lost files.
1836 it isn't user facing and we can handle the corner cases internally.
1913 the global state to its initial value, we can't easily clean up the deltas on
2029 fine as the order doesn't really matter.