From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: overlay file to test btrfs repairs
Date: Tue, 22 Mar 2016 17:34:58 +0000 (UTC) [thread overview]
Message-ID: <pan$9cb9a$185b2e9b$7b5df63f$77a1558e@cox.net> (raw)
In-Reply-To: 56F15505.1090807@gmail.com
Austin S. Hemmelgarn posted on Tue, 22 Mar 2016 10:21:57 -0400 as
excerpted:
> OTOH, if we could add some way to tell the code (both userspace and
> in-kernel) to explicitly ignore specific devices when trying to assemble
> filesystems, that would allow us to use DM snapshots (or something
> similar) to do this, and would also allow people to work around the UUID
> issues when dealing with LVM snapshots (or similar situations).
That's a good idea, but minor detail, it'd need to resolve to specific
block-device major:minor comparison; it couldn't be a simple device-path
blacklist, because device paths are routinely symlinked.
I guess that's obvious from a kernel dev perspective, but perhaps not so
much from an admin-user perspective, where the device-path /is/ often
considered the device.
--
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:[~2016-03-22 17:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-21 3:43 overlay file to test btrfs repairs Chris Murphy
2016-03-21 9:55 ` Duncan
2016-03-21 11:22 ` Austin S. Hemmelgarn
2016-03-21 17:13 ` Chris Murphy
2016-03-22 14:21 ` Austin S. Hemmelgarn
2016-03-22 17:34 ` Duncan [this message]
2016-03-23 19:45 ` Goffredo Baroncelli
2016-03-22 20:42 ` Henk Slager
2016-03-23 11:17 ` Austin S. Hemmelgarn
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$9cb9a$185b2e9b$7b5df63f$77a1558e@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