From: Christoph Hellwig <hch@infradead.org>
To: Sage Weil <sage@inktank.com>
Cc: ceph-devel@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: v0.80.4 Firefly released
Date: Wed, 16 Jul 2014 02:22:26 -0700 [thread overview]
Message-ID: <20140716092226.GA23561@infradead.org> (raw)
In-Reply-To: <alpine.DEB.2.00.1407151634250.21336@cobra.newdream.net>
On Tue, Jul 15, 2014 at 04:45:59PM -0700, Sage Weil wrote:
> This Firefly point release fixes an potential data corruption problem
> when ceph-osd daemons run on top of XFS and service Firefly librbd
> clients. A recently added allocation hint that RBD utilizes triggers
> an XFS bug on some kernels (Linux 3.2, and likely others) that leads
> to data corruption and deep-scrub errors (and inconsistent PGs). This
> release avoids the situation by disabling the allocation hint until we
> can validate which kernels are affected and/or are known to be safe to
> use the hint on.
I've not really seen an report for that on the XFS list, could it be
that you're running into the issue fixed by
"xfs: Use preallocation for inodes with extsz hints"
(commit aff3a9edb7080f69f07fe76a8bd089b3dfa4cb5d)?
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next parent reply other threads:[~2014-07-16 9:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.DEB.2.00.1407151634250.21336@cobra.newdream.net>
2014-07-16 9:22 ` Christoph Hellwig [this message]
2014-07-16 17:26 ` v0.80.4 Firefly released Gregory Farnum
2014-07-16 22:31 ` Dave Chinner
2014-07-16 23:41 ` Samuel Just
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=20140716092226.GA23561@infradead.org \
--to=hch@infradead.org \
--cc=ceph-devel@vger.kernel.org \
--cc=sage@inktank.com \
--cc=xfs@oss.sgi.com \
/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