All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arne Jansen <sensille@gmx.net>
To: Roman Mamedov <rm@romanrm.ru>
Cc: Andrea Gelmini <andrea.gelmini@gmail.com>,
	Chris Mason <chris.mason@oracle.com>,
	linux-btrfs <linux-btrfs@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] Btrfs pull request
Date: Mon, 07 Nov 2011 10:57:48 +0100	[thread overview]
Message-ID: <4EB7AB9C.8010402@gmx.net> (raw)
In-Reply-To: <20111107154936.7c60be38@natsu>

On 07.11.2011 10:49, Roman Mamedov wrote:
> On Mon, 07 Nov 2011 10:37:16 +0100
> Arne Jansen <sensille@gmx.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.
> 

You're right of course. The advice was not meant as a fix, but as a
means to gather more information.

  reply	other threads:[~2011-11-07  9:57 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-06 18:38 [GIT PULL] Btrfs pull request Chris Mason
2011-11-06 19:29 ` Andrea Gelmini
2011-11-06 19:29   ` Andrea Gelmini
2011-11-07  9:37   ` Arne Jansen
2011-11-07  9:49     ` Roman Mamedov
2011-11-07  9:57       ` Arne Jansen [this message]
2011-11-07 12:49       ` Andrea Gelmini
2011-11-07 12:42     ` Andrea Gelmini
2011-11-07 12:45       ` Arne Jansen
2011-11-07 12:50         ` Andrea Gelmini
2011-11-08  7:47           ` Arne Jansen
2011-11-09  1:07             ` Chris Mason
2011-11-09  7:48               ` Christoph Hellwig
2011-11-09  9:06                 ` Arne Jansen
2011-11-09 10:11                   ` Christoph Hellwig
2011-11-09 12:11                   ` Chris Mason
2011-11-09 10:29                 ` Jan Schmidt
2011-11-09 10:34                   ` Christoph Hellwig
2011-11-09 10:49                   ` Jan Schmidt
2011-11-09 12:12                   ` Chris Mason
2011-11-07  0:35 ` Chris Mason
2011-11-08 17:55 ` Dan Merillat
2011-11-08 17:55   ` Dan Merillat
2011-11-08 18:27   ` Chris Mason
2011-11-08 18:27     ` Chris Mason
2011-11-08 20:17     ` Chris Mason
2011-11-08 20:17       ` Chris Mason
2011-11-09  6:53       ` Dan Merillat
2011-11-09  6:53         ` Dan Merillat

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=4EB7AB9C.8010402@gmx.net \
    --to=sensille@gmx.net \
    --cc=andrea.gelmini@gmail.com \
    --cc=chris.mason@oracle.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rm@romanrm.ru \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.