All of lore.kernel.org
 help / color / mirror / Atom feed
From: Miao Xie <miaox@cn.fujitsu.com>
To: Johannes Hirte <johannes.hirte@fem.tu-ilmenau.de>
Cc: Dave Chinner <david@fromorbit.com>,
	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: Mon, 19 Jul 2010 16:01:46 +0800	[thread overview]
Message-ID: <4C44066A.3080701@cn.fujitsu.com> (raw)
In-Reply-To: <201007152014.52924.johannes.hirte@fem.tu-ilmenau.de>

On Thu, 15 Jul 2010 20:14:51 +0200, Johannes Hirte wrote:
> Am Donnerstag 15 Juli 2010, 02:11:04 schrieb Dave Chinner:
>> 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?
>
> Nothing. I double checked the logs. There are only the messages when mounting
> the filesystem. No other errors are reported than the inaccessible file and the
> output from xfs_check.

Is there anything wrong with your disks or memory?
Sometimes the bad memory can break the filesystem. I have met this kind of problem
some time ago.

If there is no problem with your disk and memory, Could you tell us the parameter of
mkfs.btrfs and mount?

Thanks
Miao Xie

  parent reply	other threads:[~2010-07-19  8:01 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-08 14:27 kernel BUG at fs/btrfs/extent-tree.c:1353 Johannes Hirte
2010-07-08 14:31 ` Chris Mason
2010-07-08 15:40   ` Johannes Hirte
2010-07-14 15:25   ` Johannes Hirte
2010-07-15  0:11     ` Dave Chinner
2010-07-15 18:14       ` Johannes Hirte
2010-07-16 14:59         ` Johannes Hirte
2010-07-19  8:01         ` Miao Xie [this message]
2010-07-22 18:07           ` Johannes Hirte
2010-07-23 11:02             ` Daniel J Blueman
2010-07-23 11:02               ` Daniel J Blueman
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
2010-08-13 12:19   ` David Woodhouse
2010-07-11 12:28 ` Johannes Hirte
2010-07-13 12:23   ` Johannes Hirte
2010-07-15 18:30     ` csum errors Johannes Hirte
2010-07-15 19:03       ` Chris Mason
2010-07-15 19:32         ` Johannes Hirte
2010-07-15 19:35           ` Chris Mason
2010-07-15 20:00             ` Johannes Hirte
2010-07-17  4:55             ` Brian Rogers
2010-08-10 21:06               ` Sebastian 'gonX' Jensen
2010-08-10 21:06                 ` Sebastian 'gonX' Jensen
2010-08-14  7:05                 ` Brian Rogers
2010-08-14 11:10                   ` Sebastian 'gonX' Jensen
2010-08-14 11:10                     ` Sebastian 'gonX' Jensen

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=4C44066A.3080701@cn.fujitsu.com \
    --to=miaox@cn.fujitsu.com \
    --cc=axboe@kernel.dk \
    --cc=chris.mason@oracle.com \
    --cc=david@fromorbit.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 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.