On Wed, Aug 12, 2015 at 11:43 AM, Hugo Mills <h...@carfax.org.uk> wrote: > [adding Ulli back into the cc list] > > On Wed, Aug 12, 2015 at 11:03:00AM -0600, Chris Murphy wrote: >> On Wed, Aug 12, 2015 at 7:07 AM, Ulli Horlacher >> <frams...@rus.uni-stuttgart.de> wrote: >> >> > /dev/sdb and /dev/sde are in reality the same physical disk! >> >> When does all of this confusion happen? Is it already confused before >> mkfs or only after mkfs or only after mount? I would find out what >> instigates it, wipe all signatures from everything, reboot, start from >> scratch, and then strace the command that causes the confusion. And >> attach that output as well as the entire dmesg to a bug report. Just >> my 2 cents, I have no idea what's going on but sounds like a block >> layer and/or drdb bug that's triggered by Btrfs multiple device >> setups. > > If (some of) the DRBD host devices are also physically present on > the machine to which the DRBDs are exported, then you're in the same > situation as having block-level snapshots or dd copies of the data -- > the FS will see two devices (the backing store and the DRBD) which are > have the same UUID. It will pick an arbitrary one to write to, which > is probably not something that the DRBD driver will cope with very > well, I suspect. > > I think the solution here would be to blacklist the backing store > from btrfs dev scan. I recall that there was such a capability at some > point -- I don't know if it made it into the userspace tools?
That makes sense. But then this would also affect XFS also I'd think, except XFS will refuse to mount if the kernel sees two of the same fs UUID. -- Chris Murphy -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
