From: Chris Mason <clm@fb.com>
To: Marc MERLIN <marc@merlins.org>
Cc: <linux-btrfs@vger.kernel.org>
Subject: Re: Upgrade to 3.14.0 messed up raid0 array (btrfs cleaner crashes in fs/btrfs/extent-tree.c:5748 and fs/btrfs/free-space-cache.c:1183 )
Date: Wed, 9 Apr 2014 11:46:13 -0400 [thread overview]
Message-ID: <53456B45.8050906@fb.com> (raw)
In-Reply-To: <20140409154259.GM10789@merlins.org>
On 04/09/2014 11:42 AM, Marc MERLIN wrote:
> On Tue, Apr 08, 2014 at 10:31:39PM -0700, Marc MERLIN wrote:
>> On Tue, Apr 08, 2014 at 09:31:25PM -0700, Marc MERLIN wrote:
>>> On Tue, Apr 08, 2014 at 07:49:14PM -0400, Chris Mason wrote:
>>>>
>>>>
>>>> On 04/08/2014 06:09 PM, Marc MERLIN wrote:
>>>>> I forgot to add that while I'm not sure if anyone ended up looking at the
>>>>> last image I made regarding
>>>>> https://urldefense.proofpoint.com/v1/url?u=https://bugzilla.kernel.org/show_bug.cgi?id%3D72801&k=ZVNjlDMF0FElm4dQtryO4A%3D%3D%0A&r=6%2FL0lzzDhu0Y1hL9xm%2BQyA%3D%3D%0A&m=dQHW2ddzMXNlRthusH4o6nZVMltGycqZ8zO5AgwPphE%3D%0A&s=783fd1cd39566becdfb62904889cd7459c81dd2793d19538b2ab093bb8d06f88
>>>>>
>>>>> I can generate a an image of that filesystem if that helps, or try other
>>>>> commands which hopefully won't crash my running server :)
>>>>> (filesystem is almost 2TB, so the image will again be big)
>>>>>
>>>>
>>>> Hi Marc,
>>>>
>>>> So from the messages it looks like your space cache is corrupted. Lets
>>>> start with clearing the space cache and running fsck and seeing exactly
>>>> what is wrong.
>>>
>>> gargamel:~# mount -o clear_cache /dev/dm-4 /mnt/mnt
>>> [48132.661274] BTRFS: device label btrfs_raid0 devid 1 transid 50567 /dev/mapper/raid0d1
>>> [48132.703063] BTRFS info (device dm-5): force clearing of disk cache
>>> [48132.724780] BTRFS info (device dm-5): disk space caching is enabled
>
> So, I tried again this morning, mounted with clear_cache, let the clearer
> process work a bit:
> root 25187 0.0 0.0 0 0 ? S 07:56 0:00 [btrfs-freespace]
> but even though I did not have the FS mounted, after just one minute, the
> kernel went into that death loop again.
>
> Then (2nd log below), I tried mounting with -o clear_cache,nospace_cache and
> had the same problem too.
>
> I'll wait on your next suggestion, with maybe how you'd like me to run btrfsck
Downloading the image now. I'd just run a readonly btrfsck /dev/xxx
-chris
next prev parent reply other threads:[~2014-04-09 15:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-08 15:36 Upgrade to 3.14.0 messed up raid0 array (btrfs cleaner crashes in fs/btrfs/extent-tree.c:5748 and fs/btrfs/free-space-cache.c:1183 ) Marc MERLIN
2014-04-08 22:09 ` Marc MERLIN
2014-04-08 23:49 ` Chris Mason
2014-04-09 4:31 ` Marc MERLIN
2014-04-09 5:31 ` Marc MERLIN
2014-04-09 15:42 ` Marc MERLIN
2014-04-09 15:46 ` Chris Mason [this message]
2014-04-09 16:51 ` Marc MERLIN
2014-04-09 18:54 ` Chris Mason
2014-04-09 19:24 ` Duncan
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=53456B45.8050906@fb.com \
--to=clm@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=marc@merlins.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).