From: Hullen@t-online.de (Helmut Hullen)
To: linux-btrfs@vger.kernel.org
Subject: Re: Uncorrectable errors on newly extended volume
Date: 07 Jun 2012 11:42:00 +0200 [thread overview]
Message-ID: <CAQox1T9CXB@helmut.hullen.de> (raw)
In-Reply-To: <CADP2XCmzvf2x10L=Cn8Wvod=2hST0ZrQ16Nu4EaYraJ1JKZyrQ@mail.gmail.com>
Hallo, Randall,
Du meintest am 07.06.12:
[...]
> I've just upgraded to 3.4.0 from git.kernel.org and I'm still running
> into problems. I checked the Problems FAQ and there doesn't seem to
> be anything that matches my problem.
[...]
> Any more help would be appreciated. Why is this happening, and how
> can I get my data back?
Why? I don't know - sorry.
Data back: take your last backup.
(I know this way to get my data back ...)
"btrfs" is still under heavy construction, and restoring damaged data is
still a problematic work. You always should have a valid backup (better:
some backups).
Viele Gruesse!
Helmut
next prev parent reply other threads:[~2012-06-07 9:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-01 8:53 Uncorrectable errors on newly extended volume Randall Mason
2012-06-01 9:06 ` Helmut Hullen
2012-06-07 9:13 ` Randall Mason
2012-06-07 9:42 ` Helmut Hullen [this message]
2012-06-07 9:47 ` Duncan
2012-06-07 10:21 ` David Sterba
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=CAQox1T9CXB@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 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).