xfs
[Top] [All Lists]

Re: XFS: possible memory allocation deadlock in kmem_alloc (mode:0x250)

To: xfs@xxxxxxxxxxx
Subject: Re: XFS: possible memory allocation deadlock in kmem_alloc (mode:0x250)
From: Yann Dupont <Yann.Dupont@xxxxxxxxxxxxxx>
Date: Tue, 03 Dec 2013 17:28:09 +0100
Delivered-to: xfs@xxxxxxxxxxx
In-reply-to: <20131203125057.GU10988@dastard>
References: <20131128091322.GC5337@xxxxxxxxxxxxxxx> <20131128100521.GO10988@dastard> <20131203095357.GC5405@xxxxxxxxxxxxxxx> <20131203125057.GU10988@dastard>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.1
Le 03/12/2013 13:50, Dave Chinner a écrit :
On Tue, Dec 03, 2013 at 10:53:58AM +0100, Emmanuel Lacour wrote:
OK, 32GB RAM, no obvious shortage, no dirty or writeback data. 2TB SATA drives, 32AGs, only unusual setting is 64k directory block size. Yup, there's your problem:

I can confirm I also saw this from times to times, in the very same context (ceph OSD, xfs volume with 64k directory blocks)

I never took the time to fully report the problem because it was very sporadic, and I suspected a specific option in my hand-made kernels, in which the problem seems to occurs more often. With the 'standard' debian 3.10.2 (from testing) I never saw the problem (56 days uptime)

cf http://tracker.ceph.com/issues/6301

the report isn't complete here ... sometimes I just have the deadlock, but without oops.
can try to dig deeper inmy old logs to be sure it's really the same

Cheers,

--
Yann Dupont - Service IRTS, DSI Université de Nantes
Tel : 02.53.48.49.20 - Mail/Jabber : Yann.Dupont@xxxxxxxxxxxxxx

<Prev in Thread] Current Thread [Next in Thread>