Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Russell Coker <russell@coker.com.au>
To: Duncan <1i5t5.duncan@cox.net>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Btrfs hangs 3.19-10
Date: Mon, 6 Apr 2015 08:39:01 +0000	[thread overview]
Message-ID: <201504060839.01726.russell@coker.com.au> (raw)
In-Reply-To: <pan$d8274$4104f220$c763dc8e$c4e4259e@cox.net>

On Mon, 6 Apr 2015 03:21:18 AM Duncan wrote:
> So... for 3.2 compatibility, extref must not be enabled (tho it's now the 
> default and AFAIK there's no way to actually disable it, only enable, so 
> an old btrfs-tools would have to be used that doesn't enable it by 
> default), AND the nodesize must be set to page size, 4096 bytes for x86.

So basically we have to have an old version of mkfs.btrfs to make a filesystem 
that can be mounted on kernel 3.2.

-- 
My Main Blog         http://etbe.coker.com.au/
My Documents Blog    http://doc.coker.com.au/

  reply	other threads:[~2015-04-06  8:39 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-02 11:38 Btrfs hangs 3.19-10 Timofey Titovets
2015-04-02 11:46 ` Hugo Mills
2015-04-02 11:47   ` Timofey Titovets
2015-04-02 14:13   ` Roman Mamedov
2015-04-03  5:14     ` Duncan
2015-04-04 12:55       ` Russell Coker
2015-04-04 13:00         ` Hugo Mills
2015-04-05  3:16           ` Duncan
2015-04-05  3:30             ` Russell Coker
2015-04-05 10:04               ` Hugo Mills
2015-04-06  3:21                 ` Duncan
2015-04-06  8:39                   ` Russell Coker [this message]
2015-04-06  7:40                 ` Pavel Volkov
2015-04-06  8:37                   ` Russell Coker
2015-04-06  9:20                   ` Duncan
2015-04-06  9:29                     ` Duncan
2015-04-06 10:13                   ` Hugo Mills

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=201504060839.01726.russell@coker.com.au \
    --to=russell@coker.com.au \
    --cc=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