From: Jim Cromie <jcromie@divsol.com>
To: linux-lvm@sistina.com
Subject: [linux-lvm] success report 2.4.10 + 1.0.1-rc2 + diff
Date: Fri, 28 Sep 2001 00:15:29 -0600 [thread overview]
Message-ID: <3BB41580.A3F6ECDB@divsol.com> (raw)
In-Reply-To: 3B54F04E.4FEF132@americasm01.nt.com
fwiw,
Im pleased to report success using linux-2.4.10, LVM-1.0.1-rc2,
and this patch: http://incandescent.mp3revolution.net/lvm/inline_fix.diff
on a basically stock RH-7.1 installation.
I made 1 minor patch to /etc/rc.d/rc.sysinit, probably theres a better
way..
+ # LVM initialization
+ action "loading LVM:" /sbin/insmod lvm-mod
if [ -e /proc/lvm -a -x /sbin/vgchange -a -f /etc/lvmtab ]; then
action $"Setting up LVM:" /sbin/vgscan && /sbin/vgchange -a y
fi
and possibly a couple manual edits to lvm-*.c;
min(z,x,y) -> min(x,y), max() too
so now, bootup works, and shows results as follows
[jimc@groucho jimc]$ df
Filesystem 1k-blocks Used Available Use% Mounted on
...
/dev/hdc5 4031656 3762168 64692 99% /home
/dev/_vgb/vl_tmp 495844 24 470220 1% /tmp
/dev/_vgb/vl_t2 1511856 326156 1108900 23% /mnt/new
[root@groucho /root]# vgdisplay
--- Volume group ---
VG Name _vgb
VG Access read/write
VG Status available/resizable
VG # 0
MAX LV 255
Cur LV 2
Open LV 2
MAX LV Size 255.99 GB
Max PV 255
Cur PV 1
Act PV 1
VG Size 9.36 GB
PE Size 4.00 MB
Total PE 2397
Alloc PE / Size 500 / 1.95 GB
Free PE / Size 1897 / 7.41 GB
VG UUID 6w4vI8-x2Qp-rqFg-soa6-eYOF-2Uwp-8sB7z8
[root@groucho /root]# lvdisplay /dev/_vgb/vl_t*
--- Logical volume ---
LV Name /dev/_vgb/vl_t2
VG Name _vgb
LV Write Access read/write
LV Status available
LV # 1
# open 1
LV Size 1.46 GB
Current LE 375
Allocated LE 375
Allocation next free
Read ahead sectors 120
Block device 58:0
--- Logical volume ---
LV Name /dev/_vgb/vl_tmp
VG Name _vgb
LV Write Access read/write
LV Status available
LV # 2
# open 1
LV Size 500.00 MB
Current LE 125
Allocated LE 125
Allocation next free
Read ahead sectors 120
Block device 58:1
the only hitch I had configing was using lvrename, vgrename;
IIRC. I had to mv the /dev/_vgb special files myself,
causing a couple of fstab-umount-reboot-to-single
sessions to clean up errs. I used the 2nd cmd-form,
"vgrename vg02 my_volume_group", if that matters.
Perhaps a FAQ entry explaining what I may have mis-understood:
{lv,vg} rename dont change names of /dev/ special-files,
nor corresponding entries in /etc/fstab. You must manually edit your mount
points.
looking forward, I plan to fix the problem with 99% on /home
thanks for great software.
next prev parent reply other threads:[~2001-09-28 6:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-18 2:11 [linux-lvm] how to deactivate vg hosting root filesystem Joe Harvell
2001-07-18 6:08 ` Luca Berra
2001-09-28 6:15 ` Jim Cromie [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-10-01 7:43 [linux-lvm] success report 2.4.10 + 1.0.1-rc2 + diff Conny Brunnkvist / dimac.net
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=3BB41580.A3F6ECDB@divsol.com \
--to=jcromie@divsol.com \
--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.