From: Kai Krakow <hurikhan77+btrfs@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: [3.2.1] BUG at fs/btrfs/inode.c:1588
Date: Thu, 02 Feb 2012 04:54:45 +0100 [thread overview]
Message-ID: <51epv8-2qu.ln1@hurikhan.ath.cx> (raw)
In-Reply-To: fgdov8-ord.ln1@hurikhan.ath.cx
Kai Krakow <hurikhan77+btrfs@gmail.com> schrieb:
> Interestingly, the filesystem was not unmountable - system hung. After
> reisub and checking again with "btrfs scrub" no errors where reported and
> it just rsync'ed fine this time. This does not make sense to me.
btrfsck still shows a lot of errors, while scrubbing says everything is
okay... *sigh
Now, how should one fix it if there is still no repair utility? I'm pretty
sure sooner or later I will run into a BUG_ON again...
Thanks,
Kai
next prev parent reply other threads:[~2012-02-02 3:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-01 1:05 [3.2.1] BUG at fs/btrfs/inode.c:1588 Kai Krakow
2012-02-01 18:39 ` Kai Krakow
2012-02-02 3:54 ` Kai Krakow [this message]
2012-02-02 11:19 ` Duncan
2012-02-02 23:25 ` Kai Krakow
2012-02-05 5:02 ` Duncan
2012-02-04 11:40 ` Kai Krakow
2012-02-05 0:07 ` Mitch Harder
2012-02-05 8:01 ` Kai Krakow
2012-02-05 16:15 ` Duncan
2012-02-13 21:05 ` Andrea Gelmini
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=51epv8-2qu.ln1@hurikhan.ath.cx \
--to=hurikhan77+btrfs@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 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).