From: tgs@iafrica.com
To: linux-lvm@sistina.com, ahiam@hotmail.com
Cc: tgs@iafrica.com
Subject: Re: [linux-lvm] Strtup probs !
Date: Tue, 17 Jul 2001 11:26:50 +0000 (GMT) [thread overview]
Message-ID: <0GGM00EWJ7ZIWI@smtp08.iafrica.com> (raw)
I had the same experience. The lvm-how to needs to be updated (changes in the
boot scripts for slackware). You going to have to change the rc.S file. I will
prepare a patch for this tonight and post on the mail list, as well email it to
you.
In the mean time I can explain the problem to you. Currently the rc.S in
slackware (I'm using version 8.0) does the following:
1. Mount to root partition as ro (read-only).
2. fsck all the filesystems in /etc/fstab. If one of them are a LVM partition
fsck can't talk to that then it can't fsck that filesystem and exits with an
error - you then go into admin mode. In order for fsck to be able to check
those filesystem you have to activate the volumes (i.e. vgchange -ay). To the
problem is that you can only run vgchange -ya if the root partition is mounted
rw. So you have a chicken-egg situation here.
My solution is:
1. mount the root partition as read-only.
2. run fsck -a /
3. remount the root partition as read-write
4. run vgscan and vgchange -ay
5. run fsck -A -a -R (will check all the fs but not the root, because it is
already been checked and mounted read-write)
I havnn't converted my root partition on a LVM yet. I don't intent to do that
not before I very sure that LVM 1.0 is released and stable.
I'm sure quota should work. I might be under correction but quota will work for
the filesystem, in your case /home is ext2 and should work.
Theo
> hi all,
>
> i need help with the following probs 'm facing.....
> my system is---> 512MB, 500Mhz, 3 scsi, Compaq server with 7.0 Slackware
> upgradded packages with latest from Slackware & kernel 2.4.6 ( with LVM as
> module)
> 1) could not start LVM with /etc/fstab entries ! ;-(
> i have created initrd.gz & have done exactly as stated in HOW-TO to
> start LVM at startup ( i'm doing it only on my /home ).
> if i dont put entries on my /etc/fstab ( for home & LVM) then it works
> ok, but sooner i put it there on boot there is an error of something swap
> disk which takes me to administrative mode !!!!.. my /etc/fstab enrty is
> /dev/VGmail/LVmail /home ext2 defaults 1 1
>
> 2) can quota be implimented with LVM for eg on my /home .. ??
>
> 3) how to have root partion on LVM.
> i tried to do that too like in the HOW-TO & did dd on an empty partion.
> but when i tried to convert root partion to LVM i got errors.. so can
> anyone tell me the actual steps pls !
>
> pls excuse me for my english
> thanxs in advance...
> arindam haldar
> _______________________________________________
> 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
---------------------------------------------
This message was sent using M-Web Airmail.
http://airmail.mweb.co.za/
next reply other threads:[~2001-07-17 11:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-17 11:26 tgs [this message]
2001-07-17 17:36 ` [linux-lvm] Strtup probs ! Johann
2001-07-19 12:43 ` Patrick Caulfield
-- strict thread matches above, loose matches on Subject: below --
2001-07-17 0:50 Arindam Haldar
2001-07-17 11:20 ` Heinz J. Mauelshagen
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=0GGM00EWJ7ZIWI@smtp08.iafrica.com \
--to=tgs@iafrica.com \
--cc=ahiam@hotmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox