From: Dave Chinner <david@fromorbit.com>
To: Sinisa <sinisa@4net.rs>
Cc: linux-raid@vger.kernel.org, linux-xfs@vger.kernel.org
Subject: Re: XFS and RAID10 with o2 layout
Date: Sat, 15 Dec 2018 08:20:22 +1100 [thread overview]
Message-ID: <20181214212022.GL6311@dastard> (raw)
In-Reply-To: <3e0e8def-2bb4-5e8a-56c1-d010ede059d4@4net.rs>
On Fri, Dec 14, 2018 at 08:03:36AM +0100, Sinisa wrote:
> On 12/13/18 11:05 PM, Dave Chinner wrote:
> >On Wed, Dec 12, 2018 at 01:29:49PM +0100, Sinisa wrote:
> >Basically, this looks and smells like a MD sync barrier race
> >condition, not an XFs problem.
>
> But why don't we see the same issue with other filesystems?
XFS has a lot more parallelism at the storage layer than other
filesystems and has a different integrity synchronisation model (via
IO completion processing rather than submission serialisation), so
it stresses the underlying storage very differently to other
filesystems.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2018-12-14 21:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-12 12:29 XFS and RAID10 with o2 layout Sinisa
2018-12-12 14:30 ` Brian Foster
2018-12-13 8:21 ` Sinisa
2018-12-13 12:28 ` Brian Foster
2018-12-13 13:02 ` Sinisa
2018-12-13 17:30 ` keld
2018-12-14 6:59 ` Sinisa
[not found] ` <0a33a20d-5f49-7b34-3662-5b818c67621a@suse.com>
[not found] ` <48ba331d-a896-f532-2c75-cf94ddf87b60@4net.rs>
2018-12-17 15:04 ` Sinisa
2018-12-18 15:01 ` Sinisa
2018-12-13 22:05 ` Dave Chinner
2018-12-14 7:03 ` Sinisa
2018-12-14 8:26 ` Wols Lists
2018-12-14 20:44 ` John Stoffel
2018-12-15 15:36 ` Siniša Bandin
2018-12-14 21:20 ` Dave Chinner [this message]
2018-12-14 11:39 ` Sinisa
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=20181214212022.GL6311@dastard \
--to=david@fromorbit.com \
--cc=linux-raid@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=sinisa@4net.rs \
/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.