Linux LVM users
 help / color / mirror / Atom feed
From: Ed Tomlinson <tomlins@cam.org>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] safe to ru-run vgscan after mounting LV root?
Date: Thu, 29 Mar 2001 07:34:00 -0500	[thread overview]
Message-ID: <01032907340001.12064@oscar> (raw)
In-Reply-To: <20010329163815.A30619@mail.wave.co.nz>

On Wednesday 28 March 2001 23:38, you wrote:
> On Tue, 27 Mar 2001, Patrick Caulfield wrote:
> > You can run vgscan as many times as you like. The main reason you
> > wouldn't is the time it can take. But even that is small compared to the
> > initialisation time
>
> Thanks for the feedback.  That's what I figured, but ...
>
> On Tue, Mar 27, 2001 at 11:01:50AM -0500, Jay Sissom wrote:
> > Just a warning.  When I run vgscan on my system, it deletes my LV.  I
> > still don't know why.  There seems to be a terrible bug in vgscan.

What release of the utilities/patch?  I had this problem with beta2, which
is what ships with the kernel.  Upgrading to beta6 fixed it _here_.

> ... this worries me.

Me too...  Here hoping that beta6 is the answer.

> Could anyone else comment on this, please?  Is Jay's problem bizzare
> and irreproducable, or is there possibly a problem with replacing the
> lvmtab files from beneath the noses of the other tools?

Ed Tomlinson

  reply	other threads:[~2001-03-29 12:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-27 14:14 [linux-lvm] safe to ru-run vgscan after mounting LV root? Mark van Walraven
2001-03-27 15:15 ` Patrick Caulfield
2001-03-27 16:01   ` Jay Sissom
2001-03-29  4:38     ` Mark van Walraven
2001-03-29 12:34       ` Ed Tomlinson [this message]
2001-03-29 14:46         ` Jay Sissom
2001-03-29 19:10           ` Andreas Dilger
2001-03-29 14:21       ` Patrick Caulfield

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=01032907340001.12064@oscar \
    --to=tomlins@cam.org \
    --cc=linux-lvm@sistina.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox