All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marco Colombo <linux-lvm@esiway.net>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: [linux-lvm] fsync() and LVM
Date: Fri, 13 Mar 2009 18:46:33 +0100	[thread overview]
Message-ID: <49BA9BF9.3070507@esiway.net> (raw)

Hi, I'm a long time user of both PostgreSQL and LVM. So far I've been quite
happy with both. But a recent thread on the PostgreSQL list made me
unconfortable. What is this thing they're referring to, fsync()'s being
ignored? Makes me feel like I'm running on thin ice, without even
knowing. Before I start phasing out LVM from all my PostgreSQL installations
(as they suggest), I'd like to hear some kind of confirmation.
This is quite scary.

http://archives.postgresql.org/pgsql-general/2009-03/msg00204.php

In my understanding:

fsync():  force data from OS memory to disk (ending up in the disk cache)
write barrier: force data from disk cache to disk platters

If you disable write-back cache on the disks, you no longer need write
barriers. But apparently they claim LVM being unsafe even with disks
caches in write-thru mode, which surprises me a lot.

.TM.

             reply	other threads:[~2009-03-13 17:47 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-13 17:46 Marco Colombo [this message]
2009-03-13 20:08 ` [linux-lvm] fsync() and LVM Stuart D. Gathman
2009-03-13 20:29   ` Ben Chobot
2009-03-13 20:38   ` Alasdair G Kergon
2009-03-14  3:16     ` Marco Colombo
2009-03-14  9:07     ` Dietmar Maurer
2009-03-14 14:31       ` Stuart D. Gathman
2009-03-15  0:51         ` Marco Colombo
2009-03-16 11:02           ` Charles Marcus
2009-03-16 11:05             ` Martin Schröder
2009-03-16 11:18               ` Charles Marcus
2009-03-16 11:25                 ` Dietmar Maurer
2009-03-16 14:36             ` Marco Colombo
2009-03-16 17:13               ` Stuart D. Gathman
2009-03-16 17:17           ` Stuart D. Gathman
2009-03-16 18:50             ` Les Mikesell
2009-03-16 19:36               ` Greg Freemyer
2009-03-16 19:55                 ` [linux-lvm] liblvm status question ben scott
2009-03-16 20:58                   ` Greg Freemyer
2009-03-17 10:38                     ` Bryn M. Reeves
2009-03-17 18:42                       ` ben scott
2009-03-17 20:52                       ` Greg Freemyer
2009-03-16 20:28                 ` [linux-lvm] fsync() and LVM Les Mikesell
2009-03-16 20:54                   ` Greg Freemyer
2009-03-16 21:17                     ` Les Mikesell
2009-03-16 21:36                       ` Greg Freemyer
2009-03-16 21:53                         ` Les Mikesell
2009-03-16 22:51                           ` Joshua D. Drake
2009-03-17 15:33                             ` Joshua D. Drake
2009-03-19  9:20                               ` Tim Post
2009-03-16 21:57                         ` Allen, Jack
2009-03-17 16:00             ` Marco Colombo
2009-03-17 17:40               ` Stuart D. Gathman
2009-03-17 18:17                 ` Les Mikesell
2009-03-18  0:37                   ` Marco Colombo
2009-03-15  8:51         ` Dietmar Maurer
2009-03-15 23:31           ` Marco Colombo
2009-03-17 18:12           ` Les Mikesell
2009-03-17 18:19             ` Dietmar Maurer

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=49BA9BF9.3070507@esiway.net \
    --to=linux-lvm@esiway.net \
    --cc=linux-lvm@redhat.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.