All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luca Berra <bluca@comedia.it>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] is devfs required?
Date: Sat Feb 23 07:28:02 2002	[thread overview]
Message-ID: <20020223132843.GA1747@colombina.comedia.it> (raw)
In-Reply-To: <20020222214037.A28086@majestic.ukshells.co.uk>

On Fri, Feb 22, 2002 at 09:40:37PM +0000, Vincent AE Scott wrote:
> errr, are you saying that it's not possible to switch between devfs and
> non-devfs, as soon as you use the former?
well, the issue is that the lvm device cache does not cope with
variyng device names, as happens when using devfs (i.e. you have both
/dev/scsi/host0/bus0/target0/lun0/part1
and
/dev/sda1
to reference the same partitin

the worst case is when you have devfs compiled in and not mounted,
so /proc/partitions holds the long device name, but /dev contains
only the short one.

> oh, i've just thought of one other thing, that maybe? caused a problem:
> i did create a LV and copied my entire /fs into it, then rebooted into
> it to see if it all worked.  havent used it since tho.
> 
> is it possible that the data in /etc/lvm* on the original and LVM copied
> partitions were not quite in sync with what was on disk?

the data in /etc/lvmtab.d can be recreated by using vgscan
that in /etc/lvmconf by vgcfgbackup

L.

-- 
Luca Berra -- bluca@comedia.it
        Communication Media & Services S.r.l.
 /"\
 \ /     ASCII RIBBON CAMPAIGN
  X        AGAINST HTML MAIL
 / \

      reply	other threads:[~2002-02-23  7:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-21  8:36 [linux-lvm] is devfs required? Vincent AE Scott
2002-02-22  3:25 ` Heinz J . Mauelshagen
2002-02-22  8:21 ` Benjamin Scott
2002-02-22 14:15   ` Luca Berra
2002-02-22 14:13 ` Luca Berra
2002-02-22 15:40   ` Vincent AE Scott
2002-02-23  7:28     ` Luca Berra [this message]

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=20020223132843.GA1747@colombina.comedia.it \
    --to=bluca@comedia.it \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.