Here is another trace, similar to the original issue, but I have a bit
more detail on this one and it is available as text which if nothing
else is more convenient so I'll go ahead and paste this. I don't
intend to keep pasting these unless I get something that looks
different.
I only posted the
I'm not sure if this is related to the same issue or not, but I just
started getting a new BUG, followed by a panic. (I'm also enabled
network console capture so that you won't have to squint at photos.)
Original BUG is:
[14740.444257] [ cut here ]
[14740.444293] kernel
On Fri, Sep 30, 2016 at 8:38 PM, Jeff Mahoney wrote:
> On 9/30/16 5:07 PM, Rich Freeman wrote:
>> On Fri, Sep 30, 2016 at 4:55 PM, Jeff Mahoney wrote:
>>> This looks like a use-after-free on one of the pages used for
>>> compression. Can you post the output of
On 9/30/16 5:07 PM, Rich Freeman wrote:
> On Fri, Sep 30, 2016 at 4:55 PM, Jeff Mahoney wrote:
>> This looks like a use-after-free on one of the pages used for
>> compression. Can you post the output of objdump -Dr
>> /lib/modules/$(uname -r)/kernel/fs/btrfs/btrfs.ko somewhere?
On Fri, Sep 30, 2016 at 4:55 PM, Jeff Mahoney wrote:
> This looks like a use-after-free on one of the pages used for
> compression. Can you post the output of objdump -Dr
> /lib/modules/$(uname -r)/kernel/fs/btrfs/btrfs.ko somewhere?
>
Sure:
On 9/30/16 2:54 PM, Rich Freeman wrote:
> On Thu, Sep 22, 2016 at 1:41 PM, Jeff Mahoney wrote:
>> On 9/22/16 8:18 AM, Rich Freeman wrote:
>>> I have been getting panics consistently after doing a btrfs replace
>>> operation on a raid1 and rebooting. I linked a photo of the panic;
On Thu, Sep 22, 2016 at 1:41 PM, Jeff Mahoney wrote:
> On 9/22/16 8:18 AM, Rich Freeman wrote:
>> I have been getting panics consistently after doing a btrfs replace
>> operation on a raid1 and rebooting. I linked a photo of the panic; I
>> haven't been able to get a text capture
Rich Freeman posted on Sun, 25 Sep 2016 09:55:42 -0400 as excerpted:
> On Fri, Sep 23, 2016 at 12:58 AM, Duncan <1i5t5.dun...@cox.net> wrote:
>>
>> Btrfs raid1 you say, and you have existing compressed files it's trying
>> to read in the backtrace?
>>
>> Sounds like the issues I see sometimes and