All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Jayashree <jaya@cs.utexas.edu>
Cc: fstests@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	linux-doc@vger.kernel.org, vijay@cs.utexas.edu,
	amir73il@gmail.com, tytso@mit.edu, fdmanana@gmail.com,
	chao@kernel.org
Subject: Re: [PATCH] Documenting the crash-recovery guarantees of Linux file systems
Date: Wed, 6 Mar 2019 16:07:05 +1100	[thread overview]
Message-ID: <20190306050705.GB23020@dastard> (raw)
In-Reply-To: <1551841140-3708-1-git-send-email-jaya@cs.utexas.edu>

On Tue, Mar 05, 2019 at 08:59:00PM -0600, Jayashree wrote:
>  In this file, we document the crash-recovery guarantees
>  provided by four Linux file systems - xfs, ext4, F2FS and btrfs. We also
>  present Dave Chinner's proposal of Strictly-Ordered Metadata Consistency
>  (SOMC), which is provided by xfs. It is not clear to us if other file systems
>  provide SOMC; we would be happy to modify the document if file-system
>  developers claim that their system provides (or aims to provide) SOMC.

I haven't had time to read this yet, but I will point out that
fstests assumes that filesystems that run
"_require_metadata_journaling" tests present SOMC semantics to
users. i.e. we are not testing POSIX semantics in fstests, we are
testing for SOMC crash-recovery semantics because POSIX does not
define a useful set of semantics.

That was the whole point of genericising that test infrastructure -
to make sure all the linux journalling filesystems behave the same
way in the same circumstances...

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

  parent reply	other threads:[~2019-03-06  5:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-06  2:59 [PATCH] Documenting the crash-recovery guarantees of Linux file systems Jayashree
2019-03-06  3:26 ` Randy Dunlap
2019-03-06  5:07 ` Dave Chinner [this message]
2019-03-06  9:14 ` Amir Goldstein
     [not found]   ` <CA+EzBbD9S6JN861H+5HRBbh_uSfo=1bCR4-NvnFmD1N2qw2h7g@mail.gmail.com>
2019-03-12 13:13     ` Chao Yu
2019-03-12 13:13       ` Chao Yu

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=20190306050705.GB23020@dastard \
    --to=david@fromorbit.com \
    --cc=amir73il@gmail.com \
    --cc=chao@kernel.org \
    --cc=fdmanana@gmail.com \
    --cc=fstests@vger.kernel.org \
    --cc=jaya@cs.utexas.edu \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=tytso@mit.edu \
    --cc=vijay@cs.utexas.edu \
    /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.