From: David Sterba <dave@jikos.cz>
To: dima <dolenin@parallels.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Corrupt file in subvolume
Date: Mon, 10 Oct 2011 13:29:17 +0200 [thread overview]
Message-ID: <20111010112917.GG17912@twin.jikos.cz> (raw)
In-Reply-To: <loom.20111010T124733-121@post.gmane.org>
On Mon, Oct 10, 2011 at 11:03:34AM +0000, dima wrote:
> The last shutdown was clean, but I had to powercycle several times this month.
> I am also mounting a swapfile via loop device, so maybe this also adds up to
> instability.
>
> The corrupt file is a firefox source file
> (mozilla-central/js/src/tests/e4x/XML/13.4.4.40.js). Interesting thing that I
> did not touch this file or rebuild firefox for about 3-4 days, so I do not have
> any idea why it got corrupted suddenly.
>
> When trying to remove the directory containing this file I am getting:
>
> Oct 10 14:03:13 yukikaze kernel: [ 9836.993172] ------------[ cut here
> ]------------
> Oct 10 14:03:13 yukikaze kernel: [ 9836.993261] kernel BUG at
> fs/btrfs/inode.c:3024!
fixed by:
commit b532402e4d147e4f409c4e7f50d4413e8450101d
Author: Tsutomu Itoh <t-itoh@jp.fujitsu.com>
Date: Tue Jul 19 07:27:20 2011 +0000
Btrfs: return error to caller when btrfs_unlink() failes
When btrfs_unlink_inode() and btrfs_orphan_add() in btrfs_unlink()
are error, the error code is returned to the caller instead of
BUG_ON().
david
next prev parent reply other threads:[~2011-10-10 11:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-10 2:14 Corrupt file in subvolume dima
2011-10-10 10:37 ` David Sterba
2011-10-10 11:03 ` dima
2011-10-10 11:29 ` David Sterba [this message]
2011-10-10 12:20 ` dima
2011-10-11 13:30 ` dima
2011-10-10 11:55 ` Kai Krakow
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=20111010112917.GG17912@twin.jikos.cz \
--to=dave@jikos.cz \
--cc=dolenin@parallels.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