Re: A big issue of NAND fragmentation

[JH <jupiter.hce@xxxxxxxxx>]

On 9/6/19, Richard Weinberger <richard@xxxxxx> wrote:
> ----- Ursprüngliche Mail -----
>> Von: "JH" <jupiter.hce@xxxxxxxxx>
>> An: "Richard Weinberger" <richard.weinberger@xxxxxxxxx>
>> CC: "linux-mtd" <linux-mtd@xxxxxxxxxxxxxxxxxxx>
>> Gesendet: Freitag, 6. September 2019 08:03:55
>> Betreff: Re: A big issue of NAND fragmentation
>>
>> Yes, I use UBIFS, was your word "force" means "write" or did you
>> allude there would be an alternative to avoid forcing UBIFS persist
>> 250 bytes?
>>
>> Waiting for out of space would be too risk, alternatively, I should
>> have a UBIFS partition for the data storage, if it runs out of space,
>> it won't impact the root file system.
>>
>
> No, by force I mean forcing the filesystem to persist the data.
> For example by using fsync(),fdatasync(), O_SYNC or a sync mounted
> filesystem.
> If you don't do this, data will be cached and can be packed
> later upon write-back.

I use std::ofstream and operator<<, it does have a flush but I don't
know if the flush is a default setting or not, but obviously it is
default which caused fragmentation. More work to do, might be better
to use an old simple C write.

Thanks for the explanation.

- jupiter

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/