From: "Leon Meßner" <l.messner@physik.tu-berlin.de>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Cc: "Leon Meßner" <l.messner@physik.tu-berlin.de>
Subject: Re: btrfs mount segfaults or crashes after powerloss
Date: Tue, 15 Mar 2011 18:26:17 +0100 [thread overview]
Message-ID: <20110315172617.GD37926@emmi.physik-pool.tu-berlin.de> (raw)
In-Reply-To: <1300208269-sup-5260@think>
On Tue, Mar 15, 2011 at 12:58:43PM -0400, Chris Mason wrote:
> Excerpts from Leon Me=DFner's message of 2011-03-14 20:28:56 -0400:
> > Hi,
> >=20
> > i'm having a problem with a damaged btrfs after power loss. When i =
try
> > to mount the fs mount either segfaults (trace at bottom) or hangs i=
n=20
> > "D" state together with [btrfs-transacti].
> >=20
> > Please CC me as i'm not an the list.
> > # btrfsck -s 1 /dev/sdb2
>=20
> Does btrfsck /dev/sdb2 work? -s 1 selects a different super, hopeful=
ly
> all the supers are the same. If plain btrfsck runs without failing w=
e
> can easily work around the log tree crash.
Yes it does (i think), output is below.
# btrfsck /dev/sdb2
root 256 inode 257 errors 800
found 50907959296 bytes used err is 1
total csum bytes: 46730092
total tree bytes: 407293952
total fs tree bytes: 315609088
btree space waste bytes: 111966302
file data blocks allocated: 184320000000
referenced 56142348288
Btrfs v0.19-35-g1b444cd
thanks,
Leon
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-03-15 17:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-15 0:28 btrfs mount segfaults or crashes after powerloss Leon Meßner
2011-03-15 16:58 ` Chris Mason
2011-03-15 17:26 ` Leon Meßner [this message]
2011-03-16 19:43 ` Chris Mason
2011-03-16 20:03 ` Leon Meßner
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=20110315172617.GD37926@emmi.physik-pool.tu-berlin.de \
--to=l.messner@physik.tu-berlin.de \
--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;
as well as URLs for NNTP newsgroup(s).