All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tomas Carnecky <tomas.carnecky@gmail.com>
To: "Yan, Zheng " <yanzheng@21cn.com>
Cc: Josef Bacik <josef@redhat.com>, linux-btrfs@vger.kernel.org
Subject: Re: Bug in btrfs_rename (kernel BUG at fs/btrfs/inode.c:5595!)
Date: Fri, 15 Jan 2010 00:59:12 +0100	[thread overview]
Message-ID: <4B4FAFD0.1070304@gmail.com> (raw)
In-Reply-To: <3d0408631001141220m5941ad58t91d01fb918daf8ab@mail.gmail.com>

On 01/14/2010 09:20 PM, Yan, Zheng wrote:
> It looks like a ENOSPC related problem, btrfs_truncate doesn't remove the orphan
> item if it fails to finish its operation. so I don't think this patch
> fixes the problem

Around the time when it happened, the filesystem was used only to ~55% 
(31G of 56G).

tom

      reply	other threads:[~2010-01-14 23:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-13 19:09 Bug in btrfs_rename (kernel BUG at fs/btrfs/inode.c:5595!) Tomas Carnecky
2010-01-13 20:13 ` Josef Bacik
2010-01-13 20:11   ` Tomas Carnecky
2010-01-14 17:03     ` Josef Bacik
2010-01-14 19:00       ` Josef Bacik
2010-01-14 20:20         ` Yan, Zheng 
2010-01-14 23:59           ` Tomas Carnecky [this message]

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=4B4FAFD0.1070304@gmail.com \
    --to=tomas.carnecky@gmail.com \
    --cc=josef@redhat.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=yanzheng@21cn.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 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.