All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Helmut Hullen" <Hullen@t-online.de>
To: linux-btrfs@vger.kernel.org
Subject: Re: btrfs-convert fails
Date: 01 Nov 2010 12:55:00 +0100	[thread overview]
Message-ID: <B$1ssrji1uB@helmut.hullen.de> (raw)
In-Reply-To: <20101101104943.00007ff9@unknown>

Hallo, Felix,

Du meintest am 01.11.10:

>>>> =A0btrfs-convert: extent-tree.c:2529: btrfs_reserve_extent:
>>>> Assertion =A0 =A0 `!(ret)' failed
>>>> =A0Abgebrochen

>>> Try btrfs-convert -r /dev/xxx, hopefully it will recover your ext2.

>> 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) ...

> 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.

In these special cases: no big problem. The 1.5 TByte partition contain=
s =20
my videos (at least most of them), and there is a kind of backup on =20
another machine in the family (some kilometers away).

And my machine works behind an UPS. But what about a shutdown initiated=
 =20
by this UPS after (p.e.) 3 minutes powerloss?

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

  reply	other threads:[~2010-11-01 11:55 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
2010-11-01 11:55       ` Helmut Hullen [this message]
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='B$1ssrji1uB@helmut.hullen.de' \
    --to=hullen@t-online.de \
    --cc=helmut@hullen.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 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.