Re: btrfs kernel oops on mount

2016-09-12 Thread Austin S. Hemmelgarn
On 2016-09-12 09:27, Jeff Mahoney wrote: On 9/12/16 2:54 PM, Austin S. Hemmelgarn wrote: On 2016-09-12 08:33, Jeff Mahoney wrote: On 9/9/16 8:47 PM, Austin S. Hemmelgarn wrote: A couple of other things to comment about on this: 1. 'can_overcommit' (the function that the Arch kernel choked on)

Re: btrfs kernel oops on mount

2016-09-12 Thread moparisthebest
On 09/12/2016 07:37 AM, Austin S. Hemmelgarn wrote: >> On 2016-09-09 15:23, moparisthebest wrote: >> Didn't ubuntu on kernel 4.4 die in the same can_overcommit function? >> (https://www.moparisthebest.com/btrfsoops.jpg) what kind of hardware >> issues would cause a repeatable kernel crash like

Re: btrfs kernel oops on mount

2016-09-12 Thread Jeff Mahoney
On 9/12/16 2:54 PM, Austin S. Hemmelgarn wrote: > On 2016-09-12 08:33, Jeff Mahoney wrote: >> On 9/9/16 8:47 PM, Austin S. Hemmelgarn wrote: >>> A couple of other things to comment about on this: >>> 1. 'can_overcommit' (the function that the Arch kernel choked on) is >>> from the memory

Re: btrfs kernel oops on mount

2016-09-12 Thread Austin S. Hemmelgarn
On 2016-09-12 08:33, Jeff Mahoney wrote: On 9/9/16 8:47 PM, Austin S. Hemmelgarn wrote: A couple of other things to comment about on this: 1. 'can_overcommit' (the function that the Arch kernel choked on) is from the memory management subsystem. The fact that that's throwing a null pointer

Re: btrfs kernel oops on mount

2016-09-12 Thread Jeff Mahoney
On 9/9/16 8:47 PM, Austin S. Hemmelgarn wrote: > A couple of other things to comment about on this: > 1. 'can_overcommit' (the function that the Arch kernel choked on) is > from the memory management subsystem. The fact that that's throwing a > null pointer says to me either your hardware has

Re: btrfs kernel oops on mount

2016-09-12 Thread Austin S. Hemmelgarn
On 2016-09-09 15:23, moparisthebest wrote: On 09/09/2016 02:47 PM, Austin S. Hemmelgarn wrote: On 2016-09-09 12:12, moparisthebest wrote: Hi, I'm hoping to get some help with mounting my btrfs array which quit working yesterday. My array was in the middle of a balance, about 50% remaining,

Re: btrfs kernel oops on mount

2016-09-10 Thread moparisthebest
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

Re: btrfs kernel oops on mount

2016-09-10 Thread moparisthebest
On 09/09/2016 01:51 PM, Chris Murphy wrote: > Also btrfs check output is useful to include also (without --repair > for starters). btrfs check --readonly output is here: https://www.moparisthebest.com/btrfs/btrfscheck.txt *Most* of it anyway, I messed up with tmux and it took 20 hours to run so

Re: btrfs kernel oops on mount

2016-09-09 Thread Duncan
moparisthebest posted on Fri, 09 Sep 2016 15:23:13 -0400 as excerpted: > On 09/09/2016 02:47 PM, Austin S. Hemmelgarn wrote: >> On 2016-09-09 12:12, moparisthebest wrote: >>> Hi, >>> >>> I'm hoping to get some help with mounting my btrfs array which quit >>> working yesterday. My array was in

Re: btrfs kernel oops on mount

2016-09-09 Thread Chris Murphy
On Fri, Sep 9, 2016 at 12:47 PM, Austin S. Hemmelgarn wrote: > > The output from btrfs fi show and fi df both indicate that the filesystem is > essentially completely full. ?What am I missing? https://www.moparisthebest.com/btrfs/btrfsfishow.txt There's thousands of GiB's

Re: btrfs kernel oops on mount

2016-09-09 Thread moparisthebest
On 09/09/2016 02:47 PM, Austin S. Hemmelgarn wrote: > On 2016-09-09 12:12, moparisthebest wrote: >> Hi, >> >> I'm hoping to get some help with mounting my btrfs array which quit >> working yesterday. My array was in the middle of a balance, about 50% >> remaining, when it hit an error and

Re: btrfs kernel oops on mount

2016-09-09 Thread Chris Murphy
On Fri, Sep 9, 2016 at 12:32 PM, moparisthebest wrote: > This is indeed an lzo compressed system, it's always been mounted with > that option anyhow. > > btrfs check has been running for ~6 hours so far, I'll follow up with > output on that when it finishes. > > Hmm,

Re: btrfs kernel oops on mount

2016-09-09 Thread Austin S. Hemmelgarn
On 2016-09-09 14:32, moparisthebest wrote: On 09/09/2016 01:51 PM, Chris Murphy wrote: On Fri, Sep 9, 2016 at 10:12 AM, moparisthebest wrote: Hi, I'm hoping to get some help with mounting my btrfs array which quit working yesterday. My array was in the middle of a

Re: btrfs kernel oops on mount

2016-09-09 Thread Austin S. Hemmelgarn
On 2016-09-09 12:12, moparisthebest wrote: Hi, I'm hoping to get some help with mounting my btrfs array which quit working yesterday. My array was in the middle of a balance, about 50% remaining, when it hit an error and remounted itself read-only [1]. btrfs fi show output [2], btrfs df output

Re: btrfs kernel oops on mount

2016-09-09 Thread moparisthebest
On 09/09/2016 01:51 PM, Chris Murphy wrote: > On Fri, Sep 9, 2016 at 10:12 AM, moparisthebest > wrote: >> Hi, >> >> I'm hoping to get some help with mounting my btrfs array which quit >> working yesterday. My array was in the middle of a balance, about 50% >> remaining,

Re: btrfs kernel oops on mount

2016-09-09 Thread Chris Murphy
On Fri, Sep 9, 2016 at 10:12 AM, moparisthebest wrote: > Hi, > > I'm hoping to get some help with mounting my btrfs array which quit > working yesterday. My array was in the middle of a balance, about 50% > remaining, when it hit an error and remounted itself read-only

btrfs kernel oops on mount

2016-09-09 Thread moparisthebest
Hi, I'm hoping to get some help with mounting my btrfs array which quit working yesterday. My array was in the middle of a balance, about 50% remaining, when it hit an error and remounted itself read-only [1]. btrfs fi show output [2], btrfs df output [3]. I unmounted the array, and when I