From: Richard Weinberger <richard@nod.at>
To: JH <jupiter.hce@gmail.com>
Cc: Richard Weinberger <richard.weinberger@gmail.com>,
linux-mtd <linux-mtd@lists.infradead.org>
Subject: Re: A big issue of NAND fragmentation
Date: Fri, 6 Sep 2019 09:02:06 +0200 (CEST) [thread overview]
Message-ID: <131148461.92686.1567753326360.JavaMail.zimbra@nod.at> (raw)
In-Reply-To: <CAA=hcWT0=ny6hxDgxZVTU6jbAYS80nizw3+PVVWzgW6poXuMwQ@mail.gmail.com>
----- Ursprüngliche Mail -----
> Von: "JH" <jupiter.hce@gmail.com>
> An: "Richard Weinberger" <richard.weinberger@gmail.com>
> CC: "linux-mtd" <linux-mtd@lists.infradead.org>
> 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.
Thanks,
//richard
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2019-09-06 7:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-05 1:27 A big issue of NAND fragmentation JH
2019-09-05 11:54 ` Richard Weinberger
2019-09-06 6:03 ` JH
2019-09-06 7:02 ` Richard Weinberger [this message]
2019-09-06 11:18 ` JH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=131148461.92686.1567753326360.JavaMail.zimbra@nod.at \
--to=richard@nod.at \
--cc=jupiter.hce@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=richard.weinberger@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.