[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20090225185413.GA2816@selene>
Date: Wed, 25 Feb 2009 18:54:13 +0000
From: Hugo Mills <hugo-lkml@...fax.org.uk>
To: Chris Mason <chris.mason@...cle.com>
Cc: Hugo Mills <hugo-lkml@...fax.org.uk>, linux-btrfs@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: btrfs: warn_slowpath in clean_tree_block and others
On Wed, Feb 25, 2009 at 01:36:26PM -0500, Chris Mason wrote:
> On Tue, 2009-02-24 at 23:02 +0000, Hugo Mills wrote:
> > This is essentially a repost of a mail I made last week, to which I
> > didn't get a reply.
>
> Sorry I missed replying to this one last week, thanks for resending.
Not a problem. I know things go astray sometimes.
> > I'm getting huge numbers of kernel warnings whilst using
> > btrfs. They're all "warn_slowpath", and all seem to be in
> > fs/btrfs/disk-io.c. I've included one typical example at the end of
> > this mail.
> >
> > Kernel versions are 2.6.29-rc2, -rc4 and -rc6.
> >
>
> The warnings look like i386, exactly what hardware is this? Is your
> kernel compiled for SMP or UP?
amd64 and a UP kernel:
hrm@...d:linux-2.6 $ uname -a
Linux vlad 2.6.29-rc6 #1 Mon Feb 23 19:53:22 GMT 2009 x86_64 GNU/Linux
Hardware is an original-series Turion 64 (i.e. one core) in a
Socket 745 desktop motherboard. The btrfs filesystem is in
LVM-on-RAID1 in an eSATA port-multiplier storage rack.
> The warning you're getting is that clean_tree_block expects this block
> to be locked, and giving out a warning because it is showing up as
> unlocked.
>
> So, hopefully you're on a UP kernel and my test for a locked spinlock is
> broken in that config.
OK. I can try patches if necessary.
Hugo.
--
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
PGP key: 515C238D from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
--- UNIX: British manufacturer of modular shelving units. ---
Download attachment "signature.asc" of type "application/pgp-signature" (190 bytes)
Powered by blists - more mailing lists