From: Vijay Chidambaram <vijay@cs.utexas.edu>
To: Dave Chinner <david@fromorbit.com>
Cc: Amir Goldstein <amir73il@gmail.com>,
Filipe Manana <fdmanana@kernel.org>,
fstests <fstests@vger.kernel.org>,
Linux Btrfs <linux-btrfs@vger.kernel.org>,
Filipe Manana <fdmanana@suse.com>
Subject: Re: [PATCH] generic: add test for fsync after shrinking truncate and rename
Date: Mon, 4 Mar 2019 19:08:05 -0600 [thread overview]
Message-ID: <CAHWVdUXMXtvncVQSqO8vdowct+GYE1nENePNvFJFjvoWzSHMcw@mail.gmail.com> (raw)
In-Reply-To: <20190305010031.GB26298@dastard>
On Mon, Mar 4, 2019 at 7:00 PM Dave Chinner <david@fromorbit.com> wrote:
>
> On Tue, Mar 05, 2019 at 11:50:20AM +1100, Dave Chinner wrote:
> > On Mon, Mar 04, 2019 at 05:04:23PM +0200, Amir Goldstein wrote:
> > > On Mon, Mar 4, 2019 at 4:44 PM <fdmanana@kernel.org> wrote:
> > > >
> > > > From: Filipe Manana <fdmanana@suse.com>
> > > >
> > > > Test that if we truncate a file to reduce its size, rename it and then
> > > > fsync it, after a power failure the file has a correct size and name.
> > > >
> > >
> > > I am not sure that ext4/xfs semantics guaranty anything about
> > > persisting file name after fsync of file?...
> >
> > They do. It's that pesky "strictly ordered metadata" thing I keep
> > having to explain to people...
>
> https://marc.info/?l=fstests&m=155010885626284&w=2
With reference to that previous conversation, Jayashree and I are
planning to submit a patch adding something like
Documentation/filesystems/crash-recovery.txt to document crash
guarantees and strictly ordered metadata semantics soon! So hopefully
there will be in-kernel documentation we can point folks to soon.
next prev parent reply other threads:[~2019-03-05 1:11 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-04 14:06 [PATCH] generic: add test for fsync after shrinking truncate and rename fdmanana
2019-03-04 15:04 ` Amir Goldstein
2019-03-04 15:23 ` Filipe Manana
2019-03-04 17:59 ` Amir Goldstein
2019-03-04 22:30 ` Filipe Manana
2019-03-05 5:59 ` Amir Goldstein
2019-03-05 9:26 ` Filipe Manana
2019-03-05 10:51 ` Amir Goldstein
2019-03-05 0:50 ` Dave Chinner
2019-03-05 1:00 ` Dave Chinner
2019-03-05 1:08 ` Vijay Chidambaram [this message]
2019-03-05 5:39 ` Amir Goldstein
2019-03-05 22:33 ` Dave Chinner
2019-03-06 7:51 ` Amir Goldstein
2019-03-06 21:48 ` Dave Chinner
2019-03-07 7:52 ` Amir Goldstein
2019-03-07 23:19 ` Jayashree Mohan
2019-03-08 4:35 ` Dave Chinner
2019-03-08 15:11 ` Vijay Chidambaram
2019-03-19 1:13 ` Dave Chinner
2019-03-08 3:46 ` Dave Chinner
2019-03-05 9:26 ` [PATCH v2] " fdmanana
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=CAHWVdUXMXtvncVQSqO8vdowct+GYE1nENePNvFJFjvoWzSHMcw@mail.gmail.com \
--to=vijay@cs.utexas.edu \
--cc=amir73il@gmail.com \
--cc=david@fromorbit.com \
--cc=fdmanana@kernel.org \
--cc=fdmanana@suse.com \
--cc=fstests@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.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 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.