From: Roman Mamedov <rm@romanrm.ru>
To: Jason Tinker <jsntinker@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Incompatibility of internal bitmap with ext4 barriers?
Date: Tue, 17 May 2011 19:17:46 +0600 [thread overview]
Message-ID: <20110517191746.556b10fa@natsu> (raw)
In-Reply-To: <BANLkTin9h+feRNWg1pWFq1t6dmBpn9keKw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 934 bytes --]
On Tue, 17 May 2011 16:10:07 +0400
Jason Tinker <jsntinker@gmail.com> wrote:
> I have encountered a weird bug when trying to use ext4 partition on
> top of mdadm RAID5 array. Mdadm array has internal bitmap, and ext4 is
> mounted with default options - which means that barriers are enabled.
The same combination works perfectly for me on 2.6.38.
> When trying to write large enough amount of files system just locks up
> indefinitely, only hard reset helps. This seems to happen at random
> times, yet consistently after several minutes of usage.
> I tried different configuration options and it seems to happen only
> when both barriers on ext4 and mdadm's internal bitmaps are enabled.
> After disabling ext4 barriers for good (it seemed like a lesser evil)
> no lock ups happened for 3 months.
> Mdadm is version 3.1.3, kernel is 2.6.32 (rhel6)
How about a newer kernel, maybe?
--
With respect,
Roman
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-05-17 13:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-17 12:10 Incompatibility of internal bitmap with ext4 barriers? Jason Tinker
2011-05-17 13:17 ` Roman Mamedov [this message]
2011-05-17 18:43 ` Jason Tinker
2011-05-17 19:00 ` Roman Mamedov
2011-05-17 20:20 ` John Robinson
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=20110517191746.556b10fa@natsu \
--to=rm@romanrm.ru \
--cc=jsntinker@gmail.com \
--cc=linux-raid@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;
as well as URLs for NNTP newsgroup(s).