From: Martin <m_btrfs@ml1.co.uk>
To: linux-btrfs@vger.kernel.org
Subject: Re: btrfsck --repair /dev/sdc (Was: [PATCH] Btrfs-progs: allow --init-extent-tree to work when extent tree is borked)
Date: Wed, 20 Nov 2013 20:03:13 +0000 [thread overview]
Message-ID: <l6j4hn$a90$2@ger.gmane.org> (raw)
In-Reply-To: <pan$809d5$4354febd$5ff6e929$a8235336@cox.net>
On 20/11/13 17:08, Duncan wrote:
> Which leads to the question of what to do next. Obviously, there have
> been a number of update patches since then, some of which might address
> your problem. You could update your kernel and userspace and try
> again... /if/ you have the patience...
This is on kernel 3.11.5 and Btrfs v0.20-rc1-591-gc652e4e.
Can easily upgrade to the latest kernel at the expense of killing the
existing btrfsck run.
Regards,
Martin
next prev parent reply other threads:[~2013-11-20 20:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-25 18:01 [PATCH] Btrfs-progs: allow --init-extent-tree to work when extent tree is borked Josef Bacik
2013-10-25 18:27 ` Martin
2013-10-25 18:31 ` Josef Bacik
2013-10-26 23:16 ` Martin
2013-10-27 1:44 ` Josef Back
2013-10-28 15:11 ` Josef Bacik
2013-11-07 1:25 ` Martin
2013-11-11 22:52 ` Martin
2013-11-13 12:08 ` Martin
2013-11-13 13:46 ` Duncan
2013-11-15 17:18 ` Martin
2013-11-19 6:34 ` Martin
2013-11-20 6:51 ` btrfsck --repair /dev/sdc (Was: [PATCH] Btrfs-progs: allow --init-extent-tree to work when extent tree is borked) Martin
2013-11-20 17:08 ` Duncan
2013-11-20 20:00 ` Martin
2013-11-25 23:18 ` Martin
2013-11-27 6:29 ` Martin
2013-11-20 20:03 ` Martin [this message]
2013-11-19 6:25 ` [PATCH] Btrfs-progs: allow --init-extent-tree to work when extent tree is borked Martin
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='l6j4hn$a90$2@ger.gmane.org' \
--to=m_btrfs@ml1.co.uk \
--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).