[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20111107154936.7c60be38@natsu>
Date: Mon, 7 Nov 2011 15:49:36 +0600
From: Roman Mamedov <rm@...anrm.ru>
To: Arne Jansen <sensille@....net>
Cc: Andrea Gelmini <andrea.gelmini@...il.com>,
Chris Mason <chris.mason@...cle.com>,
linux-btrfs <linux-btrfs@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] Btrfs pull request
On Mon, 07 Nov 2011 10:37:16 +0100
Arne Jansen <sensille@....net> wrote:
> > I've got this:
> >
> > root@Q45:/home/gelma/dev/prg/btrfs# ./btrfs scrub start -Br /dev/md126
> > ERROR: scrubbing /dev/md126 failed for device id 1 (Cannot allocate memory)
> > scrub canceled for 11827b37-1ba0-4b3e-883d-2746987724ca
> > scrub started at Sun Nov 6 20:23:46 2011 and was aborted after 0 seconds
> > total bytes scrubbed: 0.00 with 0 errors
> > root@Q45:/home/gelma/dev/prg/btrfs# ./btrfs scrub start -Br /home/
> > ERROR: scrubbing /home/ failed for device id 1 (Cannot allocate memory)
> > scrub canceled for 11827b37-1ba0-4b3e-883d-2746987724ca
> > scrub started at Sun Nov 6 20:25:01 2011 and was aborted after 0 seconds
> > total bytes scrubbed: 0.00 with 0 errors
>
> On what platform are you running this? Can you please try this after
> a fresh boot? Maybe there's an allocation that can't be served with
> a badly fragmented memory.
If so, shouldn't there also be a corresponding dmesg warning about "Unable to allocate....", which would confirm or rule this out?
So before following the "did you try turning it off and on again" advice (and throwing away useful debug info), I'd suggest checking/saving dmesg first.
--
With respect,
Roman
~~~~~~~~~~~~~~~~~~~~~~~~~~~
"Stallman had a printer,
with code he could not see.
So he began to tinker,
and set the software free."
Download attachment "signature.asc" of type "application/pgp-signature" (199 bytes)
Powered by blists - more mailing lists