linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Philipp <philipp.andreas@gmail.com>
To: Johannes Hirte <johannes.hirte@fem.tu-ilmenau.de>
Cc: "Yan, Zheng " <yanzheng@21cn.com>, linux-btrfs@vger.kernel.org
Subject: Re: machine gets unresponsive during btrfs balance
Date: Thu, 26 Aug 2010 15:39:25 +0200	[thread overview]
Message-ID: <4C766E8D.7000103@gmail.com> (raw)
In-Reply-To: <201008261527.54056.johannes.hirte@fem.tu-ilmenau.de>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 26.08.2010 15:27, Johannes Hirte wrote:
> On Saturday 14 August 2010 00:11:55 Andreas Philipp wrote:
>> On 12.08.2010 10:04, Yan, Zheng wrote:
>>> On Thu, Aug 12, 2010 at 3:14 PM, Andreas Philipp
>>> <philipp.andreas@gmail.com> wrote:
>>>   
>>>> Hi,
>>>>
>>>> I am using a btrfs filesystem created with raid0 for data and metadata
>>>> for (temporary) storage of tv recordings from my vdr. The filesystem was
>>>> created under kernel version 2.6.34. An initial btrfs balance command
>>>> succeeded. Since I upgraded to 2.6.35-rcX and 2.6.35 btrfs balance no
>>>> longer finishes but puts the machine in some unresponsive state.
>>>> Unfortunately, I do not see any kernel oops or other debug information
>>>> because even the display freezes. The last thing that happens are that
>>>> those two lines are written to /var/log/messages:
>>>> Aug 11 21:42:23 thor kernel: btrfs: found 62911 extents
>>>> Aug 11 21:42:24 thor kernel: btrfs: relocating block group 1723913469952
>>>> flags 9
>>>> After that the machine becomes immediately unresponsive.
>>>>
>>>> As I did not see anything that might be related to my problem in the
>>>> changelog for 2.6.35.1 I did not try again with this version.
>>>>
>>>>     
>>> Do you have more than one machines? would you please setup netconsole
>>> to see what happen.
>>>   
>> I have reproduced the error on v2.6.35.1 and recorded all kernel output
>> with netconsole. The interesting point is that this time the machine did
>> not crash but the btrfs balance segfaulted at exact the same position
>> where the previous crashes had happened.
> 
> Looks like another manifestation of the csum bug. Are you able to read all 
> files from the affected volume? Did you tried a balance with an 2.6.34 kernel 
> after the test with 2.6.35?
> 
Till now I did not see any unreadable files but I did not do a
complete test. No, I did not try to balance with an 2.6.34 kernel. If
it helps I can switch back and try.

Yours,
Andreas
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJMdm6MAAoJEJIcBJ3+Xkgi9vUQALX7V6fOs+DJR9NGRr21uY1a
/tFj5e1r71Mryn6uFcnb2Iukf6oNirxc3n4XcSgfel/GppTPAt+s8a3jS048SNa1
XpPhpuA5j9vtPns46ZR5Bg9rTtAIa7oDO8Ko2lewnHcrZN9qoGyroTz+eIzqv/U/
N8BmGTKTE1TwKfETE8jVXXHvsQuV6vYeOJqtWzPkETw9gldHThTSvr3pl7+46yFT
iCv5n/IHsdAyeZpSJm1Jp3xxAGZJsrkhoKiyNcHHt7+UshcKpFYky4lOCAlDgpPO
quZhEHiYKUeHGYb8vueaebCgy2panrYcnEgwoGkI7XLPvTlWY/5uUgV/54rlUdwi
jqo+zgyNaBnEwUkqTAPzqZQBYb7XA5uJS7UchFhf5rpgFZeEX+gUnNYtEtUkkYLk
9vAAeXl8OyNJnBAH97/FBpRw0nVYpXeuE8/dvc1TfbHDjkOQLlgEYg3T4PW+NgsV
IwVOChoFPEmyFndAvONphTmUQjzGMJu2Y+3p9D7ZDRQOo8AHjGrErWPY+zGkZkd1
MtFCIKeTyOoR+13U4xAxi+2alGf7UE0jdxoGMQPnh7COjOYpUgMt1zFnksxn6yY+
RcFEWJSoBkOPMePxzJUTOCVb/Qr4V6HCJNEylBxF1VsECAOkjTSxl4XTAXrLKYVu
pllFS2PYozhZMoKrDKQE
=ldPn
-----END PGP SIGNATURE-----

  reply	other threads:[~2010-08-26 13:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-12  7:14 machine gets unresponsive during btrfs balance Andreas Philipp
2010-08-12  8:04 ` Yan, Zheng 
2010-08-13  9:28   ` Andreas Philipp
2010-08-13 22:11   ` Andreas Philipp
2010-08-26 13:27     ` Johannes Hirte
2010-08-26 13:39       ` Andreas Philipp [this message]
2010-08-26 16:38         ` Johannes Hirte
2010-08-26 18:11           ` Lubos Kolouch
2010-08-29 13:52           ` Andreas Philipp

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=4C766E8D.7000103@gmail.com \
    --to=philipp.andreas@gmail.com \
    --cc=johannes.hirte@fem.tu-ilmenau.de \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=yanzheng@21cn.com \
    /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).