From: christophe.ochal@gmail.com
To: linux-lvm@lists.linux.dev
Subject: lvm2 weirdness in Fedora 40
Date: Sun, 16 Feb 2025 16:11:26 +0100 [thread overview]
Message-ID: <fa068a4eabaece5fcddca5ea5adf0557f26387a2.camel@gmail.com> (raw)
I'm at present fighting with LVM2, for some weird reason I can't get my
lvm volume
to be activated & mounted at boot resulting in me having to do
"vgchange -ay" at boot (after I'm dropped in a shell & prompted for my
root password,to make debugging even more troublesome I can only mess
with this over the weekends, i've included the lvmdump to this mail,
any more help would be very welcome, as i'm at a loss of how to
proceed. this might also have relevant information.
https://bugzilla.redhat.com/show_bug.cgi?id=2338735
next reply other threads:[~2025-02-16 15:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-16 15:11 christophe.ochal [this message]
2025-02-16 21:45 ` lvm2 weirdness in Fedora 40 Roger Heflin
2025-02-22 16:05 ` christophe.ochal
2025-02-22 16:55 ` Roger Heflin
2025-02-23 9:20 ` christophe.ochal
-- strict thread matches above, loose matches on Subject: below --
2025-02-16 15:05 christophe.ochal
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=fa068a4eabaece5fcddca5ea5adf0557f26387a2.camel@gmail.com \
--to=christophe.ochal@gmail.com \
--cc=linux-lvm@lists.linux.dev \
/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).