From: Felix Blanke <felixblanke@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: btrfs-convert fails
Date: Mon, 1 Nov 2010 10:49:43 +0100 [thread overview]
Message-ID: <20101101104943.00007ff9@unknown> (raw)
In-Reply-To: <B$1sRYTD1uB@helmut.hullen.de>
Hi Helmut,
don't use btrfs for important files if you got no backup yet. It's
quite stable and a lot of ppl don't have problem with it, but there are
some cases where it could be very ugly, like a powerloss while writing
etc.
Regards,
=46elix
Am 01 Nov 2010 09:02:00 +0100
schrieb "Helmut Hullen" <Hullen@t-online.de>:
> Hallo, Yan,
>=20
> Du meintest am 01.11.10:
>=20
> >> I've tried to convert a 12 GByte ext2 partition (nearly full, 280
> >> MByte free) with btrfs-convert.
> >>
> >> After about 15 minutes (700-MHz-CPU) the system tells
> >>
> >> =A0...
> >> =A0creating ext2fs image file
> >> =A0cleaning up system chunk
> >> =A0btrfs-convert: extent-tree.c:2529: btrfs_reserve_extent: Assert=
ion
> >> =A0 =A0 `!(ret)' failed
> >> =A0Abgebrochen
>=20
> > Try btrfs-convert -r /dev/xxx, hopefully it will recover your ext2.
>=20
> Restoring is (now) no problem, I'm still testing. But in some days
> (or weeks) I want to convert a partition with 1,5 TByte (which has
> no backup) ...
>=20
> Viele Gruesse!
> Helmut
> --
> 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
--
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:[~2010-11-01 9:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-31 15:55 btrfs-convert fails Helmut Hullen
2010-10-31 19:26 ` Helmut Hullen
2010-11-01 2:06 ` Yan, Zheng
2010-11-01 8:02 ` Helmut Hullen
2010-11-01 9:49 ` Felix Blanke [this message]
2010-11-01 11:55 ` Helmut Hullen
2010-11-01 12:20 ` cwillu
2010-11-02 0:43 ` Chris Samuel
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=20101101104943.00007ff9@unknown \
--to=felixblanke@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;
as well as URLs for NNTP newsgroup(s).