From: Frank van Maarseveen <frankvm@xs4all.nl>
To: "Richard B. Johnson" <root@chaos.analogic.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Memory mapped files question
Date: Mon, 14 Apr 2003 22:27:41 +0200 [thread overview]
Message-ID: <20030414202741.GA26414@iapetus.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.53.0304141559140.28851@chaos>
On Mon, Apr 14, 2003 at 04:13:52PM -0400, Richard B. Johnson wrote:
>
> Memory mapped files are supposed to be accessed through memory!
> Any program that needs to know what's on the physical disk is
> broken. If you need to write to files and know when they are
> written to the physical media, you use a journaled file-system.
It is not that simple.
Shared mmaped files are _never_ flushed, at least in 2.4.x. So,
without an explicit msync() a process (innd comes to mind) may loose
years of updates upon a system crash or power outage.
I have learned to live with it but I still find this a bit awkward.
--
Frank
next prev parent reply other threads:[~2003-04-14 20:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-14 19:31 Perez-Gonzalez, Inaky
2003-04-14 19:42 ` Bryan Shumsky
2003-04-14 19:53 ` Alan Cox
2003-04-14 21:24 ` Chris Friesen
2003-04-14 20:13 ` Richard B. Johnson
2003-04-14 20:27 ` Frank van Maarseveen [this message]
2003-04-14 20:52 ` Richard B. Johnson
2003-04-14 22:08 ` H. Peter Anvin
2003-04-15 4:56 ` Jamie Lokier
2003-04-15 5:30 ` H. Peter Anvin
-- strict thread matches above, loose matches on Subject: below --
2003-04-14 19:50 Perez-Gonzalez, Inaky
2003-04-14 3:57 Bryan Shumsky
2003-04-14 14:36 ` Martin J. Bligh
2003-04-14 15:07 ` Antonio Vargas
2003-04-14 15:04 ` Martin J. Bligh
2003-04-14 18:07 ` H. Peter Anvin
2003-04-14 20:39 ` Chris Friesen
2003-04-14 21:12 ` H. Peter Anvin
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=20030414202741.GA26414@iapetus.localdomain \
--to=frankvm@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®