linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Konstantinos Skarlatos <k.skarlatos@gmail.com>
To: Chris Mason <chris.mason@oracle.com>
Cc: Linux Btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Having parent transid verify failed
Date: Thu, 05 May 2011 19:07:43 +0300	[thread overview]
Message-ID: <4DC2CB4F.7060903@gmail.com> (raw)
In-Reply-To: <1304607926-sup-3304@think>



On 5/5/2011 6:06 =CE=BC=CE=BC, Chris Mason wrote:
> Excerpts from Konstantinos Skarlatos's message of 2011-05-05 10:27:30=
 -0400:
>> attached you can find the whole dmesg log. I can trigger the error a=
gain
>> if more logs are needed
>
> Yes, I'll send you a patch to get rid of the printk for the transid
> failed message.  That way we can get a clean view of the other errors=
=2E
>
> Will you be able to compile/test it?

Yes, i think i will be able to make it, but because i have only done=20
this once and in a quite hackish way, i may need some help in order to=20
do it right.

>
> -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

  reply	other threads:[~2011-05-05 16:07 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
     [not found]       ` <4DC2B3D2.6080307@gmail.com>
2011-05-05 15:06         ` Chris Mason
2011-05-05 16:07           ` Konstantinos Skarlatos [this message]
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=4DC2CB4F.7060903@gmail.com \
    --to=k.skarlatos@gmail.com \
    --cc=chris.mason@oracle.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 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).