All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Wiedmer - FHBB <markus.wiedmer@stud.fhbb.ch>
To: linux-lvm@spam.dragonhold.org
Cc: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] VGs not detected at startup
Date: Mon, 8 Nov 2004 15:49:07 +0100	[thread overview]
Message-ID: <1535323208.20041108154907@stud.fhbb.ch> (raw)
In-Reply-To: <20041108135339.GA5797@dragonhold.org>

[-- Attachment #1: Type: text/plain, Size: 1078 bytes --]

llsdo> On Mon, Nov 08, 2004 at 02:46:31PM +0100, Markus Wiedmer - FHBB wrote:
>> I now found a work-around that seems to work so far. In the
>> LVM-Start-Script I just put "mount /dev/sda5 || true" before the vgscan. it
>> looks like after a mount-command the system suddenly finds the VG.
>> strange...

llsdo> Apologies if this is something that's already been
llsdo> discussed (if so I missed it), and also
llsdo> for saying something that you've almost definitely covered but......

llsdo> Check to see if there's any autoloading of modules, or
llsdo> anything, going on as a result of the
llsdo> mount/fdisk?

llsdo> Also (instead of the mount) does a 'dd' work?  E.g. dd
llsdo> if=/dev/sda of=/dev/null bs=512
llsdo> count=1?

llsdo> That's going to be faster & probably less intrusive.

llsdo> Graham

thanks a lot for your hint. it really was a module (sd_mod) that was
not loaded at boottime. everything works now like a charm

thanks

markus



-- 
Mit freundlichen Grüssen
Markus Wiedmer - FHBB
mailto:markus.wiedmer@stud.fhbb.ch


[-- Attachment #2: Type: application/pgp-signature, Size: 186 bytes --]

  reply	other threads:[~2004-11-08 14:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-08  8:16 [linux-lvm] VGs not detected at startup Markus Wiedmer - FHBB
2004-11-08  9:40 ` David S.
2004-11-08 13:46   ` Markus Wiedmer - FHBB
2004-11-08 13:53     ` linux-lvm
2004-11-08 14:49       ` Markus Wiedmer - FHBB [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-04-06 10:02 Diaz Rodriguez, Eduardo

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=1535323208.20041108154907@stud.fhbb.ch \
    --to=markus.wiedmer@stud.fhbb.ch \
    --cc=linux-lvm@redhat.com \
    --cc=linux-lvm@spam.dragonhold.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.