Re: XFS: possible memory allocation deadlock in kmem_alloc

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I don't think that's the information I requested:

>> Can you please do:
>>
>> # echo 11 > /proc/sys/fs/xfs/error_level
>>
>> and hit it again, then send a few of the backtraces from dmesg?

-Eric


On 11/5/19 1:53 PM, Chris Holcombe wrote:
> I've got the stack traces and they're massive.
> https://cloud.box.com/s/5grgnjwej5prmahl92v49937w6hgdnsv
> https://cloud.box.com/s/wfrjg7yhiwufpgidoq1qos8mrwtu4ij3
> https://cloud.box.com/s/3wcfgfdyvcsbslfdxc9ntfdt7yrhtcjt
> 
> On Tue, Nov 5, 2019 at 9:11 AM Eric Sandeen <sandeen@xxxxxxxxxxx> wrote:
>>
>>
>>
>> CAUTION: External Email
>>
>>
>>
>>
>> On 11/5/19 10:25 AM, Chris Holcombe wrote:
>>> Hi Eric,
>>> I've attached both the dmesg command output and /var/log/dmesg.log
>>> which have different values in them.
>>
>> Thanks.  Aaand .... I forgot that we don't dump a stack trace by default.
>>
>> Can you please do:
>>
>> # echo 11 > /proc/sys/fs/xfs/error_level
>>
>> and hit it again, then send a few of the backtraces from dmesg?
>>
>> # echo 3 > /proc/sys/fs/xfs/error_level
>>
>> will quiet things down again.
>>
>> -Eric
> 



[Index of Archives]     [XFS Filesystem Development (older mail)]     [Linux Filesystem Development]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux RAID]     [Linux SCSI]


  Powered by Linux