From nobody Sun Dec 25 16:32:55 2022 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Ng60h3r3Jz20jVm for ; Sun, 25 Dec 2022 16:33:08 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-ed1-x535.google.com (mail-ed1-x535.google.com [IPv6:2a00:1450:4864:20::535]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Ng60h1f9Gz4VMV for ; Sun, 25 Dec 2022 16:33:08 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ed1-x535.google.com with SMTP id i9so13248411edj.4 for ; Sun, 25 Dec 2022 08:33:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20210112.gappssmtp.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=oecEONUScIcgko7m4ktgTXdqZLmin9Qj3xWSacinJY4=; b=34a0b59+/Vlb85tPDCZMh0bKrBtPRAgtCXWHV8JwCzqyQXrOca1wBEFucmh7qUQv0K Eh3yoHtD5mugRY4Y3OXrcxQbjlAmuEinko52U0XUARwk5nuWgBTnTUhpch6TxKCJT3ap 6czND1Z+BzBcXX6esxFYcCG+2WFNPYXpQ+ma/fb+5MPpoxD9aV8/zVCm64A90sMmvSXp 7GmjSiKH1eKZE6s256BHh5FHxizdR+OoxS80EZKgxNLM55Cf+6bYIBK06Or9YkvDOIH+ YkFg2Z6+SyiWzjBBpmnLPqcPOkp6FaY/q2Y8YyndxFo1R+jcdM4jGkqf1z8D52VSyNkc g/qg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=oecEONUScIcgko7m4ktgTXdqZLmin9Qj3xWSacinJY4=; b=pve96oDfZ+q7xTwKulw98vEFIA4CKtYOmNlhUB7/RB6dQr2TO1RYi6IC7KVDNSCkZb K9TXynvxcHeGrfPVp5TWynhds8O83yjLNnwNI1sMT6XbjpB8HM2gt4eOGQcBISjKloAw B6tMcDhJeoTCnHgQbdRhGlBnGIAd5ntPK9S07PU8LVh95qGT/qGPZWCTZ1yRK0tLzHG8 4MwT9yBK4P9nwUPqeVHrYxiX39zNJTZss1FjYq57MES0R/gDQJ9pfu/7tdzd4cjkzIkq aBmX0iTS484prU2mofVBEY26uRsmw6GutHGkOhsAW11Ar06WvtQNh4TFXp1POTPZPaWl eRKA== X-Gm-Message-State: AFqh2kpimI7YVgMamPcDFARxzQOPNJ9NxAAgB5B0DR2lBOYQWGTwXAif U80utu0PljHYiJOc/c80XL8ryExoDAOc/GICpbQ0dKH+VG26vg== X-Google-Smtp-Source: AMrXdXtJ8krMv57QakxtqUU3skxQLn16Enph3eOKJbhP2jtQpU5Yt0+w5YxcExcvRrFo+DexGx5p9sivWSQuHHYN1SA= X-Received: by 2002:a05:6402:1f02:b0:47f:6531:deed with SMTP id b2-20020a0564021f0200b0047f6531deedmr1001237edb.154.1671985986313; Sun, 25 Dec 2022 08:33:06 -0800 (PST) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 References: In-Reply-To: From: Warner Losh Date: Sun, 25 Dec 2022 09:32:55 -0700 Message-ID: Subject: Re: Disk partitions disappear when mounting others To: Alexey Dokuchaev Cc: FreeBSD Current Content-Type: multipart/alternative; boundary="000000000000c8b81e05f0a9929f" X-Rspamd-Queue-Id: 4Ng60h1f9Gz4VMV X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --000000000000c8b81e05f0a9929f Content-Type: text/plain; charset="UTF-8" On Sun, Dec 25, 2022, 1:02 AM Alexey Dokuchaev wrote: > Hi there, > > I'm in the process of moving my data from a dying HDD, and just noticed > something weird. It's an MBR partitioned drive, and there is a FreeBSD > slice and Fedora LVM in EBR, accessible as > /dev/linux_lvm/fedora-{swap,home,root}. > > The problem is that once I mount my old FreeBSD partition, e.g. > /dev/ada0s2a, those LVM nodes are gone, logging this: > > GEOM_LINUX_LVM: disk pv0 already initialised in fedora > GEOM_LINUX_LVM: Disk diskid/DISK-XXXXXXX1s4+00000001 removed from pv0. > GEOM_LINUX_LVM: Device linux_lvm/fedora-swap removed. > GEOM_LINUX_LVM: Device linux_lvm/fedora-home removed. > GEOM_LINUX_LVM: Device linux_lvm/fedora-root removed. > > If I unmount /dev/ada0s2a and mount any Fedora's partition, then I can > longer access other slices as there's only /dev/ada0 remains; ``gpart > show'' > also does not list them, but only those under diskid/DISK-XXXXXXX1. > > Why is this happening? What should I fix to stop my partitions from > disappearing and reappearing? Something has them open. My guess is the Linux lvm geom provider opens too many things. It's been standard geom behavior to remove the other device aliases in /dev when one is open. Though the problem may be in tasting during open since gpart list shows them gone. Warner Thanks, > > ./danfe > > --000000000000c8b81e05f0a9929f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Sun, Dec 25, 2022, 1:02 AM Alexey Dokuchaev <danfe@freebsd.org> wrote:
Hi there,

I'm in the process of moving my data from a dying HDD, and just noticed=
something weird.=C2=A0 It's an MBR partitioned drive, and there is a Fr= eeBSD
slice and Fedora LVM in EBR, accessible as /dev/linux_lvm/fedora-{swap,home= ,root}.

The problem is that once I mount my old FreeBSD partition, e.g.
/dev/ada0s2a, those LVM nodes are gone, logging this:

=C2=A0 GEOM_LINUX_LVM: disk pv0 already initialised in fedora
=C2=A0 GEOM_LINUX_LVM: Disk diskid/DISK-XXXXXXX1s4+00000001 removed from pv= 0.
=C2=A0 GEOM_LINUX_LVM: Device linux_lvm/fedora-swap removed.
=C2=A0 GEOM_LINUX_LVM: Device linux_lvm/fedora-home removed.
=C2=A0 GEOM_LINUX_LVM: Device linux_lvm/fedora-root removed.

If I unmount /dev/ada0s2a and mount any Fedora's partition, then I can<= br> longer access other slices as there's only /dev/ada0 remains; ``gpart s= how''
also does not list them, but only those under diskid/DISK-XXXXXXX1.

Why is this happening?=C2=A0 What should I fix to stop my partitions from disappearing and reappearing?
Something has them open. My guess is the Linux lvm= geom provider opens too many things. It's been standard geom behavior = to remove the other device aliases in /dev when one is open.=C2=A0

Though the problem may be in tas= ting during open since gpart list shows them gone.=C2=A0

Warner

= Thanks,

./danfe

--000000000000c8b81e05f0a9929f--