From: Hugo Mills <hugo@carfax.org.uk>
To: Pavel Volkov <sailor@lists.xtsubasa.org>
Cc: Russell Coker <russell@coker.com.au>,
Duncan <1i5t5.duncan@cox.net>,
linux-btrfs@vger.kernel.org
Subject: Re: Btrfs hangs 3.19-10
Date: Mon, 6 Apr 2015 10:13:38 +0000 [thread overview]
Message-ID: <20150406101338.GF13864@carfax.org.uk> (raw)
In-Reply-To: <2f6a9ac9-0684-4b9a-982e-031286be398e@lists.xtsubasa.org>
[-- Attachment #1: Type: text/plain, Size: 956 bytes --]
On Mon, Apr 06, 2015 at 10:40:03AM +0300, Pavel Volkov wrote:
> On Sunday, April 5, 2015 1:04:17 PM MSK, Hugo Mills wrote:
> > That's these, I think:
> >
> >#define BTRFS_FEATURE_INCOMPAT_BIG_METADATA (1ULL << 5)
> >#define BTRFS_FEATURE_INCOMPAT_EXTENDED_IREF (1ULL << 6)
> >
> >so it's definitely -O^extref. I don't see where big_metadata comes
> >from, though. That's not a -O option. Try with -O^extref and see where
> >that gets you. (Also, don't mount the FS on a newer kernel -- it may
> >be setting big metadata automatically, although it probably shouldn't
> >do).
>
> By the way, is there any way to see which options are enabled on a
> local filesystem without having to try mounting it with old kernel
> and checking dmesg?
btrfs-show-super is the tool for that.
Hugo.
--
Hugo Mills | Great oxymorons of the world, no. 4:
hugo@... carfax.org.uk | Future Perfect
http://carfax.org.uk/ |
PGP: E2AB1DE4 |
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2015-04-06 10:13 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
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 [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=20150406101338.GF13864@carfax.org.uk \
--to=hugo@carfax.org.uk \
--cc=1i5t5.duncan@cox.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=russell@coker.com.au \
--cc=sailor@lists.xtsubasa.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