* [linux-lvm] 'vgscan' at boot-up
@ 2004-11-06 1:12 David S.
2004-11-06 9:58 ` Sander
2004-11-07 16:52 ` Luca Berra
0 siblings, 2 replies; 3+ messages in thread
From: David S. @ 2004-11-06 1:12 UTC (permalink / raw)
To: linux-lvm
I'm using lvm2-2.00.15 and device-mapper-1.00.17 on a Slackware (x86)
system, with a 2.6.9 kernel and udev-026. I've created a volume
group and a logical volume without any trouble, but the file system
I built on the volume won't mount at boot-up. That's apparently
because the 'vgscan' program run from the system initialization
script does not find an volume groups. After the system boots,
'vgscan' works fine. I can get the file system mounted by putting
/sbin/vgscan 2>/dev/null
sleep 10
/sbin/vgchange -ay
/sbin/mount -a
in 'rc.local'. Does anyone have a idea why 'vgscan' would fail
in the sytem initialization script, but succeed in 'rc.local'?
David S.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [linux-lvm] 'vgscan' at boot-up
2004-11-06 1:12 [linux-lvm] 'vgscan' at boot-up David S.
@ 2004-11-06 9:58 ` Sander
2004-11-07 16:52 ` Luca Berra
1 sibling, 0 replies; 3+ messages in thread
From: Sander @ 2004-11-06 9:58 UTC (permalink / raw)
To: LVM general discussion and development
David S. wrote:
>I'm using lvm2-2.00.15 and device-mapper-1.00.17 on a Slackware (x86)
>system, with a 2.6.9 kernel and udev-026. I've created a volume
>group and a logical volume without any trouble, but the file system
>I built on the volume won't mount at boot-up. That's apparently
>because the 'vgscan' program run from the system initialization
>script does not find an volume groups. After the system boots,
>'vgscan' works fine. I can get the file system mounted by putting
>
> /sbin/vgscan 2>/dev/null
> sleep 10
> /sbin/vgchange -ay
> /sbin/mount -a
>
>in 'rc.local'. Does anyone have a idea why 'vgscan' would fail
>in the sytem initialization script, but succeed in 'rc.local'?
>
>David S.
>
>_______________________________________________
>linux-lvm mailing list
>linux-lvm@redhat.com
>https://www.redhat.com/mailman/listinfo/linux-lvm
>read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
>
>
>
>
What version of Slackware? I use LVM with 8.1 and 9.1. In 9.1 it should
work 'out-of-the-box' in 8.1 I had to put the LVM mounting stuf my
self. Did you put / on a logical volume? Is /proc mounted before you
try to bring the volumes online (i remember I had to do that in 8.1)
Sander
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [linux-lvm] 'vgscan' at boot-up
2004-11-06 1:12 [linux-lvm] 'vgscan' at boot-up David S.
2004-11-06 9:58 ` Sander
@ 2004-11-07 16:52 ` Luca Berra
1 sibling, 0 replies; 3+ messages in thread
From: Luca Berra @ 2004-11-07 16:52 UTC (permalink / raw)
To: linux-lvm
On Fri, Nov 05, 2004 at 05:12:59PM -0800, David S. wrote:
>
>I'm using lvm2-2.00.15 and device-mapper-1.00.17 on a Slackware (x86)
>system, with a 2.6.9 kernel and udev-026. I've created a volume
>group and a logical volume without any trouble, but the file system
>I built on the volume won't mount at boot-up. That's apparently
>because the 'vgscan' program run from the system initialization
>script does not find an volume groups. After the system boots,
>'vgscan' works fine. I can get the file system mounted by putting
...
>in 'rc.local'. Does anyone have a idea why 'vgscan' would fail
>in the sytem initialization script, but succeed in 'rc.local'?
>
wild guess,
udev has not yet created the block device file you require,
try putting udevstart in the system initialization script before vgscan
Regards,
L.
--
Luca Berra -- bluca@comedia.it
Communication Media & Services S.r.l.
/"\
\ / ASCII RIBBON CAMPAIGN
X AGAINST HTML MAIL
/ \
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2004-11-07 16:53 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-11-06 1:12 [linux-lvm] 'vgscan' at boot-up David S.
2004-11-06 9:58 ` Sander
2004-11-07 16:52 ` Luca Berra
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox