From: Nikola Ciprich <extmaillist@linuxbox.cz>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Harry Edmon <harry@atmos.washington.edu>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-nfs@vger.kernel.org,
nikola.ciprich@linuxbox.cz
Subject: Re: 2.6.32.2 - WARNING: at lib/kref.c:43 kref_get+0x,23/0x2b()
Date: Wed, 17 Feb 2010 16:14:35 +0100 [thread overview]
Message-ID: <20100217151435.GC30897@develbox.linuxbox.cz> (raw)
In-Reply-To: <20100216202947.GF26292@fieldses.org>
Well,
I did a lot of stress tests, and it seems to be pretty random, and what's
worse, I think it is more then one problem, oh great...
Seems that at least one of my NFS problems was in fact caused by ext4 regression
(what FS are you using?)
applying this one: http://bugzilla.kernel.org/attachment.cgi?id=24975
improved things for me a lot (see http://bugzilla.kernel.org/show_bug.cgi?id=15231 for
full discussion).
I'll watch the machine for next few days and report...
regards
nik
On Tue, Feb 16, 2010 at 03:29:47PM -0500, J. Bruce Fields wrote:
> On Tue, Feb 16, 2010 at 09:27:20PM +0100, Nikola Ciprich wrote:
> > > Nothing yet. I'm taking another look.
> > >
> > > Do you know what the most recent version was where you did *not* see
> > > these warnings?
> > well, actually I decided I'll bisect this one no matter what, so hopefully
> > we'll see soon :)
> > I'll report
>
> That would be fantastic, thanks. What test-case are you using?
>
> Any partial information ("xxxx good, xxxx bad") would also be useful.
>
> --b.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
-------------------------------------
Ing. Nikola CIPRICH
LinuxBox.cz, s.r.o.
28. rijna 168, 709 01 Ostrava
tel.: +420 596 603 142
fax: +420 596 621 273
mobil: +420 777 093 799
www.linuxbox.cz
mobil servis: +420 737 238 656
email servis: servis@linuxbox.cz
-------------------------------------
next prev parent reply other threads:[~2010-02-17 15:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-14 17:53 2.6.32.2 - WARNING: at lib/kref.c:43 kref_get+0x,23/0x2b() Harry Edmon
2010-01-22 23:03 ` Andrew Morton
2010-01-27 19:05 ` J. Bruce Fields
2010-01-27 23:01 ` Harry Edmon
2010-02-02 16:22 ` J. Bruce Fields
2010-02-16 18:22 ` Nikola Ciprich
2010-02-16 20:21 ` J. Bruce Fields
2010-02-16 20:27 ` Nikola Ciprich
2010-02-16 20:29 ` J. Bruce Fields
2010-02-17 15:14 ` Nikola Ciprich [this message]
2010-02-20 23:51 ` J. Bruce Fields
2010-02-22 5:37 ` Nikola Ciprich
2010-02-24 7:19 ` Jesper Krogh
2010-02-23 9:17 ` Jesper Krogh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100217151435.GC30897@develbox.linuxbox.cz \
--to=extmaillist@linuxbox.cz \
--cc=akpm@linux-foundation.org \
--cc=bfields@fieldses.org \
--cc=harry@atmos.washington.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=nikola.ciprich@linuxbox.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox