linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Li Zefan <lizf@cn.fujitsu.com>
To: Marcus Sorensen <shadowsor@gmail.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: kernel BUG at fs/btrfs/delayed-inode.c:1693!
Date: Fri, 29 Jul 2011 13:42:20 +0800	[thread overview]
Message-ID: <4E32483C.4060708@cn.fujitsu.com> (raw)
In-Reply-To: <CALFpzo5MPj10Hkf2Peq3Zko9wE+DccxmS070S0VmRbFYEQk2pQ@mail.gmail.com>

Marcus Sorensen wrote:
> I too have run into this just today, file system is nearly fresh:
> 
> 
> ------------[ cut here ]------------
> kernel BUG at fs/btrfs/delayed-inode.c:1693!

I just sent out a patch to fix it, see:

[PATCH] Btrfs: reverse enough space for file clone

--
Li Zefan

  reply	other threads:[~2011-07-29  5:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-28 18:57 kernel BUG at fs/btrfs/delayed-inode.c:1693! Marcus Sorensen
2011-07-29  5:42 ` Li Zefan [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-07-26  7:51 Markus Suvanto
2011-07-26  7:57 ` cwillu
2011-07-26  8:01   ` Markus Suvanto

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=4E32483C.4060708@cn.fujitsu.com \
    --to=lizf@cn.fujitsu.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=shadowsor@gmail.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;
as well as URLs for NNTP newsgroup(s).