invalidate: busy buffer
Setup: 4 IBM drives attached to a 3ware raid card (64xx), in a raid 0 configuration, as /dev/sdb.
Trying to set up LVM on it, run vgscan and get:
vgscan -- reading all physical volumes (this may take a while...)
invalidate: busy buffer
invalidate: busy buffer
invalidate: busy buffer
invalidate: busy buffer
invalidate: busy buffer
invalidate: busy buffer
invalidate: busy buffer
invalidate: busy buffer
invalidate: busy buffer
invalidate: busy buffer
invalidate: busy buffer
vgscan -- "/etc/lvmtab" and "/etc/lvmtab.d" successfully created vgscan -- WARNING: This program does not do a VGDA backup of your volume group
Is this a warning from LVM? If so, what does it mean (and if not, if anyone does know what it means, I'd be really glad to find out).
thanks.
Signature · 1 line
Share and Enjoy.
Hi, Petro!
Petro ([email protected]) wrote 37 lines:
Quoted 3 lines
vgscan -- reading all physical volumes (this may take a while...)
invalidate: busy buffer
invalidate: busy buffer
I have been told that these (at vgscan) are spurious and not dangerous.
Quoted 3 lines
vgscan -- "
/etc/lvmtab" and "/etc/lvmtab.d" successfully created vgscan -- WARNING: This program does not do a VGDA backup of your volume group
This warning is non-critical, just a friendly remainder.
BTW, is there a good reason to run vgscan on boot time every time? I have had more sorrow than joy with that. If my vg's really changed, I can always run it from the (non-LVM) / which will come up, even if only as an emergency system.
-Wolfgang
Hi,
Quoted 4 lines · Wolfgang Weisselberg
BTW, is there a good reason to run vgscan on boot time every time? I have had more sorrow than joy with that. If my vg's really changed, I can always run it from the (non-LVM) / which will come up, even if only as an emergency system.
Ok, but you need to run vgscan && vgchange -ay every time you wanna use your LVM-drives, and I think that's normally every time you boot your PC.
I won't run the commands every time I reboot manually. But... I add them to /etc/rcS.d/S99local incl. the mount command. This takes nearly the same effect as if I run it manually after the booting finished.
Regards
Uli
Signature · 1 line
'The box said, 'Requires Windows 95 or better', so i installed Linux - TKK 5
Hi, Ulrich!
Ulrich Wiederhold ([email protected]) wrote 26 lines:
Quoted 9 lines · Wolfgang Weisselberg
Quoted 4 lines
BTW, is there a good reason to run vgscan on boot time every time? I have had more sorrow than joy with that. If my vg's really changed, I can always run it from the (non-LVM) / which will come up, even if only as an emergency system.
Ok, but you need to run vgscan && vgchange -ay every time you wanna use your LVM-drives, and I think that's normally every time you boot your PC.
Funny, my PC boots and mounts the LVs even though I commented out vgscan entirely in the boot process. vgchange is another thing, though...
Quoted 2 lines
But... I add them
to/etc/rcS.d/S99localincl. the mount command.
Faaar to late -- considering that all the daemons start up early and need fancy things like /usr, /var and sometimes /tmp ..
-Wolfgang
Hi,
Quoted 2 lines · Wolfgang Weisselberg
Faaar to late -- considering that all the daemons start up early and need fancy things like /usr, /var and sometimes /tmp ..
ok. I only have data on lvm-drives, so it won't bother me if it's mounted lately.
Uli
Signature · 1 line
'The box said, 'Requires Windows 95 or better', so i installed Linux - TKK 5
My $0.02 ..
I never run vgscan unless I change my LVM configuration. vgchange -a y of course must be run prior to mounting LVM volumes. The one caveat is that /proc must be mounted, and if root is mounted read only, as it usually is on boot, you have to use the -n option to mount it.
So one may find early in my slackware rc.S file:
mount -n /proc/sbin/vgchange -a y
umount -n /proc
yes, I umount /proc so the rc.S can mount it "normally" later.
-- todd --
Quoted 44 lines
X-Apparently-To: [email protected] via web13608.mail.yahoo.com; 16 Dec 2001 19:15:50 -0800 (PST)
X-RocketRCL: 1105;1;82599241
X-Track: -10
From: Wolfgang Weisselberg <[email protected]>
Mail-Followup-To: [email protected]
Content-Disposition: inline
Sender: [email protected]
Reply-To: [email protected]
X-Original-Date: Mon, 17 Dec 2001 03:53:59 +0100
Date: Mon, 17 Dec 2001 03:53:59 +0100Hi, Ulrich!
Ulrich Wiederhold ([email protected]) wrote 26 lines:
Quoted 9 lines · Wolfgang Weisselberg
Quoted 4 lines
BTW, is there a good reason to run vgscan on boot time every time? I have had more sorrow than joy with that. If my vg's really changed, I can always run it from the (non-LVM) / which will come up, even if only as an emergency system.
Ok, but you need to run vgscan && vgchange -ay every time you wanna use your LVM-drives, and I think that's normally every time you boot your PC.
Funny, my PC boots and mounts the LVs even though I commented out vgscan entirely in the boot process. vgchange is another thing, though...
Quoted 2 lines
But... I add them
to/etc/rcS.d/S99localincl. the mount command.Faaar to late -- considering that all the daemons start up early and need fancy things like /usr, /var and sometimes /tmp ..
-Wolfgang
_______________________________________________
linux-lvm mailing list
[email protected]
http://lists.sistina.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html
Quoted 7 lines · Wolfgang Weisselberg
Hi, Petro!
Petro ([email protected]) wrote 37 lines:Quoted 3 lines
vgscan -- reading all physical volumes (this may take a while...)
invalidate: busy buffer
invalidate: busy bufferI have been told that these (at vgscan) are spurious and not dangerous.
I was more or less wondering where they can from. Somtimes I get them, sometimes I don't, and we've been trying to map the error modes of a particular setup.
Quoted 5 lines
Quoted 3 lines
vgscan -- "
/etc/lvmtab" and "/etc/lvmtab.d" successfully created vgscan -- WARNING: This program does not do a VGDA backup of your volume groupThis warning is non-critical, just a friendly remainder.
Yeah, I knew about that last bit. It was the invalidate I was wondering about.
Thanks.
Quoted 12 lines
BTW, is there a good reason to run vgscan on boot time every time? I have had more sorrow than joy with that. If my vg's really changed, I can always run it from the (non-LVM) / which will come up, even if only as an emergency system.
-Wolfgang
_______________________________________________
linux-lvm mailing list
[email protected]
http://lists.sistina.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html
Signature · 1 line
Share and Enjoy.
Quoted 4 lines · Wolfgang Weisselberg
BTW, is there a good reason to run vgscan on boot time every time? I have had more sorrow than joy with that. If my vg's really changed, I can always run it from the (non-LVM) / which will come up, even if only as an emergency system.
It is only really useful if your drive mappings are likely to change (i.e. adding SCSI drives, or re-arranging your IDE drives). Otherwise, it is not necessary to run vgscan at boot.
IMHO, the concept of running "vgscan" at boot is flawed, because it re-builds the entire _VG_ setup each time it is run. I would much rather only rebuild the _PV_ setup on each boot (which is the only likely thing to change between reboots), and leave the VG setup alone. It should be up to the sysadmin to change the VG config.
Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/