[linux-lvm] Invalidate: Busy Buffer

[linux-lvm] Invalidate: Busy Buffer

[mikyy]

Hello,

I am running a "clean" 2.4.13 kernel patched with the latest LVM tools (LVM 1.0.1-rc4) and compiled (as a module) with gcc 3.0 on Suse 7.1 with reiserfs 3.6.x filesystems and I am getting a "invalidate: busy buffer" message..
I tryed to search if anyone posted a similar message but did not find the answer.

Could you please help me?
Please cc me as I am not subscribed to this mailing list.

Thanks and cheers,

Michele

Re: [linux-lvm] Invalidate: Busy Buffer

[Ulrich Wiederhold]

Hi,
same here with 2.4.13, xfs and lvm.
But lvm works without Problems.
Uli

* mikyy@tin.it <mikyy@tin.it> [011107 10:37]:
> Hello,
> 
> I am running a "clean" 2.4.13 kernel patched with the latest LVM tools (LVM 1.0.1-rc4) and compiled (as a module) with gcc 3.0 on Suse 7.1 with reiserfs 3.6.x filesystems and I am getting a "invalidate: busy buffer" message..
> I tryed to search if anyone posted a similar message but did not find the answer.
> 
> Could you please help me?
> Please cc me as I am not subscribed to this mailing list.
> 
> Thanks and cheers,
> 
> Michele
> 
> 
> 
> 
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html
-- 
'The box said, 'Requires Windows 95 or better', so i installed Linux - TKK 5

Re: [linux-lvm] Invalidate: Busy Buffer

[Heinz J . Mauelshagen]

On Wed, Nov 07, 2001 at 10:37:17AM +0100, mikyy@tin.it wrote:
> Hello,
> 
> I am running a "clean" 2.4.13 kernel patched with the latest LVM tools (LVM 1.0.1-rc4) and compiled (as a module) with gcc 3.0 on Suse 7.1 with reiserfs 3.6.x filesystems and I am getting a "invalidate: busy buffer" message..

Older kernels were quiet about this.
No negative impact on LVM/your data is caused by this.

We'll check, if we need the invalidation still...

> I tryed to search if anyone posted a similar message but did not find the answer.
> 
> Could you please help me?
> Please cc me as I am not subscribed to this mailing list.
> 
> Thanks and cheers,
> 
> Michele
> 
> 
> 
> 
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html

-- 

Regards,
Heinz    -- The LVM Guy --

*** Software bugs are stupid.
    Nevertheless it needs not so stupid people to solve them ***

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Heinz Mauelshagen                                 Sistina Software Inc.
Senior Consultant/Developer                       Am Sonnenhang 11
                                                  56242 Marienrachdorf
                                                  Germany
Mauelshagen@Sistina.com                           +49 2626 141200
                                                       FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Re: [linux-lvm] Invalidate: Busy Buffer

[joan]

Hey,
I am usig a RedHat 7.1 with kernel 2.4.13 with the same LVM tools and I've 
the same problem. I recompiled with -O (not with -O2) but this only solves 
the core dump error. 

Thanxs
Joan

> Hello,
> 
> I am running a "clean" 2.4.13 kernel patched with the latest LVM tools
> (LVM 1.0.1-rc4) and compiled (as a module) with gcc 3.0 on Suse 7.1
> with reiserfs 3.6.x filesystems and I am getting a "invalidate: busy
> buffer" message.. I tryed to search if anyone posted a similar message
> but did not find the answer.
> 
> Could you please help me?
> Please cc me as I am not subscribed to this mailing list.
> 
> Thanks and cheers,
> 
> Michele
> 
> 
> 
> 
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html


----------------------------------------------------
Joan Manel L�pez Francesch 
Webmaster
mailto://joan@cat-linux.com 
http://www.cat-linux.com 
ICQ#:15276175 
PGP: http://www.cat-linux.com/downloads/joan-pgp.asc

[linux-lvm] invalidate: busy buffer

[Petro]

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.


-- 
Share and Enjoy. 

Re: [linux-lvm] invalidate: busy buffer

[Wolfgang Weisselberg]

Hi, Petro!

Petro (petro@auctionwatch.com) wrote 37 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.

> 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

Re: [linux-lvm] invalidate: busy buffer

[Ulrich Wiederhold]

Hi,
* Wolfgang Weisselberg <weissel@netcologne.de> [011216 20:50]:
> 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

-- 
'The box said, 'Requires Windows 95 or better', so i installed Linux - TKK 5

Re: [linux-lvm] invalidate: busy buffer

[Wolfgang Weisselberg]

Hi, Ulrich!

Ulrich Wiederhold (U.Wiederhold@gmx.net) wrote 26 lines:

> * Wolfgang Weisselberg <weissel@netcologne.de> [011216 20:50]:
> > 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...

> But... I add them
> to /etc/rcS.d/S99local incl. 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

Re: [linux-lvm] invalidate: busy buffer

[Ulrich Wiederhold]

Hi,
* Wolfgang Weisselberg <weissel@netcologne.de> [011217 03:53]:
> 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

-- 
'The box said, 'Requires Windows 95 or better', so i installed Linux - TKK 5

Re: [linux-lvm] invalidate: busy buffer

[Todd M. Roy]

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 --

>  X-Apparently-To: todd_m_roy@yahoo.com via web13608.mail.yahoo.com; 16 Dec 2001 19:15:50 -0800 (PST)
>  X-RocketRCL: 1105;1;82599241
>  X-Track: -10
>  From: Wolfgang Weisselberg <weissel@netcologne.de>
>  Mail-Followup-To: linux-lvm@sistina.com
>  Content-Disposition: inline
>  Sender: linux-lvm-admin@sistina.com
>  Reply-To: linux-lvm@sistina.com
>  X-Original-Date: Mon, 17 Dec 2001 03:53:59 +0100
>  Date: Mon, 17 Dec 2001 03:53:59 +0100
>  
>  Hi, Ulrich!
>  
>  Ulrich Wiederhold (U.Wiederhold@gmx.net) wrote 26 lines:
>  
>  > * Wolfgang Weisselberg <weissel@netcologne.de> [011216 20:50]:
>  > > 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...
>  
>  > But... I add them
>  > to /etc/rcS.d/S99local incl. 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
>  linux-lvm@sistina.com
>  http://lists.sistina.com/mailman/listinfo/linux-lvm
>  read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html
>  

Re: [linux-lvm] invalidate: busy buffer

[Petro]

On Sun, Dec 16, 2001 at 08:50:44PM +0100, Wolfgang Weisselberg wrote:
> Hi, Petro!
> Petro (petro@auctionwatch.com) wrote 37 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.

    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. 

> > 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.

    Yeah, I knew about that last bit. It was the invalidate I was
    wondering about.

    Thanks.

> 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
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html

-- 
Share and Enjoy. 

Re: [linux-lvm] invalidate: busy buffer

[Andreas Dilger]

On Dec 16, 2001  20:50 +0100, Wolfgang Weisselberg wrote:
> 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/