All of lore.kernel.org
 help / color / mirror / Atom feed
From: Les Mikesell <lesmikesell@gmail.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] fsync() and LVM
Date: Mon, 16 Mar 2009 16:53:30 -0500	[thread overview]
Message-ID: <49BECA5A.3040407@gmail.com> (raw)
In-Reply-To: <87f94c370903161436y40eddb3pe162bfa64a90e371@mail.gmail.com>

Greg Freemyer wrote:
>>> I haven't seen anyone claim yet that there is support for fsync(), which
>> must return the status of the completion of the operation to the
>> application.  If it does, then the discussion could turn to performance.
>> 
> Is your specific interest to ext3?

No, it is whether a useful fsync() is possible over LVM.

> If so, I suggest you post a
> question there along the lines of:
> 
> Device Mapper does not support barriers if more than one physical
> device is in use by the LV.  If I'm using ext3 on a LV and I call
> fsync() from user space, how is fsync() implemented.  Or is it not?

The point of fsync() is for an application to know that a write has been 
safely committed, as for example sendmail would do before acknowledging 
to the sender that a message has been accepted.  The question isn't 
whether an application can call fsync() but rather whether it's return 
status is lying, making the underlying storage unsuitable for anything 
that needs reliability.

-- 
   Les Mikesell
    lesmikesell@gmail.com

  reply	other threads:[~2009-03-16 21:53 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-13 17:46 [linux-lvm] fsync() and LVM Marco Colombo
2009-03-13 20:08 ` 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 [this message]
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=49BECA5A.3040407@gmail.com \
    --to=lesmikesell@gmail.com \
    --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.