From: "Figo.zhang" <figo1802@gmail.com>
To: NeilBrown <neilb@suse.de>
Cc: "Artem S. Tashkinov" <t.artem@lycos.com>,
david@lang.hm, lkml <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-fsdevel@vger.kernel.org, axboe@kernel.dk,
Linux-MM <linux-mm@kvack.org>
Subject: Re: Disabling in-memory write cache for x86-64 in Linux II
Date: Tue, 5 Nov 2013 09:40:55 +0800 [thread overview]
Message-ID: <CAF7GXvpJVLYDS5NfH-NVuN9bOJjAS5c1MQqSTjoiVBHJt6bWcw@mail.gmail.com> (raw)
In-Reply-To: <20131026091112.241da260@notabene.brown>
[-- Attachment #1: Type: text/plain, Size: 882 bytes --]
> >
> > Of course, if you don't use Linux on the desktop you don't really care -
> well, I do. Also
> > not everyone in this world has an UPS - which means such a huge buffer
> can lead to a
> > serious data loss in case of a power blackout.
>
> I don't have a desk (just a lap), but I use Linux on all my computers and
> I've never really noticed the problem. Maybe I'm just very patient, or
> maybe
> I don't work with large data sets and slow devices.
>
> However I don't think data-loss is really a related issue. Any process
> that
> cares about data safety *must* use fsync at appropriate places. This has
> always been true.
>
> =>May i ask question that, some like ext4 filesystem, if some app motify
the files, it create some dirty data. if some meta-data writing to the
journal disk when a power backout,
it will be lose some serious data and the the file will damage?
[-- Attachment #2: Type: text/html, Size: 1204 bytes --]
next prev parent reply other threads:[~2013-11-05 1:40 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-25 7:25 Artem S. Tashkinov
2013-10-25 8:18 ` Linus Torvalds
2013-11-05 0:50 ` Andreas Dilger
2013-11-05 4:12 ` Dave Chinner
2013-11-07 13:48 ` Jan Kara
2013-11-11 3:22 ` Dave Chinner
2013-11-11 19:31 ` Jan Kara
2013-11-05 6:32 ` Figo.zhang
2013-10-25 10:49 ` NeilBrown
2013-10-25 11:26 ` David Lang
2013-10-25 18:26 ` Artem S. Tashkinov
2013-10-25 19:40 ` Diego Calleja
2013-10-25 23:32 ` Fengguang Wu
2013-11-15 15:48 ` Diego Calleja
2013-10-25 20:43 ` NeilBrown
2013-10-25 21:03 ` Artem S. Tashkinov
2013-10-25 22:11 ` NeilBrown
2013-11-05 1:40 ` Figo.zhang [this message]
2013-11-05 1:47 ` David Lang
2013-11-05 2:08 ` NeilBrown
2013-10-29 20:49 ` Jan Kara
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=CAF7GXvpJVLYDS5NfH-NVuN9bOJjAS5c1MQqSTjoiVBHJt6bWcw@mail.gmail.com \
--to=figo1802@gmail.com \
--cc=axboe@kernel.dk \
--cc=david@lang.hm \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=neilb@suse.de \
--cc=t.artem@lycos.com \
--cc=torvalds@linux-foundation.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox