From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Btrfs hangs 3.19-10
Date: Sun, 5 Apr 2015 03:16:21 +0000 (UTC) [thread overview]
Message-ID: <pan$bf795$4bdcf130$e29eb18a$9b854964@cox.net> (raw)
In-Reply-To: 20150404130047.GC13864@carfax.org.uk
Hugo Mills posted on Sat, 04 Apr 2015 13:00:47 +0000 as excerpted:
> On Sat, Apr 04, 2015 at 12:55:08PM +0000, Russell Coker wrote:
>
>> As an aside are there options to mkfs.btrfs that would make a
>> filesystem mountable by kernel 3.2.65? If so I'll file a Debian/Jessie
>> bug report requesting that a specific mention be added to the man page.
>
> Yes, there are. It's probably -O^extref, but if you can show the
> dmesg output from the 3.2 kernel on the failed mount (so that it shows
> what the actual failure was), we should be able to give you a more
> precise answer.
So I was thinking about this, and the several other earlier options where
support wasn't added until kernel X, and had an idea...
How easy and useful might it be to add to mkfs.btrfs appropriate option-
group aliases such that if one knew the oldest kernel one was likely to
deal with, all one would need to do for the mkfs would be to set for
example, -O3.2, or even simply --3.2 (or maybe even --32), and have
mkfs.btrfs automatically set/unset the appropriate options so it would
"just work" with that kernel and anything newer?
I imagine that could be a very useful feature for some, and I can't
imagine it being too hard to setup the aliases since after all that
should be all that's necessary, so what's left is to decide if it'd
actually be useful enough to enough people to bother implementing and
documenting...
--
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
next prev parent reply other threads:[~2015-04-05 3:16 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 [this message]
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
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$bf795$4bdcf130$e29eb18a$9b854964@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