public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Alex Elsayed <eternaleye@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Kernel BUG on mounting BtrFS / after reboot
Date: Tue, 23 Feb 2010 08:30:56 +0000 (UTC)	[thread overview]
Message-ID: <loom.20100223T092903-542@post.gmane.org> (raw)
In-Reply-To: loom.20100218T215310-779@post.gmane.org

Alex Elsayed <eternaleye <at> gmail.com> writes:

> 
> Chris Mason <chris.mason <at> oracle.com> writes:
> > I think the btrfsck output is missing.  It sounds like we'll survive if
> > we just skip this part of the log replay.  I'll cook a patch based on
> > the btrfsck output.
> 
> It was inline in my first message, immediately after the BUG trace.

Any update? Including btrfsck output here, in case it got lost:

Arkadios ~ # btrfsck /dev/Arkadios/Root
root 5 inode 1525410 errors 400
root 5 inode 5364659 errors 2
root 5 inode 5364663 errors 2
root 5 inode 5364668 errors 2
root 5 inode 5364677 errors 2
root 5 inode 6123691 errors 400
root 5 inode 6239775 errors 2
root 5 inode 6239779 errors 2
root 5 inode 6239789 errors 2
root 5 inode 6239971 errors 2
root 5 inode 6269030 errors 2
root 5 inode 6269034 errors 2
root 5 inode 6269667 errors 2
root 5 inode 6270025 errors 2
root 5 inode 6423082 errors 400
root 5 inode 6424288 errors 2
root 5 inode 6424328 errors 2
root 5 inode 6424506 errors 2
root 5 inode 6424510 errors 2
root 5 inode 7314036 errors 400
root 5 inode 7538573 errors 400
root 5 inode 7541407 errors 400
root 5 inode 7541533 errors 400
root 5 inode 7954626 errors 400
root 5 inode 7955659 errors 2
root 5 inode 7955723 errors 2
root 5 inode 7955727 errors 2
root 5 inode 7957158 errors 2
root 5 inode 8076299 errors 2
root 5 inode 8138735 errors 400
root 5 inode 8346718 errors 400
root 5 inode 8378669 errors 400
root 5 inode 8504794 errors 400
root 5 inode 8628757 errors 400
root 5 inode 8628952 errors 2
root 5 inode 8628966 errors 2
root 5 inode 8628970 errors 2
root 5 inode 8629003 errors 2
root 5 inode 8633819 errors 2
root 5 inode 8693549 errors 400
root 5 inode 9014871 errors 2
root 5 inode 9014938 errors 2
root 5 inode 9014942 errors 2
root 5 inode 9014946 errors 2
found 449101881344 bytes used err is 1
total csum bytes: 433187792
total tree bytes: 5517582336
total fs tree bytes: 4585156608
btree space waste bytes: 1419008115
file data blocks allocated: 1040877457408
 referenced 439746732032
Btrfs Btrfs v0.19



  reply	other threads:[~2010-02-23  8:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-12 21:04 Kernel BUG on mounting BtrFS / after reboot Alex Elsayed
2010-02-12 22:50 ` Mike Fedyk
2010-02-12 22:59   ` Alex Elsayed
2010-02-17  6:47     ` Alex Elsayed
2010-02-17 14:18 ` Chris Mason
2010-02-18  0:35   ` Alex Elsayed
2010-02-18 15:02     ` Chris Mason
2010-02-18 17:38       ` Alex Elsayed
2010-02-18 20:48         ` Chris Mason
2010-02-18 20:54           ` Alex Elsayed
2010-02-23  8:30             ` Alex Elsayed [this message]
2010-02-25  1:40               ` Chris Mason

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=loom.20100223T092903-542@post.gmane.org \
    --to=eternaleye@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox