From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Partition broken, btrfsck segfaults or asserts
Date: Tue, 5 Nov 2013 14:00:08 +0000 (UTC) [thread overview]
Message-ID: <pan$dd2c1$bf1263f8$d3d5db6a$5d59e872@cox.net> (raw)
In-Reply-To: 20131105130459.133d538e@samson
Dennis Schridde posted on Tue, 05 Nov 2013 13:04:59 +0100 as excerpted:
> I have a serious problem with inaccessible data and segfaulting btrfsck
> for the /var partition on my computer.
> I can mount it[.] When I access certain directories, however, I get a
> message like this one:
> ls: cannot access /var/log: Stale NFS file handle
> When I run btrfsck --repair it asserts, and when I just run btrfsck
> without extra options it segfaults.
Ouch!
> https://bugzilla.kernel.org/show_bug.cgi?id=64411
>
> # btrfs --version Btrfs v0.20-rc1-358-g194aa4a
>
> # uname -r 3.11.6-gentoo
Fellow gentooer, and quite upto date both kernel- and tools-wise, as
befits a still experimental filesystem under heavy development.
=:^)
> I would be thankful if you could help me to get as much as possible of
> my data back. And please CC me, as I am not subscribed to the list.
Posted directly to you and to list as requested.
Unfortunately I don't have an easy guaranteed recovery solution.
But since you're running an experimental filesystem that both the btrfs
wiki (mentioned in the gentoo btrfs-tools package post-inst message) and
the kernel config option warn to keep tested backups and use only with
non-critical data, either restore from that tested backup or by
definition you considered the data not critical enough to be worth
worrying about recovering if it was lost in the first place. Thus no
worries either way. Either you had tested backups and can restore from
them, or by your actions you already declared the data not worth worrying
about if the still experimental filesystem ate it for lunch!
Meanwhile, I see you've tried a few recovery methods, but it might be
worth mentioning this post, with a list of methods to try and in what
order:
http://permalink.gmane.org/gmane.comp.file-systems.btrfs/27999
And in case you missed the gentoo btrfs-tools package homepage link,
which is to the wiki, here it is again. If you haven't already, it's
worth reading up. =:^)
https://btrfs.wiki.kernel.org
--
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
prev parent reply other threads:[~2013-11-05 14:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-05 12:04 Partition broken, btrfsck segfaults or asserts Dennis Schridde
2013-11-05 14:00 ` Duncan [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='pan$dd2c1$bf1263f8$d3d5db6a$5d59e872@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).