From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Question: How can I recover this partition? (unable to find logical $hugenum len 4096)
Date: Thu, 22 Aug 2013 23:53:28 +0000 (UTC) [thread overview]
Message-ID: <pan$c2c58$61dbf027$55d0c5a2$71b9b679@cox.net> (raw)
In-Reply-To: 79471CD1-CDDD-4EDD-B255-40568B8446E2@nickle.es
Nicholas Lee posted on Thu, 22 Aug 2013 02:47:38 -0400 as excerpted:
> Problem: My filesystem is screwed up, and I can't mount it at all right
> now. In the logs, the problem begins around 45s.
> Adding insult to injury, this occurred right as I began the initial
> backup to another system with rsync. :(
> I would be seriously grateful to anyone that can figure out a way to
> mount/fix this partition, and I'd be willing to send some bitcoin
Not to add insult to injury, but for future reference anyway, you /are/
aware that btrfs is still marked experimental both in the kernel btrfs
option description and on the btrfs wiki[1], and that as such, anything
you put on it should be considered subject to loss, basically throw-away
data that you don't care about losing either because you have multiple
backups (on rather less developmental-stage stable filesystems), or
because it really is throw-away data, and backups would be overkill.
I know you were just starting that backup, but the fact that you're
willing to throw some bitcoin at recovery indicates that you
/already/ had valuable data on the filesystem, that should have already
been restoreable from (tested) backup. Alternatively, perhaps btrfs
simply isn't an appropriate choice of filesystem for you at this point,
because it /is/ still considered experimental. Maybe in a year or two,
sometime after that experimental label comes off, depending on how
conservative you actually need to be with your data.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2013-08-22 23:53 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-22 6:47 Question: How can I recover this partition? (unable to find logical $hugenum len 4096) Nicholas Lee
2013-08-22 14:09 ` Mitch Harder
2013-08-22 19:23 ` Nicholas Lee
2013-08-22 19:38 ` Nicholas Lee
2013-08-22 22:58 ` Chris Murphy
2013-08-23 0:58 ` Chris Murphy
[not found] ` <6A12FF1B-5E1A-4F6F-92DA-41E52152E6F2@nickle.es>
2013-08-26 17:26 ` Nicholas Lee
2013-08-26 17:36 ` Chris Murphy
[not found] ` <CAGURm2FS=YTuBpbrg7BV=Un8ZCp9xYZae-WuqhjV29xXA7e0jw@mail.gmail.com>
2013-08-26 19:10 ` Chris Murphy
2013-08-26 19:31 ` Hugo Mills
2013-08-27 3:39 ` Chris Murphy
2013-08-29 17:35 ` Zach Brown
2013-08-29 19:37 ` Chris Murphy
2013-08-29 19:40 ` Hugo Mills
2013-08-29 19:44 ` Chris Murphy
2013-08-29 19:53 ` Hugo Mills
2013-08-29 20:19 ` Chris Murphy
2013-08-29 20:28 ` Chris Murphy
2013-08-30 14:44 ` Eric Sandeen
2013-08-30 14:54 ` Hugo Mills
2013-08-23 0:59 ` Nicholas Lee
2013-08-23 1:26 ` Chris Murphy
2013-08-22 23:53 ` Duncan [this message]
[not found] ` < pan$c2c58$61dbf027$55d0c5a2$71b9b679@cox.net>
2013-08-23 1:47 ` Duncan
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='pan$c2c58$61dbf027$55d0c5a2$71b9b679@cox.net' \
--to=1i5t5.duncan@cox.net \
--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).