public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Siniša Bandin" <sinisa@4net.rs>
To: linux-raid@vger.kernel.org, linux-xfs@vger.kernel.org,
	linux-raid-owner@vger.kernel.org
Subject: Re: XFS and RAID10 with o2 layout
Date: Sat, 15 Dec 2018 16:36:10 +0100	[thread overview]
Message-ID: <1a5643d5f68d3dfe1aaa472aac6bd398@4net.rs> (raw)
In-Reply-To: <23572.5681.810087.381496@quad.stoffel.home>



On 14.12.2018 21:44, John Stoffel wrote:
>>>>>> "Wols" == Wols Lists <antlists@youngman.org.uk> writes:
> 
> Wols> On 14/12/18 07:03, Sinisa wrote:
>>>> And another MD flush thread waiting on a MD sync barrier.
>>>> 
>>>> Basically, this looks and smells like a MD sync barrier race
>>>> condition, not an XFs problem.
>>>> 
>>>> Cheers,
>>>> 
>>>> Dave.
>>> 
>>> But why don't we see the same issue with other filesystems?
> 
> Wols> Possibly because, iirc, xfs is aware of the underlying raid?
> 
> I don't think it's that in touch with the raid.  It can/does query for
> settings so it can optimize stuff, but I don't think it actually uses
> it other than as a block device.
> 
> Wols> I don't know, but I seem to remember that from earlier 
> discussions about
> Wols> "xfs over mdraid".
> 
> Have you tried doing this with the absolute latest kernel?

Well, not "absolute" but relative :)

Absolute latest being 4.20-rc6, I have tried with 4.20-rc2 or -rc3


-- 
Srdačan pozdrav/Best regards,
Siniša Bandin

  reply	other threads:[~2018-12-15 15:36 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 [this message]
2018-12-14 21:20     ` Dave Chinner
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=1a5643d5f68d3dfe1aaa472aac6bd398@4net.rs \
    --to=sinisa@4net.rs \
    --cc=linux-raid-owner@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=linux-xfs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox