xfs
[Top] [All Lists]

Re: XFS problem

To: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Subject: Re: XFS problem
From: Kelbel Junior <jymmyjr@xxxxxxxxx>
Date: Thu, 26 Jan 2012 13:57:34 -0200
Cc: linux-kernel@xxxxxxxxxxxxxxx, xfs@xxxxxxxxxxx
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=3GQCAcWfi5k/y8F1SlJfAF9/y0fUnttQyI1MNzR2d2w=; b=xFnUMT1645P+YhNKEM6f0NZkCt3/gI5HaJU1heymc/SRDn3uIKLqO6XqhuGCfHSkU8 JtLQTnnqmELRYsOg7nu9CPQ7pcUbq4jd80qOP7JhDAPsB7ajpN679fvhShAfCKoR6tcy 4t78YzeBq1Sck5nr/OeXfeB49Q2kIGg/SQqbA=
In-reply-to: <20120124213936.GA1505@xxxxxxxxxxxxx>
References: <CAAA8XhOXuszcyCaMOcVWb-erGAJQdhBHCX-gsJ4KpH+Td7+bPQ@xxxxxxxxxxxxxx> <20120124213936.GA1505@xxxxxxxxxxxxx>
Well, in 24/01 i upgrade to the kernel 3.2.1 in one server and forgot
read my emails...until now it's running without problems.
Then, yesterday i put kernel 3.2.1 on another server and this morning
a several same messages "server013 kernel: XFS: possible memory
allocation deadlock in kmem_alloc (mode:0x250)" and delays.

(without call trace because i forgot to apply that patch with dump_stack)

Now i applied the dump_stack and the latest patches that you sent.
I'm trying to discover what triggers this bug, to help in a
solution... I tell you any news


*** Some useful information:

# mount
/dev/sdb1 on MOUNTPOINT type xfs (rw,noatime)

But in some cases i use RAID and mount the partition with the
following settings (and happen the same problem):
/dev/mapper/server012_vg-server012_vol on MOUNTPOINT type xfs
(rw,noatime,nodiratime,inode64,nobarrier)

HD model:
Seagate ST31000528AS -- Barracuda 7200.12 SATA 3Gb/s 1TB Hard Drive

I work in a cache solution company, so I/O performance is very
important in our context.


Thanks.
Kelbel Junior

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