From mboxrd@z Thu Jan 1 00:00:00 1970 From: Petro Subject: Re: [linux-lvm] invalidate: busy buffer Message-ID: <20011217004954.GA14300@auctionwatch.com> References: <20011214191634.GB24486@auctionwatch.com> <20011216205044.F26924@tiger.bigcats.invalid> Mime-Version: 1.0 Content-Disposition: inline In-Reply-To: <20011216205044.F26924@tiger.bigcats.invalid> Sender: linux-lvm-admin@sistina.com Errors-To: linux-lvm-admin@sistina.com Reply-To: linux-lvm@sistina.com List-Help: List-Post: List-Subscribe: , List-Unsubscribe: , List-Archive: Date: Sun Dec 16 18:47:02 2001 List-Id: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-lvm@sistina.com 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.