linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: lazytime mount option—no support in Btrfs
Date: Thu, 23 Aug 2018 04:46:10 +0000 (UTC)	[thread overview]
Message-ID: <pan$5bac3$e653290f$955bc939$6fc721ed@cox.net> (raw)
In-Reply-To: 3a460831-0924-7615-0977-b32ab82cbece@gmail.com

Austin S. Hemmelgarn posted on Wed, 22 Aug 2018 07:30:09 -0400 as
excerpted:

>> Meanwhile, since broken rootflags requiring an initr* came up let me
>> take the opportunity to ask once again, does btrfs-raid1 root still
>> require an initr*?  It'd be /so/ nice to be able to supply the
>> appropriate rootflags=device=...,device=... and actually have it work
>> so I didn't need the initr* any longer!

> Last I knew, specifying appropriate `device=` options in rootflags works
> correctly without an initrd.

Just to confirm, that's with multi-device btrfs rootfs?  Because it used 
to work when the btrfs was single-device, but not multi-device.

(For multi-device, or at least raid1, one had to add degraded, also, or 
it would refuse to mount despite all the appropriate device= entries in 
rootflags, thus of course risking all the problems running degraded raid1 
operationally can bring, tho I never figured out for sure whether btrfs 
was smart enough to eventually pick up the other devices, after the scan 
before bringing other btrfs online or not, but either way it was a risk I 
wasn't willing to take.)

-- 
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

  reply	other threads:[~2018-08-23  8:16 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-13 11:50 lazytime mount option—no support in Btrfs Adam Hunt
2017-08-14 13:19 ` Austin S. Hemmelgarn
2018-08-18 20:45 ` waxhead
2018-08-19  8:37   ` Martin Steigerwald
2018-08-19 10:25     ` Andrei Borzenkov
2018-08-20 12:16       ` Austin S. Hemmelgarn
2018-08-21 12:06         ` Adam Borowski
2018-08-21 12:17           ` Austin S. Hemmelgarn
2018-08-21 13:32             ` Janos Toth F.
2018-08-21 14:10               ` Austin S. Hemmelgarn
2018-08-21 16:05                 ` David Sterba
2018-08-21 17:01                   ` Austin S. Hemmelgarn
2018-08-22  3:57                     ` Duncan
2018-08-22 11:30                       ` Austin S. Hemmelgarn
2018-08-23  4:46                         ` Duncan [this message]
2018-08-22 13:48                     ` David Sterba
2018-08-22 13:56                       ` Austin S. Hemmelgarn
2018-08-22 15:01                         ` David Sterba
2018-08-22 16:59                           ` Austin S. Hemmelgarn
2018-08-23 23:33                 ` Janos Toth F.

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$5bac3$e653290f$955bc939$6fc721ed@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;
as well as URLs for NNTP newsgroup(s).