From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: btrfs-raid questions I couldn't find an answer to on the wiki
Date: Wed, 1 Feb 2012 06:59:26 +0000 (UTC) [thread overview]
Message-ID: <pan.2012.02.01.06.59.25@cox.net> (raw)
In-Reply-To: COL113-DS1406F918FEA81D38635AA3B0730@phx.gbl
Kyle Gates posted on Tue, 31 Jan 2012 18:22:51 -0600 as excerpted:
> I don't think I specifically enabled mixed chunk support when I created
> this filesystem. It was done on a 2.6 kernel sometime in the middle of
> 2011 iirc.
Yeah, I'd guess that was before mixed-chunk, or at least before it became
the default for <=1GiB filesystems, so even if it was supported it
wouldn't have been the default.
Meaning there's still an open question as to whether grub-1.99 supports
mixed-chunk.
It looks like I might get more time to play with it this coming week than
I had this past week. I might try some of my own experiments... and
whether grub groks mixed-chunk will certainly be among them if I do.
As for those recommending something other than btrfs for /boot, yes,
that's a possibility, but I strongly prefer to standardize on a single
filesystem type. Right now, that's reiserfs for everything except flash-
based USB and legacy floppies (both of which I use ext4 without
journaling for, except for the floppies I used to update my BIOS, before
my 2003 era mainboard got EOLed; those were freedos images), and
ultimately, I hope it'll be btrfs for everything including flash-based
(tho perhaps not for legacy floppies, but it has been awhile since I used
one of them for anything, after that last BIOS update...).
Of course I'm going to keep reiserfs on my backups, even if I use btrfs
for my working system, for the time being since btrfs is still in heavy
development, but ultimately, I want to go all btrfs just as I'm all
reiserfs now, and that would include both /boot 2-spindle raid-1s.
Tho if btrfs doesn't work well for that ATM, I can keep /boot as reiserfs
for the time being, since I'm already keeping it for the backups, for the
time being.
--
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:[~2012-02-01 6:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-26 15:41 btrfs-raid questions I couldn't find an answer to on the wiki Duncan
2012-01-28 12:08 ` Martin Steigerwald
2012-01-29 5:40 ` Duncan
2012-01-29 7:55 ` Martin Steigerwald
2012-01-29 11:23 ` Goffredo Baroncelli
2012-01-30 5:49 ` Li Zefan
2012-01-30 14:58 ` Kyle Gates
2012-01-31 5:55 ` Duncan
2012-02-01 0:22 ` Kyle Gates
2012-02-01 6:59 ` Duncan [this message]
2012-02-10 19:45 ` Phillip Susi
2012-02-11 5:48 ` Duncan
2012-02-12 0:04 ` Phillip Susi
2012-02-12 22:31 ` 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=pan.2012.02.01.06.59.25@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 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.