From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from plane.gmane.org ([80.91.229.3]:38801 "EHLO plane.gmane.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755257AbcCVRfR (ORCPT ); Tue, 22 Mar 2016 13:35:17 -0400 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1aiQCz-0005xH-Pr for linux-btrfs@vger.kernel.org; Tue, 22 Mar 2016 18:35:09 +0100 Received: from ip98-167-165-199.ph.ph.cox.net ([98.167.165.199]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 22 Mar 2016 18:35:09 +0100 Received: from 1i5t5.duncan by ip98-167-165-199.ph.ph.cox.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 22 Mar 2016 18:35:09 +0100 To: linux-btrfs@vger.kernel.org From: Duncan <1i5t5.duncan@cox.net> Subject: Re: overlay file to test btrfs repairs Date: Tue, 22 Mar 2016 17:34:58 +0000 (UTC) Message-ID: References: <56EFD981.7020606@gmail.com> <56F15505.1090807@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Sender: linux-btrfs-owner@vger.kernel.org List-ID: 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