linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel J Blueman <daniel.blueman@gmail.com>
To: Josef Bacik <josef@redhat.com>
Cc: Linux BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: [2.6.29-rc2] insert_dir_item hitting assertion during log replay
Date: Tue, 12 Apr 2011 00:07:20 +0800	[thread overview]
Message-ID: <BANLkTin7nYmOXcHjfS0s77s+-buQW-0cgQ@mail.gmail.com> (raw)
In-Reply-To: <4DA31F11.90200@redhat.com>

On 11 April 2011 23:32, Josef Bacik <josef@redhat.com> wrote:
> 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 mo=
unt?
> =A0Thanks,

I still have this fs, though it didn't panic at next mount. I guess
this creates a case for cooking a script that eg logically disconnects
a block device during activity (hdparm or echo 1 >delete) then
reconnects it for remount...let me know if interested.

Thanks,
  Daniel
--=20
Daniel J Blueman
--
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-04-11 16:07 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
2011-04-11 16:07   ` Daniel J Blueman [this message]
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=BANLkTin7nYmOXcHjfS0s77s+-buQW-0cgQ@mail.gmail.com \
    --to=daniel.blueman@gmail.com \
    --cc=josef@redhat.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).