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: Wed, 16 Mar 2011 21:03:03 +0100 [thread overview]
Message-ID: <20110316200303.GA5711@emmi.physik-pool.tu-berlin.de> (raw)
In-Reply-To: <1300304176-sup-1475@think>
On Wed, Mar 16, 2011 at 03:43:52PM -0400, Chris Mason wrote:
> Excerpts from Leon Me=DFner's message of 2011-03-15 13:26:17 -0400:
> > 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 -040=
0:
> > > > Hi,
> > > >=20
> > > > i'm having a problem with a damaged btrfs after power loss. Whe=
n i try
> > > > to mount the fs mount either segfaults (trace at bottom) or han=
gs in=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, hop=
efully
> > > all the supers are the same. If plain btrfsck runs without faili=
ng we
> > > can easily work around the log tree crash.
> >=20
> > Yes it does (i think), output is below.
>=20
> Ok, if you have the latest btrfs-progs from git, you can
>=20
> make btrfs-zero-log
> ./btrfs-zero-log /dev/xxx
That worked. I could mount the partition with the following log message=
:
# dmesg | tail -n 4
Btrfs loaded
device label rootext4 devid 1 transid 45013 /dev/sdb2
Btrfs detected SSD devices, enabling SSD mode
btrfs: unlinked 13 orphan
Thanks a lot,
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
prev parent reply other threads:[~2011-03-16 20:03 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
2011-03-16 19:43 ` Chris Mason
2011-03-16 20:03 ` Leon Meßner [this message]
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=20110316200303.GA5711@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).