From: Chris Mason <chris.mason@oracle.com>
To: Konstantinos Skarlatos <k.skarlatos@gmail.com>
Cc: Linux Btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Having parent transid verify failed
Date: Thu, 05 May 2011 10:23:06 -0400 [thread overview]
Message-ID: <1304605365-sup-4172@think> (raw)
In-Reply-To: <4DC28DC4.7050308@gmail.com>
Excerpts from Konstantinos Skarlatos's message of 2011-05-05 07:45:08 -=
0400:
>=20
> On 5/5/2011 2:42 =CE=BC=CE=BC, Chris Mason wrote:
> > Excerpts from Konstantinos Skarlatos's message of 2011-05-05 07:19:=
52 -0400:
> >> Hello, I have a 5.5TB Btrfs filesystem on top of a md-raid 5 devic=
e. Now
> >> if i run some file operations like find, i get these messages.
> >> kernel is 2.6.38.5-1 on arch linux
> >
> > Are all of the messages for this one block?
> >
> > parent transid verify failed on 3062073683968 wanted 5181 found 518=
8
> yes, only this block
Ok, what were the call traces in there? Was there an oops or a hung
task? It looks like part of the messages are missing.
-chris
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-05-05 14:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-05 11:19 Having parent transid verify failed Konstantinos Skarlatos
2011-05-05 11:42 ` Chris Mason
2011-05-05 11:45 ` Konstantinos Skarlatos
2011-05-05 14:23 ` Chris Mason [this message]
[not found] ` <4DC2B3D2.6080307@gmail.com>
2011-05-05 15:06 ` Chris Mason
2011-05-05 16:07 ` Konstantinos Skarlatos
2011-05-05 20:27 ` Konstantinos Skarlatos
2011-05-05 20:32 ` Chris Mason
2011-05-05 21:04 ` Konstantinos Skarlatos
2011-05-05 23:50 ` Chris Mason
2011-05-06 0:01 ` Peter Stuge
2011-05-06 5:58 ` Konstantinos Skarlatos
2011-06-02 16:36 ` Johannes Hirte
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=1304605365-sup-4172@think \
--to=chris.mason@oracle.com \
--cc=k.skarlatos@gmail.com \
--cc=linux-btrfs@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 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.