All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fred Donck <fred@donck.com>
To: linux-lvm@redhat.com
Subject: [linux-lvm] LVM upgrade
Date: Mon, 13 Nov 2006 13:19:00 +0100	[thread overview]
Message-ID: <20061113121900.GK276@dogbert> (raw)


*,

I am in the process of upgrading my Gentoo system and all that is stgill
to be done is LVM2

My current install is the following

host ~ # lvm version
  LVM version:     2.01.09 (2005-04-04)
  Library version: 1.01.00-ioctl (2005-01-17)
  Driver version:  4.4.0
host ~ # df -k
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/md2               1003932     64952    938980   7% /
/dev/vg/usr           10485436   3729092   6756344  36% /usr
/dev/vg/var           10485436    636380   9849056   7% /var
/dev/vg/tmp            4194172    494092   3700080  12% /tmp
/dev/vg/opt            4194172     35928   4158244   1% /opt
/dev/vg/home           4194172   3041392   1152780  73% /home
none                    248632         0    248632   0% /dev/shm
host ~ # 


The latest Gentoo version for LVM2 is

host ~ # emerge -p lvm2

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild     U ] sys-fs/device-mapper-1.02.10-r1 [1.01.00] USE="(-selinux)" 
[ebuild     U ] sys-fs/lvm2-2.02.06 [2.01.09] USE="-clvm% -cman% -gulm% -nolvm1% -nomirrors% -nosnapshots% (-selinux)" 
host ~ # 

Are there any problems i could expect when upgrading? 
Especially in the volume names or in the mapping of volume name to device
name for /etc/fstab.

Thanks in advance
-- 
Fred

Doubt is an uncomfortable situation, but certainty is an absurd one
	-- Voltaire

             reply	other threads:[~2006-11-13 12:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-13 12:19 Fred Donck [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-12-08 14:09 [linux-lvm] How do you mount a snapshot? Chris Mason
2000-12-08 15:08 ` [linux-lvm] LVM Upgrade Magnus Naeslund(f)

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=20061113121900.GK276@dogbert \
    --to=fred@donck.com \
    --cc=linux-lvm@redhat.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.