All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Hampton <mailinglists@dhampton.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Missing half of available space (resend)
Date: Wed, 09 Dec 2015 12:28:01 -0500	[thread overview]
Message-ID: <1449682081.7150.0.camel@dhampton.net> (raw)
In-Reply-To: <pan$2b447$368e596$ba3d70ae$2f6cd5d4@cox.net>

On Wed, 2015-12-09 at 16:48 +0000, Duncan wrote:
> David Hampton posted on Wed, 09 Dec 2015 01:30:09 -0500 as excerpted:
> 
> > Seems I need to upgrade my tools.  That command was added in 3.18 and I
> > only have the 3.12 tools.
> 
> Definitely so, especially because you're running raid6, which wasn't 
> stable until 4.1 for both kernel and userspace.  3.12?  I guess it did 
> have the very basic raid56 support, but it's definitely nothing I'd 
> trust, at that old not for btrfs in general, but FOR SURE not raid56.

I've upgraded to the 4.2.0 kernel and the 4.0 btrfs-tools package.
These are the latest that Ubuntu has packaged for 15.10, and I've pulled
them into my 14.10 based release.  Is this recent enough, or do I need
to try the 4.3 kernel/tools build from the active development tree (that
will eventually become 16.04)?

David




  reply	other threads:[~2015-12-09 19:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-09  5:02 Missing half of available space (resend) David Hampton
2015-12-09  5:27 ` Chris Murphy
2015-12-09  6:30   ` David Hampton
2015-12-09 16:48     ` Duncan
2015-12-09 17:28       ` David Hampton [this message]
2015-12-09 19:39         ` Chris Murphy
2015-12-09 19:56           ` Gareth Pye
2015-12-09 21:26             ` David Hampton
2015-12-09 21:28             ` Chris Murphy
2015-12-09 21:41               ` David Hampton
2015-12-09 21:59                 ` Gareth Pye
2015-12-10  3:27           ` 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=1449682081.7150.0.camel@dhampton.net \
    --to=mailinglists@dhampton.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 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.