All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josef Bacik <josef@redhat.com>
To: Daniel J Blueman <daniel.blueman@gmail.com>
Cc: Linux BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: [2.6.29-rc2] insert_dir_item hitting assertion during log replay
Date: Mon, 11 Apr 2011 11:32:33 -0400	[thread overview]
Message-ID: <4DA31F11.90200@redhat.com> (raw)
In-Reply-To: <BANLkTi=M5q6WbkgNMURWkBCi-46E6-UOkA@mail.gmail.com>

On 04/10/2011 04:29 AM, Daniel J Blueman wrote:
> When rebooting from a crash, thus during log replay on 2.6.29-rc2,
> btrfs_insert_dir_item caused an assertion failure [1]. The fs was
> being mounted clear_cache on an SSD.
>
> Probably it's not so easy to reproduce, but better to report it...
>

Do you still have this fs, and does it still panic the same way on 
mount?  Thanks,

Josef

  reply	other threads:[~2011-04-11 15:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-10  8:29 [2.6.29-rc2] insert_dir_item hitting assertion during log replay Daniel J Blueman
2011-04-11 15:32 ` Josef Bacik [this message]
2011-04-11 16:07   ` Daniel J Blueman
2011-05-08 13:36     ` Daniel J Blueman
2011-05-09 16:03       ` Josef Bacik
2011-05-31 15:37 ` [3.0-rc1] " Daniel J Blueman

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=4DA31F11.90200@redhat.com \
    --to=josef@redhat.com \
    --cc=daniel.blueman@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.