From: Qu Wenruo <quwenruo@cn.fujitsu.com>
To: Robert Munteanu <robert.munteanu@gmail.com>
Cc: Chris Murphy <lists@colorremedies.com>,
Vytautas D <vytdau@gmail.com>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs partition converted from ext4 becomes read-only minutes after booting: WARNING: CPU: 2 PID: 2777 at ../fs/btrfs/super.c:260 __btrfs_abort_transaction+0x4b/0x120
Date: Mon, 3 Aug 2015 08:54:12 +0800 [thread overview]
Message-ID: <55BEBBB4.4040801@cn.fujitsu.com> (raw)
In-Reply-To: <CAC8ULPbe+E6JzGS-BYvjoLTN+Y9j6PYGC4U3f5cYhgz=eaaUOg@mail.gmail.com>
Thanks for the log.
I'll investigate it to see whether we can resolve the infinite loop problem.
Thanks,
Qu
Robert Munteanu wrote on 2015/07/31 16:38 +0300:
> On Fri, Jul 31, 2015 at 5:08 AM, Qu Wenruo <quwenruo@cn.fujitsu.com> wrote:
>> Any full output about it?
>
> Please see the attached log. I left the process running for about 4
> hours, and after the first five minutes all it cared about was a
> single inode. I ended up stopping it as it looks like it's not making
> progress.
>
>> Not sure if it real loops, but maybe the inode number changed in later
>> output?
>
> Looks to me like it's the same inode
>
> $ awk '/ for inode/ { print $7 } ' screenlog.0 | sort | uniq
> 14214570
>
> Thanks,
>
> Robert
>
>
>
>
>
>
>
next prev parent reply other threads:[~2015-08-03 0:54 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-12 12:19 btrfs partition converted from ext4 becomes read-only minutes after booting: WARNING: CPU: 2 PID: 2777 at ../fs/btrfs/super.c:260 __btrfs_abort_transaction+0x4b/0x120 Robert Munteanu
2015-06-17 17:46 ` Marc MERLIN
2015-06-17 19:41 ` Marc Joliet
2015-06-18 11:05 ` Robert Munteanu
2015-06-25 4:16 ` Marc MERLIN
2015-06-25 12:08 ` Vytautas D
[not found] ` <CABE5tBasBsycy_+q=RZj1dpqsLTREJTA72F-ZwNLt=kLX6wXhg@mail.gmail.com>
2015-06-25 21:09 ` Marc MERLIN
2015-06-17 18:48 ` Jeff Mahoney
2015-06-18 11:08 ` Robert Munteanu
2015-06-26 1:54 ` Qu Wenruo
2015-06-26 2:08 ` Qu Wenruo
2015-07-09 3:09 ` Chris Murphy
2015-07-09 10:52 ` Vytautas D
[not found] ` <CAO5K3OcA1_Z4-jvv_2C0StBkOr++_vUX4kOspY8cuhnX2t3z_A@mail.gmail.com>
2015-07-09 21:38 ` Chris Murphy
2015-07-10 0:34 ` Qu Wenruo
2015-07-10 0:45 ` Chris Murphy
2015-07-10 4:45 ` Qu Wenruo
2015-07-14 23:29 ` Chris Murphy
2015-07-26 21:47 ` Robert Munteanu
2015-07-30 13:16 ` Robert Munteanu
2015-07-31 2:08 ` Qu Wenruo
2015-07-31 13:38 ` Robert Munteanu
2015-08-03 0:54 ` Qu Wenruo [this message]
2015-08-03 1:22 ` Qu Wenruo
2015-08-03 7:45 ` Robert Munteanu
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=55BEBBB4.4040801@cn.fujitsu.com \
--to=quwenruo@cn.fujitsu.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
--cc=robert.munteanu@gmail.com \
--cc=vytdau@gmail.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.