From: Dave Chinner <david@fromorbit.com>
To: Johannes Hirte <johannes.hirte@fem.tu-ilmenau.de>
Cc: Chris Mason <chris.mason@oracle.com>,
linux-kernel@vger.kernel.org, linux-btrfs@vger.kernel.org,
zheng.yan@oracle.com, Jens Axboe <axboe@kernel.dk>,
linux-fsdevel@vger.kernel.org
Subject: Re: kernel BUG at fs/btrfs/extent-tree.c:1353
Date: Thu, 15 Jul 2010 10:11:04 +1000 [thread overview]
Message-ID: <20100715001104.GF30737@dastard> (raw)
In-Reply-To: <201007141725.24507.johannes.hirte@fem.tu-ilmenau.de>
On Wed, Jul 14, 2010 at 05:25:23PM +0200, Johannes Hirte wrote:
> Am Donnerstag 08 Juli 2010, 16:31:09 schrieb Chris Mason:
> I'm not sure if btrfs is to blame for this error. After the errors I switched
> to XFS on this system and got now this error:
>
> ls -l .kde4/share/apps/akregator/data/
> ls: cannot access .kde4/share/apps/akregator/data/feeds.opml: Structure needs
> cleaning
> total 4
> ?????????? ? ? ? ? ? feeds.opml
What is the error reported in dmesg when the XFS filesytem shuts down?
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2010-07-15 0:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201007081627.24654.johannes.hirte@fem.tu-ilmenau.de>
[not found] ` <20100708143109.GR15984@think>
2010-07-14 15:25 ` kernel BUG at fs/btrfs/extent-tree.c:1353 Johannes Hirte
2010-07-15 0:11 ` Dave Chinner [this message]
2010-07-15 18:14 ` Johannes Hirte
2010-07-16 14:59 ` Johannes Hirte
2010-07-19 8:01 ` Miao Xie
2010-07-22 18:07 ` Johannes Hirte
2010-07-23 11:02 ` Daniel J Blueman
2010-07-23 11:14 ` Bob Copeland
2010-07-29 17:09 ` Johannes Hirte
2010-07-29 18:54 ` Jens Axboe
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=20100715001104.GF30737@dastard \
--to=david@fromorbit.com \
--cc=axboe@kernel.dk \
--cc=chris.mason@oracle.com \
--cc=johannes.hirte@fem.tu-ilmenau.de \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zheng.yan@oracle.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).