public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Emmanuel Florac <eflorac@intellique.com>
To: Emmanuel Florac <eflorac@intellique.com>
Cc: Sascha Askani <saskani@inovex.de>, xfs@oss.sgi.com
Subject: Re: Weird XFS Corruption Error
Date: Thu, 23 Jan 2014 15:29:35 +0100	[thread overview]
Message-ID: <20140123152935.0f555074@harpe.intellique.com> (raw)
In-Reply-To: <20140123151943.281baa04@harpe.intellique.com>


[-- Attachment #1.1: Type: text/plain, Size: 1308 bytes --]

Le Thu, 23 Jan 2014 15:19:43 +0100
Emmanuel Florac <eflorac@intellique.com> écrivait:

> OTOH it looks really similar to an older bug :
> 
> http://oss.sgi.com/archives/xfs/2013-02/msg00482.html
> 
> AFAIK this one could be related to the current Ubuntu LTS lvm stack...
> We need Dave's advice on this one.
> 

Yes, I guess we're getting closer:
https://www.redhat.com/archives/dm-devel/2013-February/msg00113.html

"It's reproducable on lots of different kernels, apparently - 3.8,
3.4.33, CentOS 6.3, debian sid/wheezy and Fedora 18 were mentioned
specifically by the OP - so it doesn't look like a recent
regression or constrained to a specific kernel."

And
https://www.redhat.com/archives/dm-devel/2013-February/msg00122.html :

"Was issue_discards enabled in lvm.conf?

If so, as Alasdair said, this lvm2 2.02.97 fix is needed:
http://git.fedorahosted.org/cgit/lvm2.git/commit/?id=07a25c249b3e "


What is the version of lvm ( dpkg -l lvm2 )?


-- 
------------------------------------------------------------------------
Emmanuel Florac     |   Direction technique
                    |   Intellique
                    |	<eflorac@intellique.com>
                    |   +33 1 78 94 84 02
------------------------------------------------------------------------

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

[-- Attachment #2: Type: text/plain, Size: 121 bytes --]

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2014-01-23 14:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-22 16:09 Weird XFS Corruption Error Sascha Askani
2014-01-22 23:31 ` Dave Chinner
2014-01-24  7:56   ` Sascha Askani
2014-01-24 21:52     ` Dave Chinner
2014-01-23 14:19 ` Emmanuel Florac
2014-01-23 14:29   ` Emmanuel Florac [this message]
2014-01-24  8:08   ` Sascha Askani

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=20140123152935.0f555074@harpe.intellique.com \
    --to=eflorac@intellique.com \
    --cc=saskani@inovex.de \
    --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