All of lore.kernel.org
 help / color / mirror / Atom feed
From: Perry Gilfillan <perrye@linuxmail.org>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: hard lockup while balance was running killed my raid5
Date: Tue, 05 May 2015 13:06:15 -0500	[thread overview]
Message-ID: <55490697.8020702@linuxmail.org> (raw)
In-Reply-To: <pan.2015.05.05.17.03.19@googlemail.com>



On 05/05/2015 12:03 PM, Holger Hoffstätte wrote:
> I've also had a hard lockup just the other day during a balance (on a
> single device though), so this points to some changes in the 4.1 merge
> window.
>
> Just to confirm: by "hard lockup" you mean that the entire box is frozen,
> no longer shows any signs of life and no longer responds to anything?
The crash occured while running vmlinuz-3.19.5-200.fc21.x86_64 kernel 
image, and the console had the tail end of a crash dump.  I wasn't even 
able to use SysRq magic as a last resort.
> One thing you could try is to mount your devices without the free-space
> cache (-o clear_cache,nospace_cache) and try to run the balance.
>
> Would be interesting to see if that helps.
No joy:

mount -o clear_cache,nospace_cache /dev/sdf5 /media/mythstore-q/
mount: wrong fs type, bad option, bad superblock on /dev/sdf5,
        missing codepage or helper program, or other error

        In some cases useful info is found in syslog - try
        dmesg | tail or so.
[root@lightmyfire btrfs-progs-unstable]# dmesg | tail
[156582.161467] BTRFS: failed to read chunk tree on sde5
[156582.199621] BTRFS: open_ctree failed
[157176.918989] BTRFS info (device sde5): force clearing of disk cache
[157176.919007] BTRFS info (device sde5): disabling disk space caching
[157176.923126] BTRFS (device sde5): parent transid verify failed on 
27198602870784 wanted 291859 found 291431
[157176.928355] BTRFS (device sde5): parent transid verify failed on 
27198602887168 wanted 291859 found 291431
[157176.975898] BTRFS (device sde5): parent transid verify failed on 
27198604001280 wanted 291640 found 291420
[157176.982158] BTRFS (device sde5): bad tree block start 889192477 
27198604001280
[157176.986004] BTRFS: failed to read chunk tree on sde5
[157177.020060] BTRFS: open_ctree failed


btrfs-image throws a different error,
bytenr mismatch, want=27198603952128, have=13057557201204318535,
where the 'have' seems to be pointing some where out past Pluto!

[root@lightmyfire btrfs-progs-unstable]# ./btrfs-image /dev/sdf5 ~/text.txt
parent transid verify failed on 27198602870784 wanted 291859 found 291431
parent transid verify failed on 27198602870784 wanted 291859 found 291431
checksum verify failed on 27198602870784 found C273E746 wanted 26905AF0
parent transid verify failed on 27198602870784 wanted 291859 found 291431
Ignoring transid failure
parent transid verify failed on 27198603952128 wanted 291431 found 291859
parent transid verify failed on 27198603952128 wanted 291431 found 291859
checksum verify failed on 27198603952128 found BC5A7A89 wanted 90B199E8
checksum verify failed on 27198603952128 found BC5A7A89 wanted 90B199E8
bytenr mismatch, want=27198603952128, have=13057557201204318535
Couldn't read chunk tree
Open ctree failed
create failed (Success)



  reply	other threads:[~2015-05-05 18:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-05 16:36 hard lockup while balance was running killed my raid5 Perry Gilfillan
2015-05-05 17:03 ` Holger Hoffstätte
2015-05-05 18:06   ` Perry Gilfillan [this message]
2015-05-06  3:46     ` ronnie sahlberg
2015-05-06  3:56       ` Chris Murphy
2015-05-07 17:21     ` Perry Gilfillan
2015-05-05 17:17 ` Chris Murphy
  -- strict thread matches above, loose matches on Subject: below --
2015-05-05  0:02 Perry Gilfillan

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=55490697.8020702@linuxmail.org \
    --to=perrye@linuxmail.org \
    --cc=linux-btrfs@vger.kernel.org \
    /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.