linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Mason <chris.mason@oracle.com>
To: Martin Steigerwald <Martin@lichtvoll.de>
Cc: linux-btrfs@vger.kernel.org, Arne Jansen <sensille@gmx.net>
Subject: Re: 3.2-rc4: scrubbing locks up the kernel, then hung tasks on boot
Date: Thu, 15 Mar 2012 14:08:52 -0400	[thread overview]
Message-ID: <20120315180852.GW19217@shiny> (raw)
In-Reply-To: <201203151903.14445.Martin@lichtvoll.de>

On Thu, Mar 15, 2012 at 07:03:14PM +0100, Martin Steigerwald wrote:
> Am Donnerstag, 15. M=E4rz 2012 schrieb Chris Mason:
> > >=20
> > > I didn=B4t yet test it but I tried the first balance then scrub s=
tuff=20
> > > again:
> > Looks like you're on a 32 bit machine.  The current for-linus branc=
h
> > has an important fix for scrub on 32 bit that should solve this.
>=20
> Yes, thats 32-bit.
>=20
> Can this fix be applied to 3.2 as well? If yes, could you point me at=
 it?
> Or otherwise is current for-linus somewhat stable?
>=20
> Cloning nonetheless - well after it finally installed git there which
> takes ages with audio playback lockups. Hopefully the /home BTRFS
> is faster than the / one ;). I have no cross-compiling set up.
>=20
> From atop:
>=20
> PAG | scan  11903 | stall      0 |              | swin      25 | swou=
t    875 |
> DSK |         sda | busy     74% | read     297 | write   4240 | avio=
    1 ms |

http://git.kernel.org/?p=3Dlinux/kernel/git/mason/linux-btrfs.git;a=3Dc=
ommit;h=3Da175423c831ea582c06784d1e172d2ce1d79923a

The patch is so small you can edit it by hand.

-chris
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2012-03-15 18:08 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-17 17:33 3.2-rc4: scrubbing locks up the kernel, then hung tasks on boot Martin Steigerwald
2011-12-17 18:11 ` Martin Steigerwald
2011-12-20 20:46 ` Martin Steigerwald
2012-01-21 10:49   ` Martin Steigerwald
2012-01-21 11:19     ` Martin Steigerwald
2012-02-24 15:51       ` Martin Steigerwald
2012-02-25  8:14         ` Arne Jansen
2012-02-25 20:14           ` Martin Steigerwald
2012-03-15 17:32           ` Martin Steigerwald
2012-03-15 17:39             ` Martin Steigerwald
2012-03-15 17:42             ` Chris Mason
2012-03-15 18:03               ` Martin Steigerwald
2012-03-15 18:08                 ` Chris Mason [this message]
2012-03-16 15:05               ` Martin Steigerwald
2012-03-16 15:37                 ` Arne Jansen
2012-03-17  9:43                 ` Martin Steigerwald
2012-03-18  0:37                   ` Greg Kroah-Hartman
2012-03-19  8:31                     ` Martin Steigerwald
2012-03-19 15:48                       ` Greg Kroah-Hartman
2012-03-19 16:03                         ` Martin Steigerwald
2012-01-24  9:28     ` Arne Jansen
2012-01-24 10:16       ` Martin Steigerwald
2012-01-24 10:29         ` Arne Jansen
2012-01-24 10:39           ` Martin Steigerwald

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=20120315180852.GW19217@shiny \
    --to=chris.mason@oracle.com \
    --cc=Martin@lichtvoll.de \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=sensille@gmx.net \
    /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;
as well as URLs for NNTP newsgroup(s).