From: moparisthebest <admin@moparisthebest.com>
To: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs kernel oops on mount
Date: Sat, 10 Sep 2016 14:50:03 -0400 [thread overview]
Message-ID: <57D455DB.20505@moparisthebest.com> (raw)
In-Reply-To: <CAJCQCtQpfJ9eji_KrNMsRkgEP=psL_PQc+nsPNJY8qAYey60VA@mail.gmail.com>
On 09/09/2016 03:28 PM, Chris Murphy wrote:
> Sounds like with enospc devs want to see a couple things beyond what I
> asked for:
>
> enospc_debug
> grep -IR . /sys/fs/btrfs/UUID/allocation/
>
> That's kinda hard to do right now if it's not mounting though...
I managed to get more output from arch/4.7.2 using netconsole, I did end
up with duplicate lines somehow though which uniq fixed, but some of the
crash is mixed together on the same line, I didn't mess with that for
fear of taking out something important:
https://www.moparisthebest.com/btrfs/archnetconsole.txt
I was also able to mount it ro so I ran the grep you asked for:
https://www.moparisthebest.com/btrfs/enospcdebug.txt
I tried mounting with mount -o rw,skip_balance and it still locked up,
so for now it's read-only...
Let me know what else I can provide or try. I haven't been able to boot
with a 4.7 kernel on my ubuntu install so I figure 4.8 will be the same,
I guess I'll need to permanently install something like arch to a flash
drive and try 4.8 from there.
Thanks!
next prev parent reply other threads:[~2016-09-10 18:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-09 16:12 btrfs kernel oops on mount moparisthebest
2016-09-09 17:51 ` Chris Murphy
2016-09-09 18:32 ` moparisthebest
2016-09-09 18:49 ` Austin S. Hemmelgarn
2016-09-09 19:21 ` Chris Murphy
2016-09-10 15:13 ` moparisthebest
2016-09-09 18:47 ` Austin S. Hemmelgarn
2016-09-09 19:23 ` moparisthebest
2016-09-09 22:09 ` Duncan
2016-09-12 11:37 ` Austin S. Hemmelgarn
2016-09-12 13:32 ` moparisthebest
2016-09-09 19:28 ` Chris Murphy
2016-09-10 18:50 ` moparisthebest [this message]
2016-09-12 12:33 ` Jeff Mahoney
2016-09-12 12:54 ` Austin S. Hemmelgarn
2016-09-12 13:27 ` Jeff Mahoney
2016-09-12 13:58 ` Austin S. Hemmelgarn
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=57D455DB.20505@moparisthebest.com \
--to=admin@moparisthebest.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).