[linux-lvm] LVM

[linux-lvm] LVM

[IT3 Stuart B. Tener, USNR-R]

List members:

	Hello to all, as I am somewhat new to the list. Perhaps one of you will recommend some basic reading to get me started, but I do have a few questions regarding LVM and my proposed deployment of it on my laptop.

	I have a Dell Laptop with two 32GB HDs, and a 1394 40GB HD. I am thinking to use LVM.

(a) I am running (2.4.8 or 2.4.9, I forget offhand) is LVM inclusive to the kernel in either of those releases?
(b) How does LVM juxtapose against a backdrop of a dual boot system, when W2K/PRO is one of the OSes installed.
(c) Same question, add FreeBSD (which I have not yet installed as of yet, but do plan to)?
(d) What about Solaris?
(e) Running W2K/PRO on a laptop does not allow for disk mirroring under windows, can LVM mirror my NTFS partition?

Can I run any filesystem with it? Will the new journaling filesystems work with it (I use ReiserFS at the moment, but I am not sure if it is the best for the money ... so to speak)?

	Is LVM still in a beta state, or is it trustable with my data to the extent you can note? I am not looking for an ironclad guarantee, but I am curious if most of the known bugs are gone.

	Any recommended reading (PDF format links if possible)?


Very Respectfully, 

Stuart Blake Tener, IT3, USNR-R, N3GWG 
Beverly Hills, California
VTU 1904G (Volunteer Training Unit) 
stuart@bh90210.net 
west coast: (310)-358-0202 P.O. Box 16043, Beverly Hills, CA 90209-2043 
east coast: (215)-338-6005 P.O. Box 45859, Philadelphia, PA 19149-5859 

Telecopier: (419)-715-6073 fax to email gateway via www.efax.com (it's free!) 

JOIN THE US NAVY RESERVE, SERVE YOUR COUNTRY, AND BENEFIT FROM IT ALL. 

Monday, September 10, 2001 4:29 AM

Re: [linux-lvm] LVM

[José Luis Domingo López]

On Monday, 10 September 2001, at 04:37:07 -0700,
IT3 Stuart B. Tener, USNR-R wrote:

> List members:
> 
> 	Hello to all, as I am somewhat new to the list. Perhaps one of you will recommend some basic reading to get me started, but I do have a few questions regarding LVM and my proposed deployment of it on my laptop.
> [...]
>
Your best starting point is the new LVM HOWTO at:
http://tech.sistina.com/lvm/doc/lvm_howto/index.html

Linux LVM is considered stable, since it passed version 1.0 (now
1.0.1-rc2). It has been stable for some time before. Current Linux kernels
include an outdated LVM version (2.4.9 still includes LVM 0.9.1-beta2,
dated back in January or so).

What LVM provides is a means or managing your disk space in Linux: so
there is no way to create a Linux LV to hold a Windows or Solaris
installation. AFAIK, W2K has some sort of volume management in some of
their versions, and I'm sure Solaris has something on its own.

Greetings.

--
Jos� Luis Domingo L�pez
Linux Registered User #189436     Debian GNU/Linux Potato (P166 64 MB RAM)
 
jdomingo EN internautas PUNTO org  => � Spam ? Atente a las consecuencias
jdomingo AT internautas DOT   org  => Spam at your own risk

RE: [linux-lvm] LVM

[IT3 Stuart B. Tener, USNR-R]

List members:

I downloaded the LVM How-To (30 AUG 2001, is this the latest version).

        Presuming I have 2.4.8 or 2.4.9 (don't remember off hand) installed, is there a patch file I can apply to bring it to a stable version? If so, where would I get this patch file for Mandrake 8.0 or kernel version 2.4.8/2.4.9?

I noticed that LVM can be installed into a partition, and thus does not need to control the non-Linux portion of the disk.

        In terms of Windows Volume Management, it does have it, but it has been specifically turned off in W2K/PRO for laptop users!


        Performing the upgrade:

Once I have patched the Mandrake 8.0 2.4.8 (I think) kernel to have the latest LVM updates, I am interested to take my NON-LVM disk and convert it to LVM. Let me explain a bit about my configuration so you can best guide me.

        I have two (exactly the same model) 32GB HDs in my Dell Laptop. I also have a 1394 40GB HD. Presume the 40GB HD (1394) and the 2nd 32GB HD are able to be used at will and have nothing important on them. The 1st 32GB HD, has a W2K and Linux partition on it. The Linux partition has a single (large 14GB) root partition (don't ask why, but it is this way due to some circumstance I needed for a client). I would like to make a bootable root partition (same size for the moment) on the 2nd disk, and then take the 2nd disk and put it into the 1st disk's position and test it by booting it up.
         I was planning on using the 1394 HD to make a backup copy of the 32GB HD ("dd if=/dev/hda of=/dev/sda bs=524288") before starting, and using the 2nd 32GB HD as a staging drive to move all the files and such, and test the boot up out. If it worked, I would then copy it back to the other 32GB HD.

        What recommendations do you offer as a migration plan for doing this?



Very Respectfully,

Stuart Blake Tener, IT3, USNR-R, N3GWG
Beverly Hills, California
VTU 1904G (Volunteer Training Unit)
stuart@bh90210.net
west coast: (310)-358-0202 P.O. Box 16043, Beverly Hills, CA 90209-2043
east coast: (215)-338-6005 P.O. Box 45859, Philadelphia, PA 19149-5859

Telecopier: (419)-715-6073 fax to email gateway via www.efax.com (it's free!)

JOIN THE US NAVY RESERVE, SERVE YOUR COUNTRY, AND BENEFIT FROM IT ALL.

Monday, September 10, 2001 5:14 AM

-----Original Message-----
From: linux-lvm-admin@sistina.com [mailto:linux-lvm-admin@sistina.com]On Behalf Of José Luis Domingo López
Sent: Monday, September 10, 2001 7:06 AM
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] LVM

On Monday, 10 September 2001, at 04:37:07 -0700,
IT3 Stuart B. Tener, USNR-R wrote:

> List members:
>
>       Hello to all, as I am somewhat new to the list. Perhaps one of you will recommend some basic reading to get me started, but I do have a few questions regarding LVM and my proposed deployment of it on my laptop.
> [...]
>
Your best starting point is the new LVM HOWTO at:
http://tech.sistina.com/lvm/doc/lvm_howto/index.html

Linux LVM is considered stable, since it passed version 1.0 (now
1.0.1-rc2). It has been stable for some time before. Current Linux kernels
include an outdated LVM version (2.4.9 still includes LVM 0.9.1-beta2,
dated back in January or so).

What LVM provides is a means or managing your disk space in Linux: so
there is no way to create a Linux LV to hold a Windows or Solaris
installation. AFAIK, W2K has some sort of volume management in some of
their versions, and I'm sure Solaris has something on its own.

Greetings.

--
José Luis Domingo López
Linux Registered User #189436     Debian GNU/Linux Potato (P166 64 MB RAM)

jdomingo EN internautas PUNTO org  => ¿ Spam ? Atente a las consecuencias
jdomingo AT internautas DOT   org  => Spam at your own risk


_______________________________________________
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

Re: [linux-lvm] LVM

[José Luis Domingo López]

On Monday, 10 September 2001, at 06:03:03 -0700,
IT3 Stuart B. Tener, USNR-R wrote:

> List members:
> 
> I downloaded the LVM How-To (30 AUG 2001, is this the latest version).
> [...]
>
Read the HOWTO you have just downloaded. Download LVM sources from
Sistina's FTP site, and read the documentation on the tarball. Most (if
not all) of your doubts will suddenly disappear :)

--
Jos� Luis Domingo L�pez
Linux Registered User #189436     Debian GNU/Linux Potato (P166 64 MB RAM)
 
jdomingo EN internautas PUNTO org  => � Spam ? Atente a las consecuencias
jdomingo AT internautas DOT   org  => Spam at your own risk

RE: [linux-lvm] LVM

[IT3 Stuart B. Tener, USNR-R]

Dear Sir:

	I HAVE READ (and DID READ) PRIOR TO ASKING MY QUESTIONS, (when I noted I downloaded it, I figured everyone would realize I had read it as well!).

All those whom are telling me to read the How-To, PLEASE, GO READ IT YOURSELF! SPECIFICALLY: section 7.2, paragraph 2. There is no such directory located on the Sistina FTP server. Where is this patch?


Very Respectfully, 

Stuart Blake Tener, IT3, USNR-R, N3GWG 
Beverly Hills, California
VTU 1904G (Volunteer Training Unit) 
stuart@bh90210.net 
west coast: (310)-358-0202 P.O. Box 16043, Beverly Hills, CA 90209-2043 
east coast: (215)-338-6005 P.O. Box 45859, Philadelphia, PA 19149-5859 

Telecopier: (419)-715-6073 fax to email gateway via www.efax.com (it's free!) 

JOIN THE US NAVY RESERVE, SERVE YOUR COUNTRY, AND BENEFIT FROM IT ALL. 

Monday, September 10, 2001 7:26 PM

-----Original Message-----
From: linux-lvm-admin@sistina.com [mailto:linux-lvm-admin@sistina.com]On Behalf Of José Luis Domingo López
Sent: Monday, September 10, 2001 9:48 AM
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] LVM

On Monday, 10 September 2001, at 06:03:03 -0700,
IT3 Stuart B. Tener, USNR-R wrote:

> List members:
>
> I downloaded the LVM How-To (30 AUG 2001, is this the latest version).
> [...]
>
Read the HOWTO you have just downloaded. Download LVM sources from
Sistina's FTP site, and read the documentation on the tarball. Most (if
not all) of your doubts will suddenly disappear :)

--
José Luis Domingo López
Linux Registered User #189436     Debian GNU/Linux Potato (P166 64 MB RAM)

jdomingo EN internautas PUNTO org  => ¿ Spam ? Atente a las consecuencias
jdomingo AT internautas DOT   org  => Spam at your own risk


_______________________________________________
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

Re: [linux-lvm] LVM

[José Luis Domingo López]

On Monday, 10 September 2001, at 19:35:13 -0700,
IT3 Stuart B. Tener, USNR-R wrote:

> Dear Sir:
> 
> 	I HAVE READ (and DID READ) PRIOR TO ASKING MY QUESTIONS, (when I noted I downloaded it, I figured everyone would realize I had read it as well!).
> 
> All those whom are telling me to read the How-To, PLEASE, GO READ IT YOURSELF! SPECIFICALLY: section 7.2, paragraph 2. There is no such directory located on the Sistina FTP server. Where is this patch?
> 
Your are right, links on the HOWTO don't point to the right location. To
get current sources of LVM download:
ftp://ftp.sistina.com/pub/LVM/1.0/lvm_1.0.1-rc2.tar.gz

It works for recent kernels (even 2.4.9) and the documentation included
explains how to create a patch specifically suited for your current Linux
source tree.

--
Jos� Luis Domingo L�pez
Linux Registered User #189436     Debian GNU/Linux Potato (P166 64 MB RAM)
 
jdomingo EN internautas PUNTO org  => � Spam ? Atente a las consecuencias
jdomingo AT internautas DOT   org  => Spam at your own risk

RE: [linux-lvm] LVM

[IT3 Stuart B. Tener, USNR-R]

Mr. López:

	Yes, and thank you for the link! I will grab the most current source, and attempt to make it work. I am using version 2.4.8-12mdk (mandrake) of the kernel. Mandrake 8.1 is going to be coming soon, and when it does come forth, I plan to upgrade. Having LVM running will make the upgrade much less painful!

	As we speak, I am downloading this file. But, can you tell me, are there any major caveats to using this version in the link below?


Very Respectfully, 

Stuart Blake Tener, IT3, USNR-R, N3GWG 
Beverly Hills, California
VTU 1904G (Volunteer Training Unit) 
stuart@bh90210.net 
west coast: (310)-358-0202 P.O. Box 16043, Beverly Hills, CA 90209-2043 
east coast: (215)-338-6005 P.O. Box 45859, Philadelphia, PA 19149-5859 

Telecopier: (419)-715-6073 fax to email gateway via www.efax.com (it's free!) 

JOIN THE US NAVY RESERVE, SERVE YOUR COUNTRY, AND BENEFIT FROM IT ALL. 

Tuesday, September 11, 2001 4:00 AM

-----Original Message-----
From: linux-lvm-admin@sistina.com [mailto:linux-lvm-admin@sistina.com]On Behalf Of José Luis Domingo López
Sent: Tuesday, September 11, 2001 5:20 AM
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] LVM

On Monday, 10 September 2001, at 19:35:13 -0700,
IT3 Stuart B. Tener, USNR-R wrote:

> Dear Sir:
>
>       I HAVE READ (and DID READ) PRIOR TO ASKING MY QUESTIONS, (when I noted I downloaded it, I figured everyone would realize I had read it as well!).
>
> All those whom are telling me to read the How-To, PLEASE, GO READ IT YOURSELF! SPECIFICALLY: section 7.2, paragraph 2. There is no such directory located on the Sistina FTP server. Where is this patch?
>
Your are right, links on the HOWTO don't point to the right location. To
get current sources of LVM download:
ftp://ftp.sistina.com/pub/LVM/1.0/lvm_1.0.1-rc2.tar.gz

It works for recent kernels (even 2.4.9) and the documentation included
explains how to create a patch specifically suited for your current Linux
source tree.

--
José Luis Domingo López
Linux Registered User #189436     Debian GNU/Linux Potato (P166 64 MB RAM)

jdomingo EN internautas PUNTO org  => ¿ Spam ? Atente a las consecuencias
jdomingo AT internautas DOT   org  => Spam at your own risk


_______________________________________________
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

Re: [linux-lvm] LVM

[svetljo]

Hi

> I am using version 2.4.8-12mdk (mandrake) of the kernel. Mandrake 8.1 is going to be coming soon, and when it does come forth, I plan to upgrade. Having LVM running will make the upgrade much less painful!
>
I think you can have troubles with upgrading to MDK-8.1 if you use 
 lvm-1.0.1 or anything after lvm-0.91beta8
as far i know they are still using  the integrated in the kernel 
lvm-0.91beta2 and they don't wont to upgrade to lvm-1.0 or 1.0.1  so 
when you boot from the CD the kernel will not  see the exiting logical 
volumes
but i think i have read somewhere that lvm-1.0.1 supports both the old 
and new phisical volumes

my advice befor copying anything to the LV ( i mean all the partitions 
you mean to upgrade : / , /usr  ...
go through all the documentation and man pages and try to find out 
whether it's posible to create VG and LV's in the old format ( pre 
lvm-0.9.1beta8) but i think it's not possible

or wait until MDK-8.1 come and then install lvm-1.0.1 

>
>	As we speak, I am downloading this file. But, can you tell me, are there any major caveats to using this version in the link below?
>
>
>Very Respectfully, 
>
>Stuart Blake Tener, IT3, USNR-R, N3GWG 
>Beverly Hills, California
>VTU 1904G (Volunteer Training Unit) 
>stuart@bh90210.net 
>west coast: (310)-358-0202 P.O. Box 16043, Beverly Hills, CA 90209-2043 
>east coast: (215)-338-6005 P.O. Box 45859, Philadelphia, PA 19149-5859 
>
>Telecopier: (419)-715-6073 fax to email gateway via www.efax.com (it's free!) 
>
>JOIN THE US NAVY RESERVE, SERVE YOUR COUNTRY, AND BENEFIT FROM IT ALL. 
>
>Tuesday, September 11, 2001 4:00 AM
>
>-----Original Message-----
>From: linux-lvm-admin@sistina.com [mailto:linux-lvm-admin@sistina.com]On Behalf Of Jos� Luis Domingo L�pez
>Sent: Tuesday, September 11, 2001 5:20 AM
>To: linux-lvm@sistina.com
>Subject: Re: [linux-lvm] LVM
>
>On Monday, 10 September 2001, at 19:35:13 -0700,
>IT3 Stuart B. Tener, USNR-R wrote:
>
>>Dear Sir:
>>
>>      I HAVE READ (and DID READ) PRIOR TO ASKING MY QUESTIONS, (when I noted I downloaded it, I figured everyone would realize I had read it as well!).
>>
>>All those whom are telling me to read the How-To, PLEASE, GO READ IT YOURSELF! SPECIFICALLY: section 7.2, paragraph 2. There is no such directory located on the Sistina FTP server. Where is this patch?
>>
>Your are right, links on the HOWTO don't point to the right location. To
>get current sources of LVM download:
>ftp://ftp.sistina.com/pub/LVM/1.0/lvm_1.0.1-rc2.tar.gz
>
>It works for recent kernels (even 2.4.9) and the documentation included
>explains how to create a patch specifically suited for your current Linux
>source tree.
>
>--
>Jos� Luis Domingo L�pez
>Linux Registered User #189436     Debian GNU/Linux Potato (P166 64 MB RAM)
>
>jdomingo EN internautas PUNTO org  => � Spam ? Atente a las consecuencias
>jdomingo AT internautas DOT   org  => Spam at your own risk
>
>
>_______________________________________________
>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
>

Re: [linux-lvm] LVM

[Heinz J . Mauelshagen]

Well,

LVM 1.0.1-rc2 supports the old ondisk format and you can get it from
ftp.sistina.com.

Regards,
Heinz    -- The LVM Guy --


On Tue, Sep 11, 2001 at 02:04:21PM +0200, svetljo wrote:
> Hi
> 
> > I am using version 2.4.8-12mdk (mandrake) of the kernel. Mandrake 8.1 is going to be coming soon, and when it does come forth, I plan to upgrade. Having LVM running will make the upgrade much less painful!
> >
> I think you can have troubles with upgrading to MDK-8.1 if you use 
>  lvm-1.0.1 or anything after lvm-0.91beta8
> as far i know they are still using  the integrated in the kernel 
> lvm-0.91beta2 and they don't wont to upgrade to lvm-1.0 or 1.0.1  so 
> when you boot from the CD the kernel will not  see the exiting logical 
> volumes
> but i think i have read somewhere that lvm-1.0.1 supports both the old 
> and new phisical volumes
> 
> my advice befor copying anything to the LV ( i mean all the partitions 
> you mean to upgrade : / , /usr  ...
> go through all the documentation and man pages and try to find out 
> whether it's posible to create VG and LV's in the old format ( pre 
> lvm-0.9.1beta8) but i think it's not possible
> 
> or wait until MDK-8.1 come and then install lvm-1.0.1 
> 
> >
> >	As we speak, I am downloading this file. But, can you tell me, are there any major caveats to using this version in the link below?
> >
> >
> >Very Respectfully, 
> >
> >Stuart Blake Tener, IT3, USNR-R, N3GWG 
> >Beverly Hills, California
> >VTU 1904G (Volunteer Training Unit) 
> >stuart@bh90210.net 
> >west coast: (310)-358-0202 P.O. Box 16043, Beverly Hills, CA 90209-2043 
> >east coast: (215)-338-6005 P.O. Box 45859, Philadelphia, PA 19149-5859 
> >
> >Telecopier: (419)-715-6073 fax to email gateway via www.efax.com (it's free!) 
> >
> >JOIN THE US NAVY RESERVE, SERVE YOUR COUNTRY, AND BENEFIT FROM IT ALL. 
> >
> >Tuesday, September 11, 2001 4:00 AM
> >
> >-----Original Message-----
> >From: linux-lvm-admin@sistina.com [mailto:linux-lvm-admin@sistina.com]On Behalf Of José Luis Domingo López
> >Sent: Tuesday, September 11, 2001 5:20 AM
> >To: linux-lvm@sistina.com
> >Subject: Re: [linux-lvm] LVM
> >
> >On Monday, 10 September 2001, at 19:35:13 -0700,
> >IT3 Stuart B. Tener, USNR-R wrote:
> >
> >>Dear Sir:
> >>
> >>      I HAVE READ (and DID READ) PRIOR TO ASKING MY QUESTIONS, (when I noted I downloaded it, I figured everyone would realize I had read it as well!).
> >>
> >>All those whom are telling me to read the How-To, PLEASE, GO READ IT YOURSELF! SPECIFICALLY: section 7.2, paragraph 2. There is no such directory located on the Sistina FTP server. Where is this patch?
> >>
> >Your are right, links on the HOWTO don't point to the right location. To
> >get current sources of LVM download:
> >ftp://ftp.sistina.com/pub/LVM/1.0/lvm_1.0.1-rc2.tar.gz
> >
> >It works for recent kernels (even 2.4.9) and the documentation included
> >explains how to create a patch specifically suited for your current Linux
> >source tree.
> >
> >--
> >José Luis Domingo López
> >Linux Registered User #189436     Debian GNU/Linux Potato (P166 64 MB RAM)
> >
> >jdomingo EN internautas PUNTO org  => ¿ Spam ? Atente a las consecuencias
> >jdomingo AT internautas DOT   org  => Spam at your own risk
> >
> >
> >_______________________________________________
> >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
> >
> 
> 
> 
> _______________________________________________
> 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

*** Software bugs are stupid.
    Nevertheless it needs not so stupid people to solve them ***

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Heinz Mauelshagen                                 Sistina Software Inc.
Senior Consultant/Developer                       Am Sonnenhang 11
                                                  56242 Marienrachdorf
                                                  Germany
Mauelshagen@Sistina.com                           +49 2626 141200
                                                       FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Re: [linux-lvm] LVM

[svetljo]

does this mean that when you are creating PV's VG's LV's could be created
 with some option in the old format
or we have to use pvversion from lvm-1.0 to convert the PV's to the old 
version
is it neccesary to convert the VG's and LV's and are there any tools
doesn't lvm-1.0.1rc2 defaults to the new version when you create PV's 
VG's LV's

the question is
can we access VG's and LV's created with lvm-1.0.1rc2 with vanila kernel 
with lvm-0.9.1beta2
Heinz J . Mauelshagen wrote:

>Well,
>
>LVM 1.0.1-rc2 supports the old ondisk format and you can get it from
>ftp.sistina.com.
>
>Regards,
>Heinz    -- The LVM Guy --
>
>
>On Tue, Sep 11, 2001 at 02:04:21PM +0200, svetljo wrote:
>
>>Hi
>>
>>>I am using version 2.4.8-12mdk (mandrake) of the kernel. Mandrake 8.1 is going to be coming soon, and when it does come forth, I plan to upgrade. Having LVM running will make the upgrade much less painful!
>>>
>>I think you can have troubles with upgrading to MDK-8.1 if you use 
>> lvm-1.0.1 or anything after lvm-0.91beta8
>>as far i know they are still using  the integrated in the kernel 
>>lvm-0.91beta2 and they don't wont to upgrade to lvm-1.0 or 1.0.1  so 
>>when you boot from the CD the kernel will not  see the exiting logical 
>>volumes
>>but i think i have read somewhere that lvm-1.0.1 supports both the old 
>>and new phisical volumes
>>
>>my advice befor copying anything to the LV ( i mean all the partitions 
>>you mean to upgrade : / , /usr  ...
>>go through all the documentation and man pages and try to find out 
>>whether it's posible to create VG and LV's in the old format ( pre 
>>lvm-0.9.1beta8) but i think it's not possible
>>
>>or wait until MDK-8.1 come and then install lvm-1.0.1 
>>
>>>	As we speak, I am downloading this file. But, can you tell me, are there any major caveats to using this version in the link below?
>>>
>>>
>>>Very Respectfully, 
>>>
>>>Stuart Blake Tener, IT3, USNR-R, N3GWG 
>>>Beverly Hills, California
>>>VTU 1904G (Volunteer Training Unit) 
>>>stuart@bh90210.net 
>>>west coast: (310)-358-0202 P.O. Box 16043, Beverly Hills, CA 90209-2043 
>>>east coast: (215)-338-6005 P.O. Box 45859, Philadelphia, PA 19149-5859 
>>>
>>>Telecopier: (419)-715-6073 fax to email gateway via www.efax.com (it's free!) 
>>>
>>>JOIN THE US NAVY RESERVE, SERVE YOUR COUNTRY, AND BENEFIT FROM IT ALL. 
>>>
>>>Tuesday, September 11, 2001 4:00 AM
>>>
>>>-----Original Message-----
>>>From: linux-lvm-admin@sistina.com [mailto:linux-lvm-admin@sistina.com]On Behalf Of Jos� Luis Domingo L�pez
>>>Sent: Tuesday, September 11, 2001 5:20 AM
>>>To: linux-lvm@sistina.com
>>>Subject: Re: [linux-lvm] LVM
>>>
>>>On Monday, 10 September 2001, at 19:35:13 -0700,
>>>IT3 Stuart B. Tener, USNR-R wrote:
>>>
>>>>Dear Sir:
>>>>
>>>>     I HAVE READ (and DID READ) PRIOR TO ASKING MY QUESTIONS, (when I noted I downloaded it, I figured everyone would realize I had read it as well!).
>>>>
>>>>All those whom are telling me to read the How-To, PLEASE, GO READ IT YOURSELF! SPECIFICALLY: section 7.2, paragraph 2. There is no such directory located on the Sistina FTP server. Where is this patch?
>>>>
>>>Your are right, links on the HOWTO don't point to the right location. To
>>>get current sources of LVM download:
>>>ftp://ftp.sistina.com/pub/LVM/1.0/lvm_1.0.1-rc2.tar.gz
>>>
>>>It works for recent kernels (even 2.4.9) and the documentation included
>>>explains how to create a patch specifically suited for your current Linux
>>>source tree.
>>>
>>>--
>>>Jos� Luis Domingo L�pez
>>>Linux Registered User #189436     Debian GNU/Linux Potato (P166 64 MB RAM)
>>>
>>>jdomingo EN internautas PUNTO org  => � Spam ? Atente a las consecuencias
>>>jdomingo AT internautas DOT   org  => Spam at your own risk
>>>
>>>
>>>_______________________________________________
>>>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
>>>
>>
>>
>>_______________________________________________
>>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
>>
>
>*** Software bugs are stupid.
>    Nevertheless it needs not so stupid people to solve them ***
>
>=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
>
>Heinz Mauelshagen                                 Sistina Software Inc.
>Senior Consultant/Developer                       Am Sonnenhang 11
>                                                  56242 Marienrachdorf
>                                                  Germany
>Mauelshagen@Sistina.com                           +49 2626 141200
>                                                       FAX 924446
>=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
>
>_______________________________________________
>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
>

RE: [linux-lvm] LVM

[IT3 Stuart B. Tener, USNR-R]

LVM List members:

	I have been doing some playing around and am not getting very far! Perhaps you can answer some questions and guide me.

I have 2 32GB HDs, which I can have both in use on my laptop simultaneously. The 2nd HD I can erase to my hearts content. It's a staging drive.

	My current configuration is:

	/dev/hda1	windows 2000 pro
	/dev/hda2	/	(Linux mandrake 8.0)

	I do not have a swap partition at the moment (I have 512MB of ram, and I use a swap file if I need too), and have everything installed into the root (I know the drawbacks of this, but it made for simplicity at the time). I also use ReiserFS, and want to implement LVM.

	The "How To" speaks of an example inclusive of a /boot partition and a swap partition. I ignored the swap partition, but was curious about the /boot partition in the how-to.

a) Do I need to have a separate /boot partition, or can I create an LVM implementation (for the moment) with everything in the root (/)?
b) The example seems to show the /boot being outside the LVM area, is that correct or does the how-to mean to show the /boot as being within the domain of the LVM controlled area?
c) How will using ReiserFS on my root partition and LVM over the root affect what I need to do for an initrd and kernel compilation options?

Once the LVM implementation is completed with everything in the / partition, and ReiserFS on the root, and it boots up, then I plan to break apart the / into separate filesystems within the LVM environment. At that point, recommendations of what filesystems to create will be helpful.


Very Respectfully, 

Stuart Blake Tener, IT3, USNR-R, N3GWG 
Beverly Hills, California
VTU 1904G (Volunteer Training Unit) 
stuart@bh90210.net 
west coast: (310)-358-0202 P.O. Box 16043, Beverly Hills, CA 90209-2043 
east coast: (215)-338-6005 P.O. Box 45859, Philadelphia, PA 19149-5859 

Telecopier: (419)-715-6073 fax to email gateway via www.efax.com (it's free!) 

JOIN THE US NAVY RESERVE, SERVE YOUR COUNTRY, AND BENEFIT FROM IT ALL. 

Wednesday, September 12, 2001 2:01 AM
 

Re: [linux-lvm] LVM

[svetljo]

Hi
you need a normal partition vor /boot not on LV and it would be good to 
have also a normal partition as swap,
but in case you don't use swap you don't need to,
the thing is that the swap is much faster when it is on partition not file
you can try to do it without formating the second disk
you can shrink ReiserFS, then with diskdrake shrink the partition
 and make a new one for boot and for the VG , make an LV on the VG , 
create filesystems on the LV and /boot, mount the LV /mnt/new-root , 
mkdir /mnt/new-root/boot and mount here the /boot partition
trasnfer your installation to /mnt/new-root:
cd /
 find . -xdev | cpio -pm /mnt/new-root

edit /mnt/new-root/etc/fstab to match the LV as / and ad an entry for /boot

reboot
and pass to lilo root=/dev/[your VG]/[your / LV]
it should be working

edit lilo.conf and reinstall lilo or grub ( i'm not shure that lilo can 
boot from the end of 32Gb drive)

reboot once more if everything is OK
you can make a PV from your old / and ad it to the VG
that should be it

about the FS's

smth important ( may be) as far i know only Reiserfs could be shrinked ,
you can only grow XFS and JFS you can not make them smaller
 
i really like XFS,and not that much the others
i had some crashes and with reiserfs i have some file entries which are 
reported to exist ,but they can not be stated when i try to delete them 
or to see them
i have not much expiriance with JFS , but i'm hearing that it was not 
that stable as of 1.0.3
and with XFS i found all lost files in " lost and find " and it was 
pretty easy to bring them back
i mention only the journal ones becouse you are speaking about 32Gb




 


IT3 Stuart B. Tener, USNR-R wrote:

>LVM List members:
>
>	I have been doing some playing around and am not getting very far! Perhaps you can answer some questions and guide me.
>
>I have 2 32GB HDs, which I can have both in use on my laptop simultaneously. The 2nd HD I can erase to my hearts content. It's a staging drive.
>
>	My current configuration is:
>
>	/dev/hda1	windows 2000 pro
>	/dev/hda2	/	(Linux mandrake 8.0)
>
>	I do not have a swap partition at the moment (I have 512MB of ram, and I use a swap file if I need too), and have everything installed into the root (I know the drawbacks of this, but it made for simplicity at the time). I also use ReiserFS, and want to implement LVM.
>
>	The "How To" speaks of an example inclusive of a /boot partition and a swap partition. I ignored the swap partition, but was curious about the /boot partition in the how-to.
>
>a) Do I need to have a separate /boot partition, or can I create an LVM implementation (for the moment) with everything in the root (/)?
>b) The example seems to show the /boot being outside the LVM area, is that correct or does the how-to mean to show the /boot as being within the domain of the LVM controlled area?
>c) How will using ReiserFS on my root partition and LVM over the root affect what I need to do for an initrd and kernel compilation options?
>
>Once the LVM implementation is completed with everything in the / partition, and ReiserFS on the root, and it boots up, then I plan to break apart the / into separate filesystems within the LVM environment. At that point, recommendations of what filesystems to create will be helpful.
>
>
>Very Respectfully, 
>
>Stuart Blake Tener, IT3, USNR-R, N3GWG 
>Beverly Hills, California
>VTU 1904G (Volunteer Training Unit) 
>stuart@bh90210.net 
>west coast: (310)-358-0202 P.O. Box 16043, Beverly Hills, CA 90209-2043 
>east coast: (215)-338-6005 P.O. Box 45859, Philadelphia, PA 19149-5859 
>
>Telecopier: (419)-715-6073 fax to email gateway via www.efax.com (it's free!) 
>
>JOIN THE US NAVY RESERVE, SERVE YOUR COUNTRY, AND BENEFIT FROM IT ALL. 
>
>Wednesday, September 12, 2001 2:01 AM
> 
>

RE: [linux-lvm] LVM

[IT3 Stuart B. Tener, USNR-R]

Svetjo:

	/dev/hda1	w2k/pro
	/dev/hda2	/boot
	/dev/hda3	/

	Something like the above?

	Okay, I did that, and now I get "LI" when I booted up! What does "LI" in lilo mean? What part of my boot up sequence is broken?

	Someone told me it meant my second stage boot loader was failing. What does that mean? What are the stages of booting? Can anyone hook me up here?

	As far as I know, I have ReiserFS compiled into the kernel along with LVM support in the kernel.

	I must admit ReiserFS has worked quite well for me, and is very bug-free. I am using the version that comes with the 2.4.8-12mdk (mandrake) kernel, so perhaps u tried an older version.


Very Respectfully, 

Stuart Blake Tener, IT3, USNR-R, N3GWG 
Beverly Hills, California
VTU 1904G (Volunteer Training Unit) 
stuart@bh90210.net 
west coast: (310)-358-0202 P.O. Box 16043, Beverly Hills, CA 90209-2043 
east coast: (215)-338-6005 P.O. Box 45859, Philadelphia, PA 19149-5859 

Telecopier: (419)-715-6073 fax to email gateway via www.efax.com (it's free!) 

JOIN THE US NAVY RESERVE, SERVE YOUR COUNTRY, AND BENEFIT FROM IT ALL. 

Wednesday, September 12, 2001 3:43 AM

-----Original Message-----
From: linux-lvm-admin@sistina.com [mailto:linux-lvm-admin@sistina.com]On Behalf Of svetljo
Sent: Wednesday, September 12, 2001 2:59 AM
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] LVM

Hi
you need a normal partition vor /boot not on LV and it would be good to
have also a normal partition as swap,
but in case you don't use swap you don't need to,
the thing is that the swap is much faster when it is on partition not file
you can try to do it without formating the second disk
you can shrink ReiserFS, then with diskdrake shrink the partition
 and make a new one for boot and for the VG , make an LV on the VG ,
create filesystems on the LV and /boot, mount the LV /mnt/new-root ,
mkdir /mnt/new-root/boot and mount here the /boot partition
trasnfer your installation to /mnt/new-root:
cd /
 find . -xdev | cpio -pm /mnt/new-root

edit /mnt/new-root/etc/fstab to match the LV as / and ad an entry for /boot

reboot
and pass to lilo root=/dev/[your VG]/[your / LV]
it should be working

edit lilo.conf and reinstall lilo or grub ( i'm not shure that lilo can
boot from the end of 32Gb drive)

reboot once more if everything is OK
you can make a PV from your old / and ad it to the VG
that should be it

about the FS's

smth important ( may be) as far i know only Reiserfs could be shrinked ,
you can only grow XFS and JFS you can not make them smaller

i really like XFS,and not that much the others
i had some crashes and with reiserfs i have some file entries which are
reported to exist ,but they can not be stated when i try to delete them
or to see them
i have not much expiriance with JFS , but i'm hearing that it was not
that stable as of 1.0.3
and with XFS i found all lost files in " lost and find " and it was
pretty easy to bring them back
i mention only the journal ones becouse you are speaking about 32Gb







IT3 Stuart B. Tener, USNR-R wrote:

>LVM List members:
>
>       I have been doing some playing around and am not getting very far! Perhaps you can answer some questions and guide me.
>
>I have 2 32GB HDs, which I can have both in use on my laptop simultaneously. The 2nd HD I can erase to my hearts content. It's a staging drive.
>
>       My current configuration is:
>
>       /dev/hda1       windows 2000 pro
>       /dev/hda2       /       (Linux mandrake 8.0)
>
>       I do not have a swap partition at the moment (I have 512MB of ram, and I use a swap file if I need too), and have everything installed into the root (I know the drawbacks of this, but it made for simplicity at the time). I also use ReiserFS, and want to implement LVM.
>
>       The "How To" speaks of an example inclusive of a /boot partition and a swap partition. I ignored the swap partition, but was curious about the /boot partition in the how-to.
>
>a) Do I need to have a separate /boot partition, or can I create an LVM implementation (for the moment) with everything in the root (/)?
>b) The example seems to show the /boot being outside the LVM area, is that correct or does the how-to mean to show the /boot as being within the domain of the LVM controlled area?
>c) How will using ReiserFS on my root partition and LVM over the root affect what I need to do for an initrd and kernel compilation options?
>
>Once the LVM implementation is completed with everything in the / partition, and ReiserFS on the root, and it boots up, then I plan to break apart the / into separate filesystems within the LVM environment. At that point, recommendations of what filesystems to create will be helpful.
>
>
>Very Respectfully,
>
>Stuart Blake Tener, IT3, USNR-R, N3GWG
>Beverly Hills, California
>VTU 1904G (Volunteer Training Unit)
>stuart@bh90210.net
>west coast: (310)-358-0202 P.O. Box 16043, Beverly Hills, CA 90209-2043
>east coast: (215)-338-6005 P.O. Box 45859, Philadelphia, PA 19149-5859
>
>Telecopier: (419)-715-6073 fax to email gateway via www.efax.com (it's free!)
>
>JOIN THE US NAVY RESERVE, SERVE YOUR COUNTRY, AND BENEFIT FROM IT ALL.
>
>Wednesday, September 12, 2001 2:01 AM
>
>



_______________________________________________
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

Re: [linux-lvm] LVM

[svetljo]

i should tell you about that
that was the problem that i had when i tried with /boot behind the first 
1024cyl of the first disk
some people tells that the new lilo can handle this (it comes with MDK-8)
some people tells that probably a BIOS update should solve the problem
it didn't work for me

you can try to update lilo to the latest beta version and to update the BIOS
but with GRUB it works
the problem is that LILO can not read from /boot
my partitions
/dev/hda1 470Mb win-boot
extended
/dev/hda5   32Mb /boot
......

can you boot with a floppy and install grub?  it must work
IT3 Stuart B. Tener, USNR-R wrote:

>Svetjo:
>
>	/dev/hda1	w2k/pro
>	/dev/hda2	/boot
>	/dev/hda3	/
>
>	Something like the above?
>
>	Okay, I did that, and now I get "LI" when I booted up! What does "LI" in lilo mean? What part of my boot up sequence is broken?
>
>	Someone told me it meant my second stage boot loader was failing. What does that mean? What are the stages of booting? Can anyone hook me up here?
>
>	As far as I know, I have ReiserFS compiled into the kernel along with LVM support in the kernel.
>
>	I must admit ReiserFS has worked quite well for me, and is very bug-free. I am using the version that comes with the 2.4.8-12mdk (mandrake) kernel, so perhaps u tried an older version.
>
>
>Very Respectfully, 
>
>Stuart Blake Tener, IT3, USNR-R, N3GWG 
>Beverly Hills, California
>VTU 1904G (Volunteer Training Unit) 
>stuart@bh90210.net 
>west coast: (310)-358-0202 P.O. Box 16043, Beverly Hills, CA 90209-2043 
>east coast: (215)-338-6005 P.O. Box 45859, Philadelphia, PA 19149-5859 
>
>Telecopier: (419)-715-6073 fax to email gateway via www.efax.com (it's free!) 
>
>JOIN THE US NAVY RESERVE, SERVE YOUR COUNTRY, AND BENEFIT FROM IT ALL. 
>
>Wednesday, September 12, 2001 3:43 AM
>
>-----Original Message-----
>From: linux-lvm-admin@sistina.com [mailto:linux-lvm-admin@sistina.com]On Behalf Of svetljo
>Sent: Wednesday, September 12, 2001 2:59 AM
>To: linux-lvm@sistina.com
>Subject: Re: [linux-lvm] LVM
>
>Hi
>you need a normal partition vor /boot not on LV and it would be good to
>have also a normal partition as swap,
>but in case you don't use swap you don't need to,
>the thing is that the swap is much faster when it is on partition not file
>you can try to do it without formating the second disk
>you can shrink ReiserFS, then with diskdrake shrink the partition
> and make a new one for boot and for the VG , make an LV on the VG ,
>create filesystems on the LV and /boot, mount the LV /mnt/new-root ,
>mkdir /mnt/new-root/boot and mount here the /boot partition
>trasnfer your installation to /mnt/new-root:
>cd /
> find . -xdev | cpio -pm /mnt/new-root
>
>edit /mnt/new-root/etc/fstab to match the LV as / and ad an entry for /boot
>
>reboot
>and pass to lilo root=/dev/[your VG]/[your / LV]
>it should be working
>
>edit lilo.conf and reinstall lilo or grub ( i'm not shure that lilo can
>boot from the end of 32Gb drive)
>
>reboot once more if everything is OK
>you can make a PV from your old / and ad it to the VG
>that should be it
>
>about the FS's
>
>smth important ( may be) as far i know only Reiserfs could be shrinked ,
>you can only grow XFS and JFS you can not make them smaller
>
>i really like XFS,and not that much the others
>i had some crashes and with reiserfs i have some file entries which are
>reported to exist ,but they can not be stated when i try to delete them
>or to see them
>i have not much expiriance with JFS , but i'm hearing that it was not
>that stable as of 1.0.3
>and with XFS i found all lost files in " lost and find " and it was
>pretty easy to bring them back
>i mention only the journal ones becouse you are speaking about 32Gb
>
>
>
>
>
>
>
>IT3 Stuart B. Tener, USNR-R wrote:
>
>>LVM List members:
>>
>>      I have been doing some playing around and am not getting very far! Perhaps you can answer some questions and guide me.
>>
>>I have 2 32GB HDs, which I can have both in use on my laptop simultaneously. The 2nd HD I can erase to my hearts content. It's a staging drive.
>>
>>      My current configuration is:
>>
>>      /dev/hda1       windows 2000 pro
>>      /dev/hda2       /       (Linux mandrake 8.0)
>>
>>      I do not have a swap partition at the moment (I have 512MB of ram, and I use a swap file if I need too), and have everything installed into the root (I know the drawbacks of this, but it made for simplicity at the time). I also use ReiserFS, and want to implement LVM.
>>
>>      The "How To" speaks of an example inclusive of a /boot partition and a swap partition. I ignored the swap partition, but was curious about the /boot partition in the how-to.
>>
>>a) Do I need to have a separate /boot partition, or can I create an LVM implementation (for the moment) with everything in the root (/)?
>>b) The example seems to show the /boot being outside the LVM area, is that correct or does the how-to mean to show the /boot as being within the domain of the LVM controlled area?
>>c) How will using ReiserFS on my root partition and LVM over the root affect what I need to do for an initrd and kernel compilation options?
>>
>>Once the LVM implementation is completed with everything in the / partition, and ReiserFS on the root, and it boots up, then I plan to break apart the / into separate filesystems within the LVM environment. At that point, recommendations of what filesystems to create will be helpful.
>>
>>
>>Very Respectfully,
>>
>>Stuart Blake Tener, IT3, USNR-R, N3GWG
>>Beverly Hills, California
>>VTU 1904G (Volunteer Training Unit)
>>stuart@bh90210.net
>>west coast: (310)-358-0202 P.O. Box 16043, Beverly Hills, CA 90209-2043
>>east coast: (215)-338-6005 P.O. Box 45859, Philadelphia, PA 19149-5859
>>
>>Telecopier: (419)-715-6073 fax to email gateway via www.efax.com (it's free!)
>>
>>JOIN THE US NAVY RESERVE, SERVE YOUR COUNTRY, AND BENEFIT FROM IT ALL.
>>
>>Wednesday, September 12, 2001 2:01 AM
>>
>>
>
>
>
>_______________________________________________
>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
>�
>

Re: [linux-lvm] LVM

[Jason Edgecombe]

hi,

  I must ask what filesystem /boot is using. If you're using reiserfs,
then you MUST mount with the "notail" option for /boot. If you're using
ext2 of reiserfs with "notail" then I would recommend the you move /boot
to before the 1024th cylinder. (I like to always put /boot at the
beginning of the drive.)

Sincerely,
Jason Edgecombe


svetljo wrote:
> 
> i should tell you about that
> that was the problem that i had when i tried with /boot behind the first
> 1024cyl of the first disk
> some people tells that the new lilo can handle this (it comes with MDK-8)
> some people tells that probably a BIOS update should solve the problem
> it didn't work for me
> 
> you can try to update lilo to the latest beta version and to update the BIOS
> but with GRUB it works
> the problem is that LILO can not read from /boot
> my partitions
> /dev/hda1 470Mb win-boot
> extended
> /dev/hda5   32Mb /boot
> ......
> 
> can you boot with a floppy and install grub?  it must work
> IT3 Stuart B. Tener, USNR-R wrote:
> 
> >Svetjo:
> >
> >       /dev/hda1       w2k/pro
> >       /dev/hda2       /boot
> >       /dev/hda3       /
> >
> >       Something like the above?
> >
> >       Okay, I did that, and now I get "LI" when I booted up! What does "LI" in lilo mean? What part of my boot up sequence is broken?
> >
> >       Someone told me it meant my second stage boot loader was failing. What does that mean? What are the stages of booting? Can anyone hook me up here?
> >
> >       As far as I know, I have ReiserFS compiled into the kernel along with LVM support in the kernel.
> >
> >       I must admit ReiserFS has worked quite well for me, and is very bug-free. I am using the version that comes with the 2.4.8-12mdk (mandrake) kernel, so perhaps u tried an older version.
> >
> >
> >Very Respectfully,
> >
> >Stuart Blake Tener, IT3, USNR-R, N3GWG
> >Beverly Hills, California
> >VTU 1904G (Volunteer Training Unit)
> >stuart@bh90210.net
> >west coast: (310)-358-0202 P.O. Box 16043, Beverly Hills, CA 90209-2043
> >east coast: (215)-338-6005 P.O. Box 45859, Philadelphia, PA 19149-5859
> >
> >Telecopier: (419)-715-6073 fax to email gateway via www.efax.com (it's free!)
> >
> >JOIN THE US NAVY RESERVE, SERVE YOUR COUNTRY, AND BENEFIT FROM IT ALL.
> >
> >Wednesday, September 12, 2001 3:43 AM
> >
> >-----Original Message-----
> >From: linux-lvm-admin@sistina.com [mailto:linux-lvm-admin@sistina.com]On Behalf Of svetljo
> >Sent: Wednesday, September 12, 2001 2:59 AM
> >To: linux-lvm@sistina.com
> >Subject: Re: [linux-lvm] LVM
> >
> >Hi
> >you need a normal partition vor /boot not on LV and it would be good to
> >have also a normal partition as swap,
> >but in case you don't use swap you don't need to,
> >the thing is that the swap is much faster when it is on partition not file
> >you can try to do it without formating the second disk
> >you can shrink ReiserFS, then with diskdrake shrink the partition
> > and make a new one for boot and for the VG , make an LV on the VG ,
> >create filesystems on the LV and /boot, mount the LV /mnt/new-root ,
> >mkdir /mnt/new-root/boot and mount here the /boot partition
> >trasnfer your installation to /mnt/new-root:
> >cd /
> > find . -xdev | cpio -pm /mnt/new-root
> >
> >edit /mnt/new-root/etc/fstab to match the LV as / and ad an entry for /boot
> >
> >reboot
> >and pass to lilo root=/dev/[your VG]/[your / LV]
> >it should be working
> >
> >edit lilo.conf and reinstall lilo or grub ( i'm not shure that lilo can
> >boot from the end of 32Gb drive)
> >
> >reboot once more if everything is OK
> >you can make a PV from your old / and ad it to the VG
> >that should be it
> >
> >about the FS's
> >
> >smth important ( may be) as far i know only Reiserfs could be shrinked ,
> >you can only grow XFS and JFS you can not make them smaller
> >
> >i really like XFS,and not that much the others
> >i had some crashes and with reiserfs i have some file entries which are
> >reported to exist ,but they can not be stated when i try to delete them
> >or to see them
> >i have not much expiriance with JFS , but i'm hearing that it was not
> >that stable as of 1.0.3
> >and with XFS i found all lost files in " lost and find " and it was
> >pretty easy to bring them back
> >i mention only the journal ones becouse you are speaking about 32Gb
> >
> >
> >
> >
> >
> >
> >
> >IT3 Stuart B. Tener, USNR-R wrote:
> >
> >>LVM List members:
> >>
> >>      I have been doing some playing around and am not getting very far! Perhaps you can answer some questions and guide me.
> >>
> >>I have 2 32GB HDs, which I can have both in use on my laptop simultaneously. The 2nd HD I can erase to my hearts content. It's a staging drive.
> >>
> >>      My current configuration is:
> >>
> >>      /dev/hda1       windows 2000 pro
> >>      /dev/hda2       /       (Linux mandrake 8.0)
> >>
> >>      I do not have a swap partition at the moment (I have 512MB of ram, and I use a swap file if I need too), and have everything installed into the root (I know the drawbacks of this, but it made for simplicity at the time). I also use ReiserFS, and want to implement LVM.
> >>
> >>      The "How To" speaks of an example inclusive of a /boot partition and a swap partition. I ignored the swap partition, but was curious about the /boot partition in the how-to.
> >>
> >>a) Do I need to have a separate /boot partition, or can I create an LVM implementation (for the moment) with everything in the root (/)?
> >>b) The example seems to show the /boot being outside the LVM area, is that correct or does the how-to mean to show the /boot as being within the domain of the LVM controlled area?
> >>c) How will using ReiserFS on my root partition and LVM over the root affect what I need to do for an initrd and kernel compilation options?
> >>
> >>Once the LVM implementation is completed with everything in the / partition, and ReiserFS on the root, and it boots up, then I plan to break apart the / into separate filesystems within the LVM environment. At that point, recommendations of what filesystems to create will be helpful.
> >>
> >>
> >>Very Respectfully,
> >>
> >>Stuart Blake Tener, IT3, USNR-R, N3GWG
> >>Beverly Hills, California
> >>VTU 1904G (Volunteer Training Unit)
> >>stuart@bh90210.net
> >>west coast: (310)-358-0202 P.O. Box 16043, Beverly Hills, CA 90209-2043
> >>east coast: (215)-338-6005 P.O. Box 45859, Philadelphia, PA 19149-5859
> >>
> >>Telecopier: (419)-715-6073 fax to email gateway via www.efax.com (it's free!)
> >>
> >>JOIN THE US NAVY RESERVE, SERVE YOUR COUNTRY, AND BENEFIT FROM IT ALL.
> >>
> >>Wednesday, September 12, 2001 2:01 AM
> >>
> >>
> >
> >
> >
> >_______________________________________________
> >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
> >¥
> >
> 
> _______________________________________________
> 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

Re: [linux-lvm] LVM

[Ed Tomlinson]

On September 12, 2001 09:44 am, Jason Edgecombe wrote:
> hi,
>
>   I must ask what filesystem /boot is using. If you're using reiserfs,
> then you MUST mount with the "notail" option for /boot. If you're using
> ext2 of reiserfs with "notail" then I would recommend the you move /boot
> to before the 1024th cylinder. (I like to always put /boot at the
> beginning of the drive.)
>
> Sincerely,
> Jason Edgecombe

This used to be true.  Recient versions of lilo understand reiserfs tails, so you 
can mount with tails IF you have an up to date LILO.

Ed Tomlinson

RE: [linux-lvm] LVM

[IT3 Stuart B. Tener, USNR-R]

Mr. Tomlinson:

	I am curious what version of lilo in fact supports ReiserFS tails. I am running Mandrake 8.0, and using the lilo supplied therewith, and have been booting a / partition as ReiserFS (with tails I believe, how do I check?).


Very Respectfully, 

Stuart Blake Tener, IT3, USNR-R, N3GWG 
Beverly Hills, California
VTU 1904G (Volunteer Training Unit) 
stuart@bh90210.net 
west coast: (310)-358-0202 P.O. Box 16043, Beverly Hills, CA 90209-2043 
east coast: (215)-338-6005 P.O. Box 45859, Philadelphia, PA 19149-5859 

Telecopier: (419)-715-6073 fax to email gateway via www.efax.com (it's free!) 

JOIN THE US NAVY RESERVE, SERVE YOUR COUNTRY, AND BENEFIT FROM IT ALL. 

Wednesday, September 12, 2001 3:38 PM

-----Original Message-----
From: linux-lvm-admin@sistina.com [mailto:linux-lvm-admin@sistina.com]On Behalf Of Ed Tomlinson
Sent: Wednesday, September 12, 2001 9:08 AM
To: linux-lvm@sistina.com; Jason Edgecombe
Subject: Re: [linux-lvm] LVM

On September 12, 2001 09:44 am, Jason Edgecombe wrote:
> hi,
>
>   I must ask what filesystem /boot is using. If you're using reiserfs,
> then you MUST mount with the "notail" option for /boot. If you're using
> ext2 of reiserfs with "notail" then I would recommend the you move /boot
> to before the 1024th cylinder. (I like to always put /boot at the
> beginning of the drive.)
>
> Sincerely,
> Jason Edgecombe

This used to be true.  Recient versions of lilo understand reiserfs tails, so you
can mount with tails IF you have an up to date LILO.

Ed Tomlinson

_______________________________________________
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

Re: [linux-lvm] LVM

[Andreas Dilger]

On Sep 12, 2001  15:41 -0700, IT3 Stuart B. Tener, USNR-R wrote:
> 	I am curious what version of lilo in fact supports ReiserFS tails. I am running Mandrake 8.0, and using the lilo supplied therewith, and have been booting a / partition as ReiserFS (with tails I believe, how do I check?).

At least version 21.6+ support reiserfs tails (maybe earlier, I don't know).
You should be able to verify with "strings /sbin/lilo | grep -i reiserfs".
What it does is unpack the tail on any kernel/initrd files so that LILO
can map the blocks directly.  In a way, it is strange that this is needed,
since I thought tails only applied to files < 64kB or similar...

Cheers, Andreas
-- 
Andreas Dilger  \ "If a man ate a pound of pasta and a pound of antipasto,
                 \  would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/               -- Dogbert

RE: [linux-lvm] LVM

[IT3 Stuart B. Tener, USNR-R]

LVM Listmembers:

	The how-to is not clear on certain issues:

(a) should ReiserFS support be compiled into the kernel or be a module?
(b) Should LVM support be compiled into the kernel or be a module?
(c) If you use LVM support as a module or in the kernel how does this effect the need or configuration of the initrd? Someone told me I don't need initrd, if its built in the kernel, no?


Very Respectfully, 

Stuart Blake Tener, IT3, USNR-R, N3GWG 
Beverly Hills, California
VTU 1904G (Volunteer Training Unit) 
stuart@bh90210.net 
west coast: (310)-358-0202 P.O. Box 16043, Beverly Hills, CA 90209-2043 
east coast: (215)-338-6005 P.O. Box 45859, Philadelphia, PA 19149-5859 

Telecopier: (419)-715-6073 fax to email gateway via www.efax.com (it's free!) 

JOIN THE US NAVY RESERVE, SERVE YOUR COUNTRY, AND BENEFIT FROM IT ALL. 

Wednesday, September 12, 2001 4:26 PM

-----Original Message-----
From: linux-lvm-admin@sistina.com [mailto:linux-lvm-admin@sistina.com]On Behalf Of Andreas Dilger
Sent: Wednesday, September 12, 2001 4:21 PM
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] LVM

On Sep 12, 2001  15:41 -0700, IT3 Stuart B. Tener, USNR-R wrote:
>       I am curious what version of lilo in fact supports ReiserFS tails. I am running Mandrake 8.0, and using the lilo supplied therewith, and have been booting a / partition as ReiserFS (with tails I believe, how do I check?).

At least version 21.6+ support reiserfs tails (maybe earlier, I don't know).
You should be able to verify with "strings /sbin/lilo | grep -i reiserfs".
What it does is unpack the tail on any kernel/initrd files so that LILO
can map the blocks directly.  In a way, it is strange that this is needed,
since I thought tails only applied to files < 64kB or similar...

Cheers, Andreas
--
Andreas Dilger  \ "If a man ate a pound of pasta and a pound of antipasto,
                 \  would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/               -- Dogbert


_______________________________________________
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

Re: [linux-lvm] LVM

[svetljo]

>
>
>LVM Listmembers:
>
>	The how-to is not clear on certain issues:
>
>(a) should ReiserFS support be compiled into the kernel or be a module?
>(b) Should LVM support be compiled into the kernel or be a module?
>(c) If you use LVM support as a module or in the kernel how does this effect the need or configuration of the initrd? 
>
it's better to have them compiled in ,

>Someone told me I don't need initrd, if its built in the kernel, no?
>
it's not needed for software RAID, IBM's EVMS (still alpha status) and 
is on the to-do list of lvm
( i have read this in the previous messages)
but as of today you need initrd for the binaries for activating the VG's 
and LV's

>
>
>Very Respectfully, 
>
>Stuart Blake Tener, IT3, USNR-R, N3GWG 
>Beverly Hills, California
>VTU 1904G (Volunteer Training Unit) 
>stuart@bh90210.net 
>west coast: (310)-358-0202 P.O. Box 16043, Beverly Hills, CA 90209-2043 
>east coast: (215)-338-6005 P.O. Box 45859, Philadelphia, PA 19149-5859 
>
>Telecopier: (419)-715-6073 fax to email gateway via www.efax.com (it's free!) 
>
>JOIN THE US NAVY RESERVE, SERVE YOUR COUNTRY, AND BENEFIT FROM IT ALL. 
>
>Wednesday, September 12, 2001 4:26 PM
>
>-----Original Message-----
>From: linux-lvm-admin@sistina.com [mailto:linux-lvm-admin@sistina.com]On Behalf Of Andreas Dilger
>Sent: Wednesday, September 12, 2001 4:21 PM
>To: linux-lvm@sistina.com
>Subject: Re: [linux-lvm] LVM
>
>On Sep 12, 2001  15:41 -0700, IT3 Stuart B. Tener, USNR-R wrote:
>
>>      I am curious what version of lilo in fact supports ReiserFS tails. I am running Mandrake 8.0, and using the lilo supplied therewith, and have been booting a / partition as ReiserFS (with tails I believe, how do I check?).
>>
>
>At least version 21.6+ support reiserfs tails (maybe earlier, I don't know).
>You should be able to verify with "strings /sbin/lilo | grep -i reiserfs".
>What it does is unpack the tail on any kernel/initrd files so that LILO
>can map the blocks directly.  In a way, it is strange that this is needed,
>since I thought tails only applied to files < 64kB or similar...
>
>Cheers, Andreas
>--
>Andreas Dilger  \ "If a man ate a pound of pasta and a pound of antipasto,
>                 \  would they cancel out, leaving him still hungry?"
>http://www-mddsp.enel.ucalgary.ca/People/adilger/               -- Dogbert
>
>
>_______________________________________________
>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
>

RE: [linux-lvm] LVM

[IT3 Stuart B. Tener, USNR-R]

Svetljo:

	So for LVM, you do need to use the lvmcreate_initrd program or not? I am still not clear on that.

	If I need to make an lvmcreate_initrd, does not that mean it cannot be in the kernel?


Very Respectfully, 

Stuart Blake Tener, IT3, USNR-R, N3GWG 
Beverly Hills, California
VTU 1904G (Volunteer Training Unit) 
stuart@bh90210.net 
west coast: (310)-358-0202 P.O. Box 16043, Beverly Hills, CA 90209-2043 
east coast: (215)-338-6005 P.O. Box 45859, Philadelphia, PA 19149-5859 

Telecopier: (419)-715-6073 fax to email gateway via www.efax.com (it's free!) 

JOIN THE US NAVY RESERVE, SERVE YOUR COUNTRY, AND BENEFIT FROM IT ALL. 

Thursday, September 13, 2001 3:20 AM

-----Original Message-----
From: linux-lvm-admin@sistina.com [mailto:linux-lvm-admin@sistina.com]On Behalf Of svetljo
Sent: Thursday, September 13, 2001 12:49 AM
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] LVM

>
>
>LVM Listmembers:
>
>       The how-to is not clear on certain issues:
>
>(a) should ReiserFS support be compiled into the kernel or be a module?
>(b) Should LVM support be compiled into the kernel or be a module?
>(c) If you use LVM support as a module or in the kernel how does this effect the need or configuration of the initrd?
>
it's better to have them compiled in ,

>Someone told me I don't need initrd, if its built in the kernel, no?
>
it's not needed for software RAID, IBM's EVMS (still alpha status) and
is on the to-do list of lvm
( i have read this in the previous messages)
but as of today you need initrd for the binaries for activating the VG's
and LV's

>
>
>Very Respectfully,
>
>Stuart Blake Tener, IT3, USNR-R, N3GWG
>Beverly Hills, California
>VTU 1904G (Volunteer Training Unit)
>stuart@bh90210.net
>west coast: (310)-358-0202 P.O. Box 16043, Beverly Hills, CA 90209-2043
>east coast: (215)-338-6005 P.O. Box 45859, Philadelphia, PA 19149-5859
>
>Telecopier: (419)-715-6073 fax to email gateway via www.efax.com (it's free!)
>
>JOIN THE US NAVY RESERVE, SERVE YOUR COUNTRY, AND BENEFIT FROM IT ALL.
>
>Wednesday, September 12, 2001 4:26 PM
>
>-----Original Message-----
>From: linux-lvm-admin@sistina.com [mailto:linux-lvm-admin@sistina.com]On Behalf Of Andreas Dilger
>Sent: Wednesday, September 12, 2001 4:21 PM
>To: linux-lvm@sistina.com
>Subject: Re: [linux-lvm] LVM
>
>On Sep 12, 2001  15:41 -0700, IT3 Stuart B. Tener, USNR-R wrote:
>
>>      I am curious what version of lilo in fact supports ReiserFS tails. I am running Mandrake 8.0, and using the lilo supplied therewith, and have been booting a / partition as ReiserFS (with tails I believe, how do I check?).
>>
>
>At least version 21.6+ support reiserfs tails (maybe earlier, I don't know).
>You should be able to verify with "strings /sbin/lilo | grep -i reiserfs".
>What it does is unpack the tail on any kernel/initrd files so that LILO
>can map the blocks directly.  In a way, it is strange that this is needed,
>since I thought tails only applied to files < 64kB or similar...
>
>Cheers, Andreas
>--
>Andreas Dilger  \ "If a man ate a pound of pasta and a pound of antipasto,
>                 \  would they cancel out, leaving him still hungry?"
>http://www-mddsp.enel.ucalgary.ca/People/adilger/               -- Dogbert
>
>
>_______________________________________________
>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
>



_______________________________________________
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

Re: [linux-lvm] LVM

[Jason Edgecombe]

you MUST run lvmcreate_initrd and use the initrd it creates if you run
an LVM root fs.

It doesn't matter if LVM is in the kernel or as a module. If your root
is not in LVM, then I don't think that you have to use initrd.

Sincerely,
Jason Edgecombe


"IT3 Stuart B. Tener, USNR-R" wrote:
>         So for LVM, you do need to use the lvmcreate_initrd program or not? I am still not clear on that.
> 
>         If I need to make an lvmcreate_initrd, does not that mean it cannot be in the kernel?

RE: [linux-lvm] LVM

[IT3 Stuart B. Tener, USNR-R]

Mr. Edgecombe:

	Ah, I understand. Yes, I am trying to LVMize my root partition.


Very Respectfully, 

Stuart Blake Tener, IT3, USNR-R, N3GWG 
Beverly Hills, California
VTU 1904G (Volunteer Training Unit) 
stuart@bh90210.net 
west coast: (310)-358-0202 P.O. Box 16043, Beverly Hills, CA 90209-2043 
east coast: (215)-338-6005 P.O. Box 45859, Philadelphia, PA 19149-5859 

Telecopier: (419)-715-6073 fax to email gateway via www.efax.com (it's free!) 

JOIN THE US NAVY RESERVE, SERVE YOUR COUNTRY, AND BENEFIT FROM IT ALL. 

Thursday, September 13, 2001 9:49 AM

-----Original Message-----
From: linux-lvm-admin@sistina.com [mailto:linux-lvm-admin@sistina.com]On Behalf Of Jason Edgecombe
Sent: Thursday, September 13, 2001 6:01 AM
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] LVM

you MUST run lvmcreate_initrd and use the initrd it creates if you run
an LVM root fs.

It doesn't matter if LVM is in the kernel or as a module. If your root
is not in LVM, then I don't think that you have to use initrd.

Sincerely,
Jason Edgecombe


"IT3 Stuart B. Tener, USNR-R" wrote:
>         So for LVM, you do need to use the lvmcreate_initrd program or not? I am still not clear on that.
>
>         If I need to make an lvmcreate_initrd, does not that mean it cannot be in the kernel?

_______________________________________________
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

Re: [linux-lvm] LVM

[svetljo]

Hi
it should be

lvmcreate_initrd --nomod 2.4.8-12mdk
and it should create /boot/initrd-lvm-2.4.8-12mdk.gz -- the lvm-initrd

IT3 Stuart B. Tener, USNR-R wrote:

>Mr. Edgecombe:
>
>	Ah, I understand. Yes, I am trying to LVMize my root partition.
>
>
>Very Respectfully, 
>
>Stuart Blake Tener, IT3, USNR-R, N3GWG 
>Beverly Hills, California
>VTU 1904G (Volunteer Training Unit) 
>stuart@bh90210.net 
>west coast: (310)-358-0202 P.O. Box 16043, Beverly Hills, CA 90209-2043 
>east coast: (215)-338-6005 P.O. Box 45859, Philadelphia, PA 19149-5859 
>
>Telecopier: (419)-715-6073 fax to email gateway via www.efax.com (it's free!) 
>
>JOIN THE US NAVY RESERVE, SERVE YOUR COUNTRY, AND BENEFIT FROM IT ALL. 
>
>Thursday, September 13, 2001 9:49 AM
>
>-----Original Message-----
>From: linux-lvm-admin@sistina.com [mailto:linux-lvm-admin@sistina.com]On Behalf Of Jason Edgecombe
>Sent: Thursday, September 13, 2001 6:01 AM
>To: linux-lvm@sistina.com
>Subject: Re: [linux-lvm] LVM
>
>you MUST run lvmcreate_initrd and use the initrd it creates if you run
>an LVM root fs.
>
>It doesn't matter if LVM is in the kernel or as a module. If your root
>is not in LVM, then I don't think that you have to use initrd.
>
>Sincerely,
>Jason Edgecombe
>
>
>"IT3 Stuart B. Tener, USNR-R" wrote:
>
>>        So for LVM, you do need to use the lvmcreate_initrd program or not? I am still not clear on that.
>>
>>        If I need to make an lvmcreate_initrd, does not that mean it cannot be in the kernel?
>>
>
>_______________________________________________
>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
>

RE: [linux-lvm] LVM

[IT3 Stuart B. Tener, USNR-R]

Svetljo:

	It does not work. It gives me some funky messages when I try it. However, I must point out I am using LVM V 0.9.2-whatever. Are you using a new version? I have been told that the newer 1.0.1 version does not or will not work properly with Mandrake for some reason of their policy about versions or something, got me.


Very Respectfully, 

Stuart Blake Tener, IT3, USNR-R, N3GWG 
Beverly Hills, California
VTU 1904G (Volunteer Training Unit) 
stuart@bh90210.net 
west coast: (310)-358-0202 P.O. Box 16043, Beverly Hills, CA 90209-2043 
east coast: (215)-338-6005 P.O. Box 45859, Philadelphia, PA 19149-5859 

Telecopier: (419)-715-6073 fax to email gateway via www.efax.com (it's free!) 

JOIN THE US NAVY RESERVE, SERVE YOUR COUNTRY, AND BENEFIT FROM IT ALL. 

Thursday, September 13, 2001 1:29 PM

-----Original Message-----
From: linux-lvm-admin@sistina.com [mailto:linux-lvm-admin@sistina.com]On Behalf Of svetljo
Sent: Thursday, September 13, 2001 10:04 AM
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] LVM

Hi
it should be

lvmcreate_initrd --nomod 2.4.8-12mdk
and it should create /boot/initrd-lvm-2.4.8-12mdk.gz -- the lvm-initrd

IT3 Stuart B. Tener, USNR-R wrote:

>Mr. Edgecombe:
>
>       Ah, I understand. Yes, I am trying to LVMize my root partition.
>
>
>Very Respectfully,
>
>Stuart Blake Tener, IT3, USNR-R, N3GWG
>Beverly Hills, California
>VTU 1904G (Volunteer Training Unit)
>stuart@bh90210.net
>west coast: (310)-358-0202 P.O. Box 16043, Beverly Hills, CA 90209-2043
>east coast: (215)-338-6005 P.O. Box 45859, Philadelphia, PA 19149-5859
>
>Telecopier: (419)-715-6073 fax to email gateway via www.efax.com (it's free!)
>
>JOIN THE US NAVY RESERVE, SERVE YOUR COUNTRY, AND BENEFIT FROM IT ALL.
>
>Thursday, September 13, 2001 9:49 AM
>
>-----Original Message-----
>From: linux-lvm-admin@sistina.com [mailto:linux-lvm-admin@sistina.com]On Behalf Of Jason Edgecombe
>Sent: Thursday, September 13, 2001 6:01 AM
>To: linux-lvm@sistina.com
>Subject: Re: [linux-lvm] LVM
>
>you MUST run lvmcreate_initrd and use the initrd it creates if you run
>an LVM root fs.
>
>It doesn't matter if LVM is in the kernel or as a module. If your root
>is not in LVM, then I don't think that you have to use initrd.
>
>Sincerely,
>Jason Edgecombe
>
>
>"IT3 Stuart B. Tener, USNR-R" wrote:
>
>>        So for LVM, you do need to use the lvmcreate_initrd program or not? I am still not clear on that.
>>
>>        If I need to make an lvmcreate_initrd, does not that mean it cannot be in the kernel?
>>
>
>_______________________________________________
>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
>




_______________________________________________
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

Re: [linux-lvm] LVM

[svetljo]

Hi
it should be working regarding the tools you are using
can you send the error message
and try
ls /lib/modules
it should give you list of kernel versions you have installed
my case
ls /lib/modules
2.4.10-pre4-xfs 2.4.9-ac7 .....
and lvmcreate_initrd -nomod 2.4.10-pre4-xfs


i'm using linux-2.4.10-pre4-xfs and linux-2.4.9-ac7 with lvm-1.0.1 cvs 
version
but it should be working also with the old tools

and there is no problem with the mandrake kernel and the new version of lvm

IT3 Stuart B. Tener, USNR-R wrote:

>Svetljo:
>
>	It does not work. It gives me some funky messages when I try it. However, I must point out I am using LVM V 0.9.2-whatever. Are you using a new version? I have been told that the newer 1.0.1 version does not or will not work properly with Mandrake for some reason of their policy about versions or something, got me.
>
>
>Very Respectfully, 
>
>Stuart Blake Tener, IT3, USNR-R, N3GWG 
>Beverly Hills, California
>VTU 1904G (Volunteer Training Unit) 
>stuart@bh90210.net 
>west coast: (310)-358-0202 P.O. Box 16043, Beverly Hills, CA 90209-2043 
>east coast: (215)-338-6005 P.O. Box 45859, Philadelphia, PA 19149-5859 
>
>Telecopier: (419)-715-6073 fax to email gateway via www.efax.com (it's free!) 
>
>JOIN THE US NAVY RESERVE, SERVE YOUR COUNTRY, AND BENEFIT FROM IT ALL. 
>
>Thursday, September 13, 2001 1:29 PM
>
>-----Original Message-----
>From: linux-lvm-admin@sistina.com [mailto:linux-lvm-admin@sistina.com]On Behalf Of svetljo
>Sent: Thursday, September 13, 2001 10:04 AM
>To: linux-lvm@sistina.com
>Subject: Re: [linux-lvm] LVM
>
>Hi
>it should be
>
>lvmcreate_initrd --nomod 2.4.8-12mdk
>and it should create /boot/initrd-lvm-2.4.8-12mdk.gz -- the lvm-initrd
>
>IT3 Stuart B. Tener, USNR-R wrote:
>
>>Mr. Edgecombe:
>>
>>      Ah, I understand. Yes, I am trying to LVMize my root partition.
>>
>>
>>Very Respectfully,
>>
>>Stuart Blake Tener, IT3, USNR-R, N3GWG
>>Beverly Hills, California
>>VTU 1904G (Volunteer Training Unit)
>>stuart@bh90210.net
>>west coast: (310)-358-0202 P.O. Box 16043, Beverly Hills, CA 90209-2043
>>east coast: (215)-338-6005 P.O. Box 45859, Philadelphia, PA 19149-5859
>>
>>Telecopier: (419)-715-6073 fax to email gateway via www.efax.com (it's free!)
>>
>>JOIN THE US NAVY RESERVE, SERVE YOUR COUNTRY, AND BENEFIT FROM IT ALL.
>>
>>Thursday, September 13, 2001 9:49 AM
>>
>>-----Original Message-----
>>From: linux-lvm-admin@sistina.com [mailto:linux-lvm-admin@sistina.com]On Behalf Of Jason Edgecombe
>>Sent: Thursday, September 13, 2001 6:01 AM
>>To: linux-lvm@sistina.com
>>Subject: Re: [linux-lvm] LVM
>>
>>you MUST run lvmcreate_initrd and use the initrd it creates if you run
>>an LVM root fs.
>>
>>It doesn't matter if LVM is in the kernel or as a module. If your root
>>is not in LVM, then I don't think that you have to use initrd.
>>
>>Sincerely,
>>Jason Edgecombe
>>
>>
>>"IT3 Stuart B. Tener, USNR-R" wrote:
>>
>>>       So for LVM, you do need to use the lvmcreate_initrd program or not? I am still not clear on that.
>>>
>>>       If I need to make an lvmcreate_initrd, does not that mean it cannot be in the kernel?
>>>
>>_______________________________________________
>>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
>>
>
>
>
>
>_______________________________________________
>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
>

Re: [linux-lvm] LVM

[Arkadiusz Miskiewicz]

Jason Edgecombe <jedgecombe@carolina.rr.com> writes:

> you MUST run lvmcreate_initrd and use the initrd it creates if you run
> an LVM root fs.
btw. lvmcreate_initrd is broken. It copies /bin/bash and /bin/sh while
on some systems /bin/sh is link to /bin/othershell (like /bin/ksh on
my systems), so initrd created by lvmcreate_initrd is not usable on
these machines.

-- 
Arkadiusz Mi�kiewicz   IPv6 ready PLD Linux at http://www.pld.org.pl
misiek at pld.org.pl    AM2-6BONE, 1024/3DB19BBD, arekm@IrcNet, PWr

Re: [linux-lvm] LVM

[Andreas Dilger]

On Sep 19, 2001  13:12 +0200, Arkadiusz Miskiewicz wrote:
> > you MUST run lvmcreate_initrd and use the initrd it creates if you run
> > an LVM root fs.
> btw. lvmcreate_initrd is broken. It copies /bin/bash and /bin/sh while
> on some systems /bin/sh is link to /bin/othershell (like /bin/ksh on
> my systems), so initrd created by lvmcreate_initrd is not usable on
> these machines.

Please try the below patch.  If it works I can check it into CVS.

Cheers, Andreas
====================  initrd-1.0.1.diff  ==========================
diff -u -r1.12 lvmcreate_initrd
--- tools/lvmcreate_initrd	2001/08/30 18:57:31	1.12
+++ tools/lvmcreate_initrd	2001/09/19 22:50:03
@@ -135,7 +135,7 @@
 
 # The size of the ramdisk is automatically calculated unless this is set
 #INITRDSIZE=
-INITRDFILES="/sbin/vgchange /sbin/vgscan /bin/bash /bin/mount /bin/umount /bin/sh /bin/rm"
+INITRDFILES="/sbin/vgchange /sbin/vgscan /bin/mount /bin/umount /bin/rm"
 
 if [ "$USEMOD" ]; then
    # Check for an LVM module, otherwise it must be compiled into the kernel
@@ -343,6 +343,13 @@
 find $INITRDFILES | cpio -pdm $OPT_Q $TMPMNT
 if [ $? -ne 0 ]; then
    echo "$cmd -- ERROR cpio to ram disk"
+   cleanup 1
+fi
+
+# Copy /bin/sh directly to avoid issues with symlinks
+cp -p /bin/sh $TMPMNT/bin/sh
+if [ $? -ne 0 ]; then
+   echo "$cmd -- ERROR copying /bin/sh to ram disk"
    cleanup 1
 fi
--
Andreas Dilger  \ "If a man ate a pound of pasta and a pound of antipasto,
                 \  would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/               -- Dogbert

Re: [linux-lvm] LVM

[Arkadiusz Miskiewicz]

Andreas Dilger <adilger@turbolabs.com> writes:

> > btw. lvmcreate_initrd is broken. It copies /bin/bash and /bin/sh while
> > on some systems /bin/sh is link to /bin/othershell (like /bin/ksh on
> > my systems), so initrd created by lvmcreate_initrd is not usable on
> > these machines.
> 
> Please try the below patch.  If it works I can check it into CVS.
It follows symlink when copying shell, so IMO it's ok to commit.

Anyway created initrd won't work on PLD kernels due to other reason
- we don't have ext2 compiled into kernel; all filesystems
except ROMFS are compiled as modules because are kernels are highly
modularized (ROMFS is used on our initrd ramdisks). It will be nice
thing to see support for other FSes when creating ramdisks in
lvmcreate_initrd. Our tool for generating initrd ramdisks (geninitrd)
can use rom, ext2 and cram as FS but it doesn't support lvm yet :-)

> Cheers, Andreas

-- 
Arkadiusz Mi�kiewicz   IPv6 ready PLD Linux at http://www.pld.org.pl
misiek(at)pld.org.pl   AM2-6BONE, 1024/3DB19BBD, arekm(at)ircnet, PWr

Re: [linux-lvm] LVM - mkinitrd.sh

[Bas]

[-- Attachment #1: Type: text/plain, Size: 308 bytes --]

Hi,

I modified lvmcreate_initrd on my system because I'm not using cpio.

This is the modified version to work with cp, let me know if it works ... I
never had any problems with it and LVM is compiled in my kernel, no module.
I checked to se if it handles symlinks like it's supposed to, and it does.

Bas.

[-- Attachment #2: mkinitrd.sh --]
[-- Type: application/octet-stream, Size: 12717 bytes --]

#!/bin/sh
#
#  Copyright (C) 1997 - 2000  Heinz Mauelshagen, Sistina Software
# 
#  June 1999
#  December 1999
#  January 2000
#  January 2001
# 
#  LVM is free software; you can redistribute it and/or modify
#  it under the terms of the GNU General Public License as published by
#  the Free Software Foundation; either version 2, or (at your option)
#  any later version.
#  
#  LVM is distributed in the hope that it will be useful,
#  but WITHOUT ANY WARRANTY; without even the implied warranty of
#  MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
#  GNU General Public License for more details.
#  
#  You should have received a copy of the GNU General Public License
#  along with LVM; see the file COPYING.  If not, write to
#  the Free Software Foundation, 59 Temple Place - Suite 330,
#  Boston, MA 02111-1307, USA. 
# 

#
# Changelog
#
#   16/11/1999 - corrected -N type with mke2fs
#   19/12/1999 - use correct ramdisk size
#                strip shared library to save space
#   04/01/2000 - support /proc mount, because lvm_dir_cache now uses it
#   12/02/2001 - always create enough inodes in ramdisk for dev files
#   [AED]      - check all INITRDFILES for library dependencies
#              - make commands quiet and avoid redirecting errors to /dev/null
#              - use cleanup function for all errors, interrupts, normal exit
#   12/02/2001 - copy and strip shared libraries before putting on ramdisk
#   [AED]      - allow specification of /dev directory (in case of devfs)
#              - calculate ramdisk size from libraries, devices, INITRDFILES
#              - add verbose progress messages
#              - copy actual executables if we are using wrapper scripts
#   12/02/2001 - support monolithic kernels
#   14/02/2001 - add usage and command-line switches. Lots of other changes
#              - from Andreas Dilger
#   05/04/2001 - Ignore errors from depmod because we might be a monolithic
#                kernel
#


cmd=`basename $0`

TMPMNT=/tmp/mnt.$$
TMPLIB=/tmp/lib.$$
USEMOD=1

PATH=/bin:/sbin:/usr/bin:/usr/sbin:$PATH

usage () {
	echo "Create an initial ramdisk image for LVM root filesystem"
	echo "$cmd: [-h] [-i] [-M] [-v] [-V] [kernel version]"
	echo "      -h|--help     print this usage message"
	echo "      -i|--iop      specify LVM IOP version to use"
	echo "      -M|--nomod    do not set up module support in initrd"
	echo "      -v|--verbose  verbose progress messages"
	echo "      -V|--version  print script version and exit"
}

verbose () {
   [ "$VERBOSE" ] && echo "`echo $cmd | tr '[a-z0-9/_]' ' '` -- $1" || true
}

cleanup () {
  [ "`mount | grep $DEVRAM`" ] && verbose "unmounting $DEVRAM" && umount $DEVRAM
  [ -f $DEVRAM ] && verbose "removing $DEVRAM" && rm $DEVRAM
  [ -d $TMPMNT ] && verbose "removing $TMPMNT" && rmdir $TMPMNT
  [ -d $TMPLIB ] && verbose "removing $TMPLIB" && rm -r $TMPLIB
  verbose "exit with code $1"
  exit $1
}

trap "
  verbose 'Caught interrupt'
  echo 'Bye bye...'
  cleanup 1
" 1 2 3 15


create_fstab () {
   cat << FSTAB > $TMPMNT/etc/fstab
/dev/ram	/		ext2	defaults	0   0
proc		/proc		proc	defaults	0   0
FSTAB
   chmod 644 $TMPMNT/etc/fstab
}

create_linuxrc () {
   echo "#!/bin/sh" > $TMPMNT/linuxrc
   [ "$LVMMOD" ] && echo "/sbin/modprobe $LVMMOD" >> $TMPMNT/linuxrc
   cat << LINUXRC >> $TMPMNT/linuxrc
/bin/mount /proc
/sbin/vgscan
/sbin/vgchange -a y
/bin/umount /proc
LINUXRC
   chmod 555 $TMPMNT/linuxrc
}

#
# Main
#
echo "Logical Volume Manager 0.9.1_CVS by Heinz Mauelshagen  02/03/2001"

VERSION=`uname -r`

while [ $# -gt 0 ]; do
   case $1 in
   -h|--help) usage; exit 0;;
   -i|--iop) IOP=$2; shift;;
   -M|--nomod) USEMOD=""; shift;;
   -V|--version) exit 0;;
   -d|-v|--debug|--verbose) VERBOSE="y";;
   [2-9].[0-9]*.[0-9]*) VERSION=$1;;
   *) echo "$cmd -- invalid option '$1'"; usage; exit 0;;
   esac
   shift
done

INITRD=${INITRD:-"/boot/initrd-lvm-$VERSION.gz"}
#INITRD=${INITRD:-"/boot/initrd-lvm-$VERSION.gz"}
MODULES=/lib/modules/$VERSION
DEVRAM=/tmp/initrd.$$
DEV=${DEV:-"/dev"}

echo "$cmd -- make LVM initial ram disk $INITRD"
echo ""

# The size of the ramdisk is automatically calculated unless this is set
INITRDSIZE=8192
INITRDFILES="/sbin/vgchange /sbin/vgscan /bin/bash /bin/mount /bin/umount /bin/sh /bin/rm"

if [ "$USEMOD" ]; then
   # Check for an LVM module, otherwise it must be compiled into the kernel
   if [ -r $MODULES/kernel/drivers/md/lvm-mod.o ]; then
      LVMMOD="lvm-mod"
      INITRDFILES="$INITRDFILES $MODULES/kernel/drivers/md/$LVMMOD.o"
   elif [ -r $MODULES/block/lvm-mod.o ]; then
      LVMMOD="lvm-mod"
      INITRDFILES="$INITRDFILES $MODULES/block/$LVMMOD.o"
   elif [ -r $MODULES/block/lvm.o ]; then
      LVMMOD="lvm"
      INITRDFILES="$INITRDFILES $MODULES/block/$LVMMOD.o"
   fi

   if [ -x "/sbin/modprobe" ]; then
      INITRDFILES="$INITRDFILES /sbin/modprobe"
   elif [ "$LVMMOD" ]; then
      echo "$cmd -- have $LVMMOD but not /sbin/modprobe."
      cleanup 1
   fi
   if [ -x "/sbin/insmod" ]; then
      INITRDFILES="$INITRDFILES /sbin/insmod"
   elif [ "$LVMMOD" ]; then
      echo "$cmd -- have $LVMMOD but not /sbin/insmod."
      cleanup 1
   fi
   if [ -r "$MODULES/modules.dep" ]; then
      INITRDFILES="$INITRDFILES $MODULES/modules.dep"
   fi
fi

# If we have LVM wrapper scripts in /sbin, we need to fix this by including
# the actual executables into the initrd as well.
if [ -x /sbin/lvmiopversion ]; then
   # Use the IOP version, if specified.  Otherwise, if we are building for
   # the current kernel or there is only one IOP version installed, use it.
   if [ "$IOP" ]; then
      IOP="/lib/lvm-iop$IOP"
   elif [ "$VERSION" = "`uname -r`" ]; then
      IOP="/lib/lvm-iop`lvmiopversion`"
   elif [ `ls -d /lib/lvm-iop* | wc -w` -eq 1 ]; then
      IOP="`ls -d /lib/lvm-iop*`"
   fi
   for FILE in $INITRDFILES; do
   case $FILE in
   /sbin/vg*|/sbin/lv*|/sbin/pv*)
      if [ "`file $FILE 2> /dev/null | grep script`" ]; then
         verbose "$FILE is a wrapper script, resolving."
         if [ -z "$IOP" ]; then
            echo "$cmd -- need to set LVM IOP for kernel $VERSION with '-i'."
            cleanup 1
         fi
         NEWFILE="$IOP/`basename $FILE`"
	 if [ -x $NEWFILE ]; then
	    INITRDFILES="$INITRDFILES $NEWFILE"
         else
	    echo "$cmd -- can't find $NEWFILE, your initrd may not work."
	 fi
      fi ;;
   esac
   done
   INITRDFILES="$INITRDFILES /sbin/lvmiopversion"
fi

# Figure out which shared libraries we actually need in our initrd
echo "$cmd -- finding required shared libraries"
verbose "INITRDFILES: `echo $INITRDFILES`"
SHLIBS=`ldd $INITRDFILES 2>/dev/null | awk '{if (/=>/) { print $3 }}' | sort -u`
if [ $? -ne 0 ]; then
   echo "$cmd -- ERROR figuring out needed shared libraries"
   exit 1
fi

verbose "need: `echo $SHLIBS`"

# Copy shared libraries to a temp directory before stripping, so that we don't
# run out of room on the ramdisk while stripping the libraries.
echo "$cmd -- stripping shared libraries"
mkdir -p ${TMPLIB}/lib
for LIB in $SHLIBS; do
   verbose "copy $LIB to ${TMPLIB}${LIB}"
   cp $LIB ${TMPLIB}${LIB}
   if [ $? -ne 0 ]; then
      echo "$cmd -- ERROR copying shared library $LIB to ram disk"
      cleanup 1
   fi
   verbose "strip $TMPLIB$LIB"
   strip ${TMPLIB}${LIB}
   if [ $? -ne 0 ]; then
      echo "$cmd -- ERROR stripping shared library $LIB"
      cleanup 1
   fi
done

# Calculate the number of inodes needed, and the size of the ramdisk image.
# Don't forget that inodes take up space too, as does the filesystem metadata.
echo "$cmd -- calculating initrd filesystem parameters"
verbose "counting files in: $DEV $TMPLIB \$INITRDFILES"
NUMINO="`find $DEV $TMPLIB $INITRDFILES | wc -w`"
verbose "minimum: $NUMINO inodes + filesystem reserved inodes"
NUMINO=`expr $NUMINO + 64`
if [ -z "$INITRDSIZE" ]; then
   echo "$cmd -- calculating loopback file size"
   verbose "finding size of: $DEV $TMPLIB \$INITRDFILES"
   INITRDSIZE="`du -ck $DEV $TMPLIB $INITRDFILES | tail -1 | cut -f 1`"
   verbose "minimum: $INITRDSIZE kB for files + inodes + filesystem metadata"
   INITRDSIZE=`expr $INITRDSIZE + $NUMINO / 8 + 512`  # enough for ext2 fs + a bit
fi

echo "$cmd -- making loopback file ($INITRDSIZE kB)"
verbose "using $DEVRAM as a temporary loopback file"
dd if=/dev/zero of=$DEVRAM count=$INITRDSIZE bs=1024 > /dev/null 2>&1
if [ $? -ne 0 ]; then
   echo "$cmd -- ERROR creating loopback file"
   cleanup 1
fi

# Ext2 can only have 8 * blocksize inodes per group, so we may need to
# increase the number of groups created if there are lots of inodes.
if [ $NUMINO -gt $INITRDSIZE ]; then
   if [ $NUMINO -gt 8192 ]; then
      verbose "too many inodes for one group - need to create more groups"
      BPG=`expr $INITRDSIZE \* 8192 / $NUMINO`
      INODE_OPT="-g `expr $BPG + 8 - $BPG % 8` -N $NUMINO"
   else
      INODE_OPT="-N $NUMINO"
   fi
else
   INODE_OPT="-i `expr $INITRDSIZE \* 1024 / $NUMINO`"
fi

echo "$cmd -- making ram disk filesystem ($NUMINO inodes)"
verbose "mke2fs -F -m0 -L LVM-$VERSION $INODE_OPT $DEVRAM $INITRDSIZE"
[ "$VERBOSE" ] && OPT_Q="" || OPT_Q="-q"
mke2fs $OPT_Q -F -m0 -L LVM-$VERSION $INODE_OPT $DEVRAM $INITRDSIZE >/dev/null 2>&1
if [ $? -ne 0 ]; then
   echo "$cmd -- ERROR making ram disk filesystem"
   echo "$cmd -- ERROR you need to use mke2fs >= 1.14 or increase INITRDSIZE"
   cleanup 1
fi

verbose "creating mountpoint $TMPMNT"
mkdir -p "$TMPMNT"
if [ $? -ne 0 ]; then
   echo "$cmd -- ERROR making $TMPMNT"
   cleanup 1
fi

echo "$cmd -- mounting ram disk filesystem"
verbose "mount -o loop $DEVRAM $TMPMNT"
mount -oloop $DEVRAM $TMPMNT
if [ $? -ne 0 ]; then
   echo "$cmd -- ERROR mounting $DEVRAM on $TMPMNT"
   cleanup 1
fi

verbose "creating /etc /proc /lib in $TMPMNT"
mkdir -p $TMPMNT/etc $TMPMNT/proc $TMPMNT/lib/modules/$VERSION $TMPMNT/dev $TMPMNT/bin $TMPMNT/sbin
if [ $? -ne 0 ]; then
   echo "$cmd -- ERROR creating directories in $TMPMNT"
   cleanup 1
fi
verbose "removing $TMPMNT/lost+found"
rmdir $TMPMNT/lost+found

if [ "$USEMOD" ]; then
   #
   # create new modules configuration to avoid kmod complaining
   # about nonexsisting modules.
   #
   MODCONF=/etc/modules.conf
   [ ! -r $MODCONF -a -r /etc/conf.modules ] && MODCONF=/etc/conf.modules
   echo "$cmd -- creating new $MODCONF"
   verbose "all block and char modules will be turned off"
   MAJ=0
   while [ $MAJ -lt 256 ]; do
      echo "alias block-major-$MAJ	off"
      echo "alias char-major-$MAJ	off"
      MAJ=`expr $MAJ + 1`
   done > $TMPMNT/$MODCONF


   # to ensure, that modprobe doesn complain about timestamps
   echo "$cmd -- creating new modules.dep"
   depmod -a $VERSION
   if [ $? -ne 0 ]; then
      echo "$cmd -- ERROR running depmod"
      cleanup 1
   fi
fi

# copy necessary files to ram disk
echo "$cmd -- copying device files to ram disk"
[ "$VERBOSE" ] && OPT_Q="-v" || OPT_Q="--quiet"
verbose "find $DEV | cpio -pdm $TMPMNT"
#(cd $DEV; find . | cpio -pdm $OPT_Q $TMPMNT/dev)
(cd $DEV; cp -pRd /dev $TMPMNT)
if [ $? -ne 0 ]; then
   echo "$cmd -- ERROR cp to ram disk"
   cleanup 1
fi

echo "$cmd -- copying initrd files to ram disk"
verbose "find \$INITRDFILES | cpio -pdm $OPT_Q $TMPMNT"
#find $INITRDFILES | cpio -pdm $OPT_Q $TMPMNT
for i in $INITRDFILES
do
	cp -pRd $i "$TMPMNT""$i"
done
if [ $? -ne 0 ]; then
   echo "$cmd -- ERROR cp to ram disk"
   cleanup 1
fi

#mkdir ${TMPMNT}/lib
echo "$cmd -- copying shared libraries to ram disk"
verbose "find $TMPLIB | cpio -pdm $OPT_Q $TMPMNT"
#(cd $TMPLIB; find * | cpio -pdm $OPT_Q $TMPMNT)
(cd ${TMPLIB}/lib ; find * -exec cp -pRd '{}' ${TMPMNT}/lib ';')
if [ $? -ne 0 ]; then
   echo "$cmd -- ERROR copying shared libraries to ram disk"
   cleanup 1
fi

echo "$cmd -- creating new /linuxrc"
create_linuxrc
if [ $? -ne 0 ]; then
   echo "$cmd -- ERROR creating linuxrc"
   cleanup
   exit 1
fi

echo "$cmd -- creating new /etc/fstab"
create_fstab
if [ $? -ne 0 ]; then
   echo "$cmd -- ERROR creating /etc/fstab"
   cleanup 1
fi

echo "$cmd -- ummounting ram disk"
umount $DEVRAM
if [ $? -ne 0 ]; then
   echo "$cmd -- ERROR umounting $DEVRAM"
   cleanup 1
fi

echo "$cmd -- creating compressed initrd $INITRD"
verbose "dd if=$DEVRAM bs=1k count=$INITRDSIZE | gzip -9"
dd if=$DEVRAM bs=1k count=$INITRDSIZE 2>/dev/null | gzip -9 > $INITRD
if [ $? -ne 0 ]; then
   echo "$cmd -- ERROR creating $INITRD"
   cleanup 1
fi

cleanup 0

[linux-lvm] Search archives broken?

[Andrew Certain]

I recently deleted a bunch of mail from this list since it seemed silly to
clutter up my mailbox with information that is so easily available on the
web, or so I thought.  Unfortunately, the archive search at sistina seems
to be broken, or am I crazy?

No matter what I enter in the search box ("lvm," "volume," "the"), I get
that the search returned no results.  Am I doing something stupid or is it
busted?  If it's busted, is there a chance it will be fixed soon?

Andrew

PS. There are other links on the new site that are busted as well.  In
http://www.sistina.com/products_lvm.htm, the "Sistina Releases LVM 1.0"
link goes to a 404 (if you delete the spaces, it's correct).

Re: [linux-lvm] LVM

[Heinz J . Mauelshagen]

On Thu, Sep 13, 2001 at 03:27:30AM -0700, IT3 Stuart B. Tener, USNR-R wrote:
> Svetljo:
> 
> 	So for LVM, you do need to use the lvmcreate_initrd program or not? I am still not clear on that.
> 
> 	If I need to make an lvmcreate_initrd, does not that mean it cannot be in the kernel?

Because LVM doesn't have metadata read support directly in the driver, this
must be accomplished by running vgscan+vgchange from the /linuxrc script
of an initrd.

If you've got an initrd anyway, it doesn't force you to have the LVM driver
(and other drivers either) statically linked into the kernel.

Regards,
Heinz    -- The LVM Guy --

> 
> 
> Very Respectfully, 
> 
> Stuart Blake Tener, IT3, USNR-R, N3GWG 
> Beverly Hills, California
> VTU 1904G (Volunteer Training Unit) 
> stuart@bh90210.net 
> west coast: (310)-358-0202 P.O. Box 16043, Beverly Hills, CA 90209-2043 
> east coast: (215)-338-6005 P.O. Box 45859, Philadelphia, PA 19149-5859 
> 
> Telecopier: (419)-715-6073 fax to email gateway via www.efax.com (it's free!) 
> 
> JOIN THE US NAVY RESERVE, SERVE YOUR COUNTRY, AND BENEFIT FROM IT ALL. 
> 
> Thursday, September 13, 2001 3:20 AM
> 
> -----Original Message-----
> From: linux-lvm-admin@sistina.com [mailto:linux-lvm-admin@sistina.com]On Behalf Of svetljo
> Sent: Thursday, September 13, 2001 12:49 AM
> To: linux-lvm@sistina.com
> Subject: Re: [linux-lvm] LVM
> 
> >
> >
> >LVM Listmembers:
> >
> >       The how-to is not clear on certain issues:
> >
> >(a) should ReiserFS support be compiled into the kernel or be a module?
> >(b) Should LVM support be compiled into the kernel or be a module?
> >(c) If you use LVM support as a module or in the kernel how does this effect the need or configuration of the initrd?
> >
> it's better to have them compiled in ,
> 
> >Someone told me I don't need initrd, if its built in the kernel, no?
> >
> it's not needed for software RAID, IBM's EVMS (still alpha status) and
> is on the to-do list of lvm
> ( i have read this in the previous messages)
> but as of today you need initrd for the binaries for activating the VG's
> and LV's
> 
> >
> >
> >Very Respectfully,
> >
> >Stuart Blake Tener, IT3, USNR-R, N3GWG
> >Beverly Hills, California
> >VTU 1904G (Volunteer Training Unit)
> >stuart@bh90210.net
> >west coast: (310)-358-0202 P.O. Box 16043, Beverly Hills, CA 90209-2043
> >east coast: (215)-338-6005 P.O. Box 45859, Philadelphia, PA 19149-5859
> >
> >Telecopier: (419)-715-6073 fax to email gateway via www.efax.com (it's free!)
> >
> >JOIN THE US NAVY RESERVE, SERVE YOUR COUNTRY, AND BENEFIT FROM IT ALL.
> >
> >Wednesday, September 12, 2001 4:26 PM
> >
> >-----Original Message-----
> >From: linux-lvm-admin@sistina.com [mailto:linux-lvm-admin@sistina.com]On Behalf Of Andreas Dilger
> >Sent: Wednesday, September 12, 2001 4:21 PM
> >To: linux-lvm@sistina.com
> >Subject: Re: [linux-lvm] LVM
> >
> >On Sep 12, 2001  15:41 -0700, IT3 Stuart B. Tener, USNR-R wrote:
> >
> >>      I am curious what version of lilo in fact supports ReiserFS tails. I am running Mandrake 8.0, and using the lilo supplied therewith, and have been booting a / partition as ReiserFS (with tails I believe, how do I check?).
> >>
> >
> >At least version 21.6+ support reiserfs tails (maybe earlier, I don't know).
> >You should be able to verify with "strings /sbin/lilo | grep -i reiserfs".
> >What it does is unpack the tail on any kernel/initrd files so that LILO
> >can map the blocks directly.  In a way, it is strange that this is needed,
> >since I thought tails only applied to files < 64kB or similar...
> >
> >Cheers, Andreas
> >--
> >Andreas Dilger  \ "If a man ate a pound of pasta and a pound of antipasto,
> >                 \  would they cancel out, leaving him still hungry?"
> >http://www-mddsp.enel.ucalgary.ca/People/adilger/               -- Dogbert
> >
> >
> >_______________________________________________
> >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
> >
> 
> 
> 
> _______________________________________________
> 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
> ?????????????????????????????????????{??[?????x%??e?{??[?????)???&??i?????l????)???&?f??f??X??)???b??????y?m???0s??3??^[m????\f??+-?v?r?????=?\x1e??h??????

*** Software bugs are stupid.
    Nevertheless it needs not so stupid people to solve them ***

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Heinz Mauelshagen                                 Sistina Software Inc.
Senior Consultant/Developer                       Am Sonnenhang 11
                                                  56242 Marienrachdorf
                                                  Germany
Mauelshagen@Sistina.com                           +49 2626 141200
                                                       FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Re: [linux-lvm] LVM

[svetljo]

IT3 Stuart B. Tener, USNR-R wrote:

>Svetljo:
>
>	So for LVM, you do need to use the lvmcreate_initrd program or not? I am still not clear on that.
>
>	If I need to make an lvmcreate_initrd, does not that mean it cannot be in the kernel?
>
there is no trouble if you compile in FS and LVM and so on
but you need lvmcreate_initrd vor creating the ramdisk which contain the 
binaries needed to activate the VG's
you can use lvmcreate_initrd --nomod [ your kernel ] to create the 
initrd without modules

>
>Very Respectfully, 
>
>Stuart Blake Tener, IT3, USNR-R, N3GWG 
>Beverly Hills, California
>VTU 1904G (Volunteer Training Unit) 
>stuart@bh90210.net 
>west coast: (310)-358-0202 P.O. Box 16043, Beverly Hills, CA 90209-2043 
>east coast: (215)-338-6005 P.O. Box 45859, Philadelphia, PA 19149-5859 
>
>Telecopier: (419)-715-6073 fax to email gateway via www.efax.com (it's free!) 
>
>JOIN THE US NAVY RESERVE, SERVE YOUR COUNTRY, AND BENEFIT FROM IT ALL. 
>
>Thursday, September 13, 2001 3:20 AM
>
>-----Original Message-----
>From: linux-lvm-admin@sistina.com [mailto:linux-lvm-admin@sistina.com]On Behalf Of svetljo
>Sent: Thursday, September 13, 2001 12:49 AM
>To: linux-lvm@sistina.com
>Subject: Re: [linux-lvm] LVM
>
>>
>>LVM Listmembers:
>>
>>      The how-to is not clear on certain issues:
>>
>>(a) should ReiserFS support be compiled into the kernel or be a module?
>>(b) Should LVM support be compiled into the kernel or be a module?
>>(c) If you use LVM support as a module or in the kernel how does this effect the need or configuration of the initrd?
>>
>it's better to have them compiled in ,
>
>>Someone told me I don't need initrd, if its built in the kernel, no?
>>
>it's not needed for software RAID, IBM's EVMS (still alpha status) and
>is on the to-do list of lvm
>( i have read this in the previous messages)
>but as of today you need initrd for the binaries for activating the VG's
>and LV's
>
>>
>>Very Respectfully,
>>
>>Stuart Blake Tener, IT3, USNR-R, N3GWG
>>Beverly Hills, California
>>VTU 1904G (Volunteer Training Unit)
>>stuart@bh90210.net
>>west coast: (310)-358-0202 P.O. Box 16043, Beverly Hills, CA 90209-2043
>>east coast: (215)-338-6005 P.O. Box 45859, Philadelphia, PA 19149-5859
>>
>>Telecopier: (419)-715-6073 fax to email gateway via www.efax.com (it's free!)
>>
>>JOIN THE US NAVY RESERVE, SERVE YOUR COUNTRY, AND BENEFIT FROM IT ALL.
>>
>>Wednesday, September 12, 2001 4:26 PM
>>
>>-----Original Message-----
>>From: linux-lvm-admin@sistina.com [mailto:linux-lvm-admin@sistina.com]On Behalf Of Andreas Dilger
>>Sent: Wednesday, September 12, 2001 4:21 PM
>>To: linux-lvm@sistina.com
>>Subject: Re: [linux-lvm] LVM
>>
>>On Sep 12, 2001  15:41 -0700, IT3 Stuart B. Tener, USNR-R wrote:
>>
>>>     I am curious what version of lilo in fact supports ReiserFS tails. I am running Mandrake 8.0, and using the lilo supplied therewith, and have been booting a / partition as ReiserFS (with tails I believe, how do I check?).
>>>
>>At least version 21.6+ support reiserfs tails (maybe earlier, I don't know).
>>You should be able to verify with "strings /sbin/lilo | grep -i reiserfs".
>>What it does is unpack the tail on any kernel/initrd files so that LILO
>>can map the blocks directly.  In a way, it is strange that this is needed,
>>since I thought tails only applied to files < 64kB or similar...
>>
>>Cheers, Andreas
>>--
>>Andreas Dilger  \ "If a man ate a pound of pasta and a pound of antipasto,
>>                \  would they cancel out, leaving him still hungry?"
>>http://www-mddsp.enel.ucalgary.ca/People/adilger/               -- Dogbert
>>
>>
>>_______________________________________________
>>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
>>
>
>
>
>_______________________________________________
>linux-lvm mailing list
>linux-lvm@sistina.com
>http://lists.sistina.com/mailman/listinfo/linux-lvm
>

RE: [linux-lvm] LVM

[IT3 Stuart B. Tener, USNR-R]

Svetljo:

	Lvmcreate_initrd -nomod I understand, what is the signifigance of "[ your kernel ]"? do I put the path to the kernel there? Can you give an example of what command like arguments I would type? My kernel version is 2.4.8-12mdk.


Very Respectfully, 

Stuart Blake Tener, IT3, USNR-R, N3GWG 
Beverly Hills, California
VTU 1904G (Volunteer Training Unit) 
stuart@bh90210.net 
west coast: (310)-358-0202 P.O. Box 16043, Beverly Hills, CA 90209-2043 
east coast: (215)-338-6005 P.O. Box 45859, Philadelphia, PA 19149-5859 

Telecopier: (419)-715-6073 fax to email gateway via www.efax.com (it's free!) 

JOIN THE US NAVY RESERVE, SERVE YOUR COUNTRY, AND BENEFIT FROM IT ALL. 

Thursday, September 13, 2001 9:32 AM

-----Original Message-----
From: linux-lvm-admin@sistina.com [mailto:linux-lvm-admin@sistina.com]On Behalf Of svetljo
Sent: Thursday, September 13, 2001 6:36 AM
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] LVM


IT3 Stuart B. Tener, USNR-R wrote:

>Svetljo:
>
>       So for LVM, you do need to use the lvmcreate_initrd program or not? I am still not clear on that.
>
>       If I need to make an lvmcreate_initrd, does not that mean it cannot be in the kernel?
>
there is no trouble if you compile in FS and LVM and so on
but you need lvmcreate_initrd vor creating the ramdisk which contain the
binaries needed to activate the VG's
you can use lvmcreate_initrd --nomod [ your kernel ] to create the
initrd without modules

>
>Very Respectfully,
>
>Stuart Blake Tener, IT3, USNR-R, N3GWG
>Beverly Hills, California
>VTU 1904G (Volunteer Training Unit)
>stuart@bh90210.net
>west coast: (310)-358-0202 P.O. Box 16043, Beverly Hills, CA 90209-2043
>east coast: (215)-338-6005 P.O. Box 45859, Philadelphia, PA 19149-5859
>
>Telecopier: (419)-715-6073 fax to email gateway via www.efax.com (it's free!)
>
>JOIN THE US NAVY RESERVE, SERVE YOUR COUNTRY, AND BENEFIT FROM IT ALL.
>
>Thursday, September 13, 2001 3:20 AM
>
>-----Original Message-----
>From: linux-lvm-admin@sistina.com [mailto:linux-lvm-admin@sistina.com]On Behalf Of svetljo
>Sent: Thursday, September 13, 2001 12:49 AM
>To: linux-lvm@sistina.com
>Subject: Re: [linux-lvm] LVM
>
>>
>>LVM Listmembers:
>>
>>      The how-to is not clear on certain issues:
>>
>>(a) should ReiserFS support be compiled into the kernel or be a module?
>>(b) Should LVM support be compiled into the kernel or be a module?
>>(c) If you use LVM support as a module or in the kernel how does this effect the need or configuration of the initrd?
>>
>it's better to have them compiled in ,
>
>>Someone told me I don't need initrd, if its built in the kernel, no?
>>
>it's not needed for software RAID, IBM's EVMS (still alpha status) and
>is on the to-do list of lvm
>( i have read this in the previous messages)
>but as of today you need initrd for the binaries for activating the VG's
>and LV's
>
>>
>>Very Respectfully,
>>
>>Stuart Blake Tener, IT3, USNR-R, N3GWG
>>Beverly Hills, California
>>VTU 1904G (Volunteer Training Unit)
>>stuart@bh90210.net
>>west coast: (310)-358-0202 P.O. Box 16043, Beverly Hills, CA 90209-2043
>>east coast: (215)-338-6005 P.O. Box 45859, Philadelphia, PA 19149-5859
>>
>>Telecopier: (419)-715-6073 fax to email gateway via www.efax.com (it's free!)
>>
>>JOIN THE US NAVY RESERVE, SERVE YOUR COUNTRY, AND BENEFIT FROM IT ALL.
>>
>>Wednesday, September 12, 2001 4:26 PM
>>
>>-----Original Message-----
>>From: linux-lvm-admin@sistina.com [mailto:linux-lvm-admin@sistina.com]On Behalf Of Andreas Dilger
>>Sent: Wednesday, September 12, 2001 4:21 PM
>>To: linux-lvm@sistina.com
>>Subject: Re: [linux-lvm] LVM
>>
>>On Sep 12, 2001  15:41 -0700, IT3 Stuart B. Tener, USNR-R wrote:
>>
>>>     I am curious what version of lilo in fact supports ReiserFS tails. I am running Mandrake 8.0, and using the lilo supplied therewith, and have been booting a / partition as ReiserFS (with tails I believe, how do I check?).
>>>
>>At least version 21.6+ support reiserfs tails (maybe earlier, I don't know).
>>You should be able to verify with "strings /sbin/lilo | grep -i reiserfs".
>>What it does is unpack the tail on any kernel/initrd files so that LILO
>>can map the blocks directly.  In a way, it is strange that this is needed,
>>since I thought tails only applied to files < 64kB or similar...
>>
>>Cheers, Andreas
>>--
>>Andreas Dilger  \ "If a man ate a pound of pasta and a pound of antipasto,
>>                \  would they cancel out, leaving him still hungry?"
>>http://www-mddsp.enel.ucalgary.ca/People/adilger/               -- Dogbert
>>
>>
>>_______________________________________________
>>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
>>
>
>
>
>_______________________________________________
>linux-lvm mailing list
>linux-lvm@sistina.com
>http://lists.sistina.com/mailman/listinfo/linux-lvm
>



_______________________________________________
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

Re: [linux-lvm] LVM

[svetljo]

Mandrake 8 use lilo 21.7 - it should be working

Andreas Dilger wrote:

>On Sep 12, 2001  15:41 -0700, IT3 Stuart B. Tener, USNR-R wrote:
>
>>	I am curious what version of lilo in fact supports ReiserFS tails. I am running Mandrake 8.0, and using the lilo supplied therewith, and have been booting a / partition as ReiserFS (with tails I believe, how do I check?).
>>
>
>At least version 21.6+ support reiserfs tails (maybe earlier, I don't know).
>You should be able to verify with "strings /sbin/lilo | grep -i reiserfs".
>What it does is unpack the tail on any kernel/initrd files so that LILO
>can map the blocks directly.  In a way, it is strange that this is needed,
>since I thought tails only applied to files < 64kB or similar...
>
>Cheers, Andreas
>

RE: [linux-lvm] LVM

[IT3 Stuart B. Tener, USNR-R]

Svetljo:

        Yes, I did determine I am in fact using lilo 21.7, and that does show why ReiserFS was bootable (absent LVM), however, with LVM I have never gotten Linux to boot up yet.


Very Respectfully,

Stuart Blake Tener, IT3, USNR-R, N3GWG
Beverly Hills, California
VTU 1904G (Volunteer Training Unit)
stuart@bh90210.net
west coast: (310)-358-0202 P.O. Box 16043, Beverly Hills, CA 90209-2043
east coast: (215)-338-6005 P.O. Box 45859, Philadelphia, PA 19149-5859

Telecopier: (419)-715-6073 fax to email gateway via www.efax.com (it's free!)

JOIN THE US NAVY RESERVE, SERVE YOUR COUNTRY, AND BENEFIT FROM IT ALL.

Thursday, September 13, 2001 3:17 AM

-----Original Message-----
From: linux-lvm-admin@sistina.com [mailto:linux-lvm-admin@sistina.com]On Behalf Of svetljo
Sent: Thursday, September 13, 2001 12:51 AM
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] LVM

Mandrake 8 use lilo 21.7 - it should be working

Andreas Dilger wrote:

>On Sep 12, 2001  15:41 -0700, IT3 Stuart B. Tener, USNR-R wrote:
>
>>      I am curious what version of lilo in fact supports ReiserFS tails. I am running Mandrake 8.0, and using the lilo supplied therewith, and have been booting a / partition as ReiserFS (with tails I believe, how do I check?).
>>
>
>At least version 21.6+ support reiserfs tails (maybe earlier, I don't know).
>You should be able to verify with "strings /sbin/lilo | grep -i reiserfs".
>What it does is unpack the tail on any kernel/initrd files so that LILO
>can map the blocks directly.  In a way, it is strange that this is needed,
>since I thought tails only applied to files < 64kB or similar...
>
>Cheers, Andreas
>



_______________________________________________
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

Re: [linux-lvm] LVM

[Jason Edgecombe]

hi,

  according to reiserfs's FAQ:
http://www.reiserfs.org/faq.html#ReiserFS-as-root

you need the notail option on the /boot partition.
the fstab might look as follows:
/dev/hda1    /boot   reiserfs    defaults,notail  0 0
/dev/hda2    /   reiserfs    defaults  0 0

if there isn't the word "notail" in the fourth column of your root fstab
entry, then you ARE booting with tails.

according the lilo changelog:
ftp://brun.dyndns.org/pub/linux/lilo/CHANGES

lilo has been able to boot from a reiserfs partition with tail support
since version 21.6 (Oct. 1, 2000)

*under an rpm-based distro such as redhat or mandrake, "rpm -qi lilo"
should give you the version. (assuming you haven't downloaded lilo as a
tarball and compiled it.)

Both were last modified in August 2001, I don't know which to believe.
For safety sake, I made my /boot ext2. Most recent computers (within the
past two years) can boot from a partition after the 1024 boundary. I
just like to make a separate /boot at the beginning of the drive as a
precaution.

as for the matter of initrd's, this is the way that I understand it:
in a non-lvm root fs, your root fs type must either be compiled in or in
the initrd image.
in a lvm root, you MUST have an initrd even if lvm is compiled into the
kernel (not as a module) because you need to run a vgchange -ay and you
need your lvm config files in the initrd.

as for having /boot (booting the kernel) straight in an lvm fs, I have
no idea.


If I am wrong, someone please correct me.

Sincerely,
Jason Edgecombe

"IT3 Stuart B. Tener, USNR-R" wrote:
>         I am curious what version of lilo in fact supports ReiserFS tails. I am running Mandrake 8.0, and using the lilo supplied therewith, and have been booting a / partition as ReiserFS (with tails I believe, how do I check?).

RE: [linux-lvm] LVM

[IT3 Stuart B. Tener, USNR-R]

Dear Sir:

	I have placed below a copy of the dmesg output from my attempt at booting the /dev/vg/root I created. However, I then was able to boot using the /dev/hda1 (which has a ReiserFS non-LVM bootable partition).

	Any analysis you can provide would be well appreciated. I will try some of the issues you mention here within.

Linux version 2.4.8-12mdk (root@linux02) (gcc version 2.96 20000731 (Linux-Mandrake 8.0 2.96-0.48mdk)) #20 Wed Sep 12 04:22:13 PDT 2001
BIOS-provided physical RAM map:
 BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
 BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
 BIOS-e820: 0000000000100000 - 000000001ffea800 (usable)
 BIOS-e820: 000000001ffea800 - 0000000020000000 (reserved)
 BIOS-e820: 00000000feea0000 - 00000000fef00000 (reserved)
 BIOS-e820: 00000000ffb80000 - 0000000100000000 (reserved)
On node 0 totalpages: 131050
zone(0): 4096 pages.
zone(1): 126954 pages.
zone(2): 0 pages.
Kernel command line: BOOT_IMAGE=linux_hda1 ro root=301 ramdisk=8192 hdb=ide-scsi idebus=66 ide0=dma ide1=dma
ide_setup: hdb=ide-scsi
ide_setup: idebus=66
ide_setup: ide0=dma
ide_setup: ide1=dma
Initializing CPU#0
Detected 997.833 MHz processor.
Console: colour dummy device 80x25
Calibrating delay loop... 1992.29 BogoMIPS
Memory: 512248k/524200k available (1164k kernel code, 11564k reserved, 312k data, 216k init, 0k highmem)
Dentry-cache hash table entries: 65536 (order: 7, 524288 bytes)
Inode-cache hash table entries: 32768 (order: 6, 262144 bytes)
Mount-cache hash table entries: 8192 (order: 4, 65536 bytes)
Buffer-cache hash table entries: 32768 (order: 5, 131072 bytes)
Page-cache hash table entries: 131072 (order: 7, 524288 bytes)
CPU: Before vendor init, caps: 0383f9ff 00000000 00000000, vendor = 0
CPU: L1 I cache: 16K, L1 D cache: 16K
CPU: L2 cache: 256K
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU: After vendor init, caps: 0383f9ff 00000000 00000000 00000000
CPU:     After generic, caps: 0383f9ff 00000000 00000000 00000000
CPU:             Common caps: 0383f9ff 00000000 00000000 00000000
CPU: Intel Pentium III (Coppermine) stepping 0a
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
mtrr: v1.40 (20010327) Richard Gooch (rgooch@atnf.csiro.au)
mtrr: detected mtrr type: Intel
PCI: PCI BIOS revision 2.10 entry at 0xfc06e, last bus=8
PCI: Using configuration type 1
PCI: Probing PCI hardware
Unknown bridge resource 2: assuming transparent
Unknown bridge resource 2: assuming transparent
PCI: Using IRQ router PIIX [8086/244c] at 00:1f.0
PnP: PNP BIOS installation structure at 0xc00fe2d0
PnP: PNP BIOS version 1.0, entry at f0000:e2f4, dseg at 40
PnP: 14 devices detected total
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
apm: BIOS version 1.2 Flags 0x03 (Driver version 1.14)
Starting kswapd v1.8
VFS: Diskquotas version dquot_6.5.0 initialized
ACPI: APM is already active, exiting
vesafb: framebuffer at 0xe8000000, mapped to 0xe0800000, size 32768k
vesafb: mode is 1024x768x16, linelength=2048, pages=20
vesafb: protected mode interface info at c000:6238
vesafb: scrolling: redraw
vesafb: directcolor: size=0:5:6:5, shift=0:11:5:0
Console: switching to colour frame buffer device 128x48
fb0: VESA VGA frame buffer device
pty: 256 Unix98 ptys configured
Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ SERIAL_PCI enabled
ttyS00 at 0x03f8 (irq = 4) is a 16550A
ttyS01 at 0x02f8 (irq = 3) is a 16550A
block: queued sectors max/low 340170kB/209098kB, 1024 slots per queue
RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
Uniform Multi-Platform E-IDE driver Revision: 6.31
ide: Assuming 66MHz system bus speed for PIO modes
PIIX4: IDE controller on PCI bus 00 dev f9
PIIX4: chipset revision 3
PIIX4: not 100% native mode: will probe irqs later
    ide0: BM-DMA at 0xbfa0-0xbfa7, BIOS settings: hda:DMA, hdb:DMA
    ide1: BM-DMA at 0xbfa8-0xbfaf, BIOS settings: hdc:DMA, hdd:pio
hda: IBM-DJSA-232, ATA DISK drive
hdb: TOSHIBA CD-RW/DVD-ROM SD-R2002, ATAPI CD/DVD-ROM drive
hdc: LS-120 SLIM3 00 UHD Floppy, ATAPI FLOPPY drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
hda: 62506080 sectors (32003 MB) w/1874KiB Cache, CHS=3890/255/63, UDMA(66)
ide-floppy driver 0.97
hdc: 1440kB, 2880 blocks, 512 sector size
hdc: 1440kB, 80/2/18 CHS, 150 kBps, 512 sector size, 720 rpm
Partition check:
 hda: hda1 hda2 hda3
 hdc: hdc1 hdc2 hdc3 hdc4
ide-floppy driver 0.97
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 4096 buckets, 32Kbytes
TCP: Hash tables configured (established 32768 bind 32768)
Linux IP multicast router 0.06 plus PIM-SM
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
RAMDISK: Compressed image found at block 0
Uncompressing.................................................................................................................................................................................................................................................................................done.
Freeing initrd memory: 869k freed
VFS: Mounted root (ext2 filesystem).
attempt to access beyond end of device
01:00: rw=0, want=8198 x(=0x), limit=8198
EXT2-fs error (device ramdisk(1,0)): ext2_read_inode: unable to read inode block - inode=8199, block=8197
attempt to access beyond end of device
01:00: rw=0, want=16390 x(=0x), limit=16390
EXT2-fs error (device ramdisk(1,0)): ext2_read_inode: unable to read inode block - inode=16387, block=16389
attempt to access beyond end of device
01:00: rw=0, want=8198 x(=0x), limit=8198
EXT2-fs error (device ramdisk(1,0)): ext2_read_inode: unable to read inode block - inode=8194, block=8197
reiserfs: checking transaction log (device 03:01) ...
Using r5 hash to sort names
ReiserFS version 3.6.25
VFS: Mounted root (reiserfs filesystem) readonly.
change_root: old root has d_count=2
Trying to unmount old root ... okay
Freeing unused kernel memory: 216k freed
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17519 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17519 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
LVM version 0.9.1_beta3  by Heinz Mauelshagen  (25/01/2001)
lvm -- Module successfully initialized
clm-6005: writing inode 17393 on readonly FS
clm-6005: writing inode 17519 on readonly FS
 hdc: hdc1 hdc2 hdc3 hdc4
 hdc: hdc1 hdc2 hdc3 hdc4
ide-floppy: hdc: I/O error, pc = 28, key =  5, asc = 21, ascq =  0
end_request: I/O error, dev 16:01 (hdc), sector 0
 hdc: hdc1 hdc2 hdc3 hdc4
ide-floppy: hdc: I/O error, pc = 28, key =  5, asc = 21, ascq =  0
end_request: I/O error, dev 16:02 (hdc), sector 0
 hdc: hdc1 hdc2 hdc3 hdc4
ide-floppy: hdc: I/O error, pc = 28, key =  5, asc = 21, ascq =  0
end_request: I/O error, dev 16:03 (hdc), sector 0
 hdc: hdc1 hdc2 hdc3 hdc4
ide-floppy: hdc: I/O error, pc = 28, key =  5, asc = 21, ascq =  0
end_request: I/O error, dev 16:04 (hdc), sector 0
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6005: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6005: writing inode 17393 on readonly FS
SCSI subsystem driver Revision: 1.00
scsi0 : SCSI host adapter emulation for IDE ATAPI devices
  Vendor: TOSHIBA   Model: DVD-ROM SD-R2002  Rev: 1D26
  Type:   CD-ROM                             ANSI SCSI revision: 02
md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
Linux Kernel Card Services 3.1.22
  options:  [pci] [cardbus] [pm]
PCI: Found IRQ 11 for device 02:0f.0
PCI: Sharing IRQ 11 with 00:1f.2
PCI: Sharing IRQ 11 with 02:0f.1
PCI: Sharing IRQ 11 with 02:0f.2
PCI: Found IRQ 11 for device 02:0f.1
PCI: Sharing IRQ 11 with 00:1f.2
PCI: Sharing IRQ 11 with 02:0f.0
PCI: Sharing IRQ 11 with 02:0f.2
Yenta IRQ list 06d8, PCI irq11
Socket status: 30000006
Yenta IRQ list 06d8, PCI irq11
Socket status: 30000006
cs: IO port probe 0x0c00-0x0cff: clean.
cs: IO port probe 0x0100-0x04ff: excluding 0x280-0x287 0x378-0x37f 0x4d0-0x4d7
cs: IO port probe 0x0a00-0x0aff: clean.
eepro100.c:v1.09j-t 9/29/99 Donald Becker http://cesdis.gsfc.nasa.gov/linux/drivers/eepro100.html
eepro100.c: $Revision: 1.36 $ 2000/11/17 Modified by Andrey V. Savochkin <saw@saw.sw.com.sg> and others
eth0: OEM i82557/i82558 10/100 Ethernet, 00:20:E0:66:C5:8A, I/O at 0xecc0, IRQ 11.
  Receiver lock-up bug exists -- enabling work-around.
  Board assembly 727095-002, Physical connectors present: RJ45
  Primary interface chip i82555 PHY #1.
  General self-test: passed.
  Serial sub-system self-test: passed.
  Internal registers self-test: passed.
  ROM checksum self-test: passed (0x04f4518b).
  Receiver lock-up workaround activated.
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
Winbond Super-IO detection, now testing ports 3F0,370,250,4E,2E ...
SMSC Super-IO detection, now testing Ports 2F0, 370 ...
PnPBIOS: Parport found PNPBIOS PNP0401 at io=0378,0778 irq=7 dma=1
0x378: FIFO is 16 bytes
0x378: writeIntrThreshold is 8
0x378: readIntrThreshold is 8
0x378: PWord is 8 bits
0x378: Interrupts are ISA-Pulses
0x378: ECP port cfgA=0x10 cfgB=0x00
0x378: ECP settings irq=<none or set by other means> dma=<none or set by other means>
parport0: PC-style at 0x378 (0x778), irq 7, dma 1 [PCSPP,TRISTATE,COMPAT,ECP,DMA]
parport0: cpp_daisy: aa5500ff(38)
parport0: assign_addrs: aa5500ff(38)
parport0: cpp_daisy: aa5500ff(38)
parport0: assign_addrs: aa5500ff(38)
lp0: using parport0 (interrupt-driven).



Very Respectfully, 

Stuart Blake Tener, IT3, USNR-R, N3GWG 
Beverly Hills, California
VTU 1904G (Volunteer Training Unit) 
stuart@bh90210.net 
west coast: (310)-358-0202 P.O. Box 16043, Beverly Hills, CA 90209-2043 
east coast: (215)-338-6005 P.O. Box 45859, Philadelphia, PA 19149-5859 

Telecopier: (419)-715-6073 fax to email gateway via www.efax.com (it's free!) 

JOIN THE US NAVY RESERVE, SERVE YOUR COUNTRY, AND BENEFIT FROM IT ALL. 

Wednesday, September 12, 2001 7:00 PM

-----Original Message-----
From: Jason Edgecombe [mailto:jedgecombe@carolina.rr.com]
Sent: Wednesday, September 12, 2001 6:02 PM
To: stuart@bh90210.net
Cc: linux-lvm@sistina.com
Subject: Re: [linux-lvm] LVM

hi,

  according to reiserfs's FAQ:
http://www.reiserfs.org/faq.html#ReiserFS-as-root

you need the notail option on the /boot partition.
the fstab might look as follows:
/dev/hda1    /boot   reiserfs    defaults,notail  0 0
/dev/hda2    /   reiserfs    defaults  0 0

if there isn't the word "notail" in the fourth column of your root fstab
entry, then you ARE booting with tails.

according the lilo changelog:
ftp://brun.dyndns.org/pub/linux/lilo/CHANGES

lilo has been able to boot from a reiserfs partition with tail support
since version 21.6 (Oct. 1, 2000)

*under an rpm-based distro such as redhat or mandrake, "rpm -qi lilo"
should give you the version. (assuming you haven't downloaded lilo as a
tarball and compiled it.)

Both were last modified in August 2001, I don't know which to believe.
For safety sake, I made my /boot ext2. Most recent computers (within the
past two years) can boot from a partition after the 1024 boundary. I
just like to make a separate /boot at the beginning of the drive as a
precaution.

as for the matter of initrd's, this is the way that I understand it:
in a non-lvm root fs, your root fs type must either be compiled in or in
the initrd image.
in a lvm root, you MUST have an initrd even if lvm is compiled into the
kernel (not as a module) because you need to run a vgchange -ay and you
need your lvm config files in the initrd.

as for having /boot (booting the kernel) straight in an lvm fs, I have
no idea.


If I am wrong, someone please correct me.

Sincerely,
Jason Edgecombe

"IT3 Stuart B. Tener, USNR-R" wrote:
>         I am curious what version of lilo in fact supports ReiserFS tails. I am running Mandrake 8.0, and using the lilo supplied therewith, and have been booting a / partition as ReiserFS (with tails I believe, how do I check?).

Re: [linux-lvm] LVM

[svetljo]

Hi

have you tried to pass to lilo : linux ramdisk_size=8192 or 
ramdisk_size=17000
after the lvm How-to you have to have in lilo.conf in the append section 
" ramdisk_size=8192 "

>
>NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
>RAMDISK: Compressed image found at block 0
>Uncompressing.................................................................................................................................................................................................................................................................................done.
>Freeing initrd memory: 869k freed
>VFS: Mounted root (ext2 filesystem).
>attempt to access beyond end of device
>01:00: rw=0, want=8198 x(=0x), limit=8198
>EXT2-fs error (device ramdisk(1,0)): ext2_read_inode: unable to read inode block - inode=8199, block=8197
>attempt to access beyond end of device
>01:00: rw=0, want=16390 x(=0x), limit=16390
>EXT2-fs error (device ramdisk(1,0)): ext2_read_inode: unable to read inode block - inode=16387, block=16389
>attempt to access beyond end of device
>01:00: rw=0, want=8198 x(=0x), limit=8198
>EXT2-fs error (device ramdisk(1,0)): ext2_read_inode: unable to read inode block - inode=8194, block=8197
>reiserfs: checking transaction log (device 03:01) ...
>Using r5 hash to sort names
>ReiserFS version 3.6.25
>VFS: Mounted root (reiserfs filesystem) readonly.
>change_root: old root has d_count=2
>Trying to unmount old root ... okay
>Freeing unused kernel memory: 216k freed
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17519 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17519 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>LVM version 0.9.1_beta3  by Heinz Mauelshagen  (25/01/2001)
>lvm -- Module successfully initialized
>clm-6005: writing inode 17393 on readonly FS
>clm-6005: writing inode 17519 on readonly FS
> hdc: hdc1 hdc2 hdc3 hdc4
> hdc: hdc1 hdc2 hdc3 hdc4
>ide-floppy: hdc: I/O error, pc = 28, key =  5, asc = 21, ascq =  0
>end_request: I/O error, dev 16:01 (hdc), sector 0
> hdc: hdc1 hdc2 hdc3 hdc4
>ide-floppy: hdc: I/O error, pc = 28, key =  5, asc = 21, ascq =  0
>end_request: I/O error, dev 16:02 (hdc), sector 0
> hdc: hdc1 hdc2 hdc3 hdc4
>ide-floppy: hdc: I/O error, pc = 28, key =  5, asc = 21, ascq =  0
>end_request: I/O error, dev 16:03 (hdc), sector 0
> hdc: hdc1 hdc2 hdc3 hdc4
>ide-floppy: hdc: I/O error, pc = 28, key =  5, asc = 21, ascq =  0
>end_request: I/O error, dev 16:04 (hdc), sector 0
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6005: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6005: writing inode 17393 on readonly FS
>SCSI subsystem driver Revision: 1.00
>scsi0 : SCSI host adapter emulation for IDE ATAPI devices
>  Vendor: TOSHIBA   Model: DVD-ROM SD-R2002  Rev: 1D26
>  Type:   CD-ROM                             ANSI SCSI revision: 02
>md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
>Linux Kernel Card Services 3.1.22
>  options:  [pci] [cardbus] [pm]
>PCI: Found IRQ 11 for device 02:0f.0
>PCI: Sharing IRQ 11 with 00:1f.2
>PCI: Sharing IRQ 11 with 02:0f.1
>PCI: Sharing IRQ 11 with 02:0f.2
>PCI: Found IRQ 11 for device 02:0f.1
>PCI: Sharing IRQ 11 with 00:1f.2
>PCI: Sharing IRQ 11 with 02:0f.0
>PCI: Sharing IRQ 11 with 02:0f.2
>Yenta IRQ list 06d8, PCI irq11
>Socket status: 30000006
>Yenta IRQ list 06d8, PCI irq11
>Socket status: 30000006
>cs: IO port probe 0x0c00-0x0cff: clean.
>cs: IO port probe 0x0100-0x04ff: excluding 0x280-0x287 0x378-0x37f 0x4d0-0x4d7
>cs: IO port probe 0x0a00-0x0aff: clean.
>eepro100.c:v1.09j-t 9/29/99 Donald Becker http://cesdis.gsfc.nasa.gov/linux/drivers/eepro100.html
>eepro100.c: $Revision: 1.36 $ 2000/11/17 Modified by Andrey V. Savochkin <saw@saw.sw.com.sg> and others
>eth0: OEM i82557/i82558 10/100 Ethernet, 00:20:E0:66:C5:8A, I/O at 0xecc0, IRQ 11.
>  Receiver lock-up bug exists -- enabling work-around.
>  Board assembly 727095-002, Physical connectors present: RJ45
>  Primary interface chip i82555 PHY #1.
>  General self-test: passed.
>  Serial sub-system self-test: passed.
>  Internal registers self-test: passed.
>  ROM checksum self-test: passed (0x04f4518b).
>  Receiver lock-up workaround activated.
>Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
>Winbond Super-IO detection, now testing ports 3F0,370,250,4E,2E ...
>SMSC Super-IO detection, now testing Ports 2F0, 370 ...
>PnPBIOS: Parport found PNPBIOS PNP0401 at io=0378,0778 irq=7 dma=1
>0x378: FIFO is 16 bytes
>0x378: writeIntrThreshold is 8
>0x378: readIntrThreshold is 8
>0x378: PWord is 8 bits
>0x378: Interrupts are ISA-Pulses
>0x378: ECP port cfgA=0x10 cfgB=0x00
>0x378: ECP settings irq=<none or set by other means> dma=<none or set by other means>
>parport0: PC-style at 0x378 (0x778), irq 7, dma 1 [PCSPP,TRISTATE,COMPAT,ECP,DMA]
>parport0: cpp_daisy: aa5500ff(38)
>parport0: assign_addrs: aa5500ff(38)
>parport0: cpp_daisy: aa5500ff(38)
>parport0: assign_addrs: aa5500ff(38)
>lp0: using parport0 (interrupt-driven).
>
>
>
>Very Respectfully, 
>
>Stuart Blake Tener, IT3, USNR-R, N3GWG 
>Beverly Hills, California
>VTU 1904G (Volunteer Training Unit) 
>stuart@bh90210.net 
>west coast: (310)-358-0202 P.O. Box 16043, Beverly Hills, CA 90209-2043 
>east coast: (215)-338-6005 P.O. Box 45859, Philadelphia, PA 19149-5859 
>
>Telecopier: (419)-715-6073 fax to email gateway via www.efax.com (it's free!) 
>
>JOIN THE US NAVY RESERVE, SERVE YOUR COUNTRY, AND BENEFIT FROM IT ALL. 
>
>Wednesday, September 12, 2001 7:00 PM
>
>-----Original Message-----
>From: Jason Edgecombe [mailto:jedgecombe@carolina.rr.com]
>Sent: Wednesday, September 12, 2001 6:02 PM
>To: stuart@bh90210.net
>Cc: linux-lvm@sistina.com
>Subject: Re: [linux-lvm] LVM
>
>hi,
>
>  according to reiserfs's FAQ:
>http://www.reiserfs.org/faq.html#ReiserFS-as-root
>
>you need the notail option on the /boot partition.
>the fstab might look as follows:
>/dev/hda1    /boot   reiserfs    defaults,notail  0 0
>/dev/hda2    /   reiserfs    defaults  0 0
>
>if there isn't the word "notail" in the fourth column of your root fstab
>entry, then you ARE booting with tails.
>
>according the lilo changelog:
>ftp://brun.dyndns.org/pub/linux/lilo/CHANGES
>
>lilo has been able to boot from a reiserfs partition with tail support
>since version 21.6 (Oct. 1, 2000)
>
>*under an rpm-based distro such as redhat or mandrake, "rpm -qi lilo"
>should give you the version. (assuming you haven't downloaded lilo as a
>tarball and compiled it.)
>
>Both were last modified in August 2001, I don't know which to believe.
>For safety sake, I made my /boot ext2. Most recent computers (within the
>past two years) can boot from a partition after the 1024 boundary. I
>just like to make a separate /boot at the beginning of the drive as a
>precaution.
>
>as for the matter of initrd's, this is the way that I understand it:
>in a non-lvm root fs, your root fs type must either be compiled in or in
>the initrd image.
>in a lvm root, you MUST have an initrd even if lvm is compiled into the
>kernel (not as a module) because you need to run a vgchange -ay and you
>need your lvm config files in the initrd.
>
>as for having /boot (booting the kernel) straight in an lvm fs, I have
>no idea.
>
>
>If I am wrong, someone please correct me.
>
>Sincerely,
>Jason Edgecombe
>
>"IT3 Stuart B. Tener, USNR-R" wrote:
>
>>        I am curious what version of lilo in fact supports ReiserFS tails. I am running Mandrake 8.0, and using the lilo supplied therewith, and have been booting a / partition as ReiserFS (with tails I believe, how do I check?).
>>

RE: [linux-lvm] LVM

[IT3 Stuart B. Tener, USNR-R]

Svetljo:

	I did try ramdisk_size = 8192, perhaps 17,000 is the number to try. Some people told me the parameter was "ramdisk = 8192", you say "ramdisk_size = 8192", do you know which is accurate?

	Also does it go in the append = "ramdisk_size=8192" or "ramdisk=8192"
	Or is it placed into the lilo.conf as a separate entry underneath the append command (or other lilo entry) ramdisk = 8192


Very Respectfully, 

Stuart Blake Tener, IT3, USNR-R, N3GWG 
Beverly Hills, California
VTU 1904G (Volunteer Training Unit) 
stuart@bh90210.net 
west coast: (310)-358-0202 P.O. Box 16043, Beverly Hills, CA 90209-2043 
east coast: (215)-338-6005 P.O. Box 45859, Philadelphia, PA 19149-5859 

Telecopier: (419)-715-6073 fax to email gateway via www.efax.com (it's free!) 

JOIN THE US NAVY RESERVE, SERVE YOUR COUNTRY, AND BENEFIT FROM IT ALL. 

Thursday, September 13, 2001 2:36 AM

-----Original Message-----
From: linux-lvm-admin@sistina.com [mailto:linux-lvm-admin@sistina.com]On Behalf Of svetljo
Sent: Thursday, September 13, 2001 12:32 AM
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] LVM


Hi

have you tried to pass to lilo : linux ramdisk_size=8192 or
ramdisk_size=17000
after the lvm How-to you have to have in lilo.conf in the append section
" ramdisk_size=8192 "

>
>NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
>RAMDISK: Compressed image found at block 0
>Uncompressing.................................................................................................................................................................................................................................................................................done.
>Freeing initrd memory: 869k freed
>VFS: Mounted root (ext2 filesystem).
>attempt to access beyond end of device
>01:00: rw=0, want=8198 x(=0x), limit=8198
>EXT2-fs error (device ramdisk(1,0)): ext2_read_inode: unable to read inode block - inode=8199, block=8197
>attempt to access beyond end of device
>01:00: rw=0, want=16390 x(=0x), limit=16390
>EXT2-fs error (device ramdisk(1,0)): ext2_read_inode: unable to read inode block - inode=16387, block=16389
>attempt to access beyond end of device
>01:00: rw=0, want=8198 x(=0x), limit=8198
>EXT2-fs error (device ramdisk(1,0)): ext2_read_inode: unable to read inode block - inode=8194, block=8197
>reiserfs: checking transaction log (device 03:01) ...
>Using r5 hash to sort names
>ReiserFS version 3.6.25
>VFS: Mounted root (reiserfs filesystem) readonly.
>change_root: old root has d_count=2
>Trying to unmount old root ... okay
>Freeing unused kernel memory: 216k freed
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17519 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17519 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>LVM version 0.9.1_beta3  by Heinz Mauelshagen  (25/01/2001)
>lvm -- Module successfully initialized
>clm-6005: writing inode 17393 on readonly FS
>clm-6005: writing inode 17519 on readonly FS
> hdc: hdc1 hdc2 hdc3 hdc4
> hdc: hdc1 hdc2 hdc3 hdc4
>ide-floppy: hdc: I/O error, pc = 28, key =  5, asc = 21, ascq =  0
>end_request: I/O error, dev 16:01 (hdc), sector 0
> hdc: hdc1 hdc2 hdc3 hdc4
>ide-floppy: hdc: I/O error, pc = 28, key =  5, asc = 21, ascq =  0
>end_request: I/O error, dev 16:02 (hdc), sector 0
> hdc: hdc1 hdc2 hdc3 hdc4
>ide-floppy: hdc: I/O error, pc = 28, key =  5, asc = 21, ascq =  0
>end_request: I/O error, dev 16:03 (hdc), sector 0
> hdc: hdc1 hdc2 hdc3 hdc4
>ide-floppy: hdc: I/O error, pc = 28, key =  5, asc = 21, ascq =  0
>end_request: I/O error, dev 16:04 (hdc), sector 0
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6005: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6006: writing inode 17393 on readonly FS
>clm-6005: writing inode 17393 on readonly FS
>SCSI subsystem driver Revision: 1.00
>scsi0 : SCSI host adapter emulation for IDE ATAPI devices
>  Vendor: TOSHIBA   Model: DVD-ROM SD-R2002  Rev: 1D26
>  Type:   CD-ROM                             ANSI SCSI revision: 02
>md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
>Linux Kernel Card Services 3.1.22
>  options:  [pci] [cardbus] [pm]
>PCI: Found IRQ 11 for device 02:0f.0
>PCI: Sharing IRQ 11 with 00:1f.2
>PCI: Sharing IRQ 11 with 02:0f.1
>PCI: Sharing IRQ 11 with 02:0f.2
>PCI: Found IRQ 11 for device 02:0f.1
>PCI: Sharing IRQ 11 with 00:1f.2
>PCI: Sharing IRQ 11 with 02:0f.0
>PCI: Sharing IRQ 11 with 02:0f.2
>Yenta IRQ list 06d8, PCI irq11
>Socket status: 30000006
>Yenta IRQ list 06d8, PCI irq11
>Socket status: 30000006
>cs: IO port probe 0x0c00-0x0cff: clean.
>cs: IO port probe 0x0100-0x04ff: excluding 0x280-0x287 0x378-0x37f 0x4d0-0x4d7
>cs: IO port probe 0x0a00-0x0aff: clean.
>eepro100.c:v1.09j-t 9/29/99 Donald Becker http://cesdis.gsfc.nasa.gov/linux/drivers/eepro100.html
>eepro100.c: $Revision: 1.36 $ 2000/11/17 Modified by Andrey V. Savochkin <saw@saw.sw.com.sg> and others
>eth0: OEM i82557/i82558 10/100 Ethernet, 00:20:E0:66:C5:8A, I/O at 0xecc0, IRQ 11.
>  Receiver lock-up bug exists -- enabling work-around.
>  Board assembly 727095-002, Physical connectors present: RJ45
>  Primary interface chip i82555 PHY #1.
>  General self-test: passed.
>  Serial sub-system self-test: passed.
>  Internal registers self-test: passed.
>  ROM checksum self-test: passed (0x04f4518b).
>  Receiver lock-up workaround activated.
>Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
>Winbond Super-IO detection, now testing ports 3F0,370,250,4E,2E ...
>SMSC Super-IO detection, now testing Ports 2F0, 370 ...
>PnPBIOS: Parport found PNPBIOS PNP0401 at io=0378,0778 irq=7 dma=1
>0x378: FIFO is 16 bytes
>0x378: writeIntrThreshold is 8
>0x378: readIntrThreshold is 8
>0x378: PWord is 8 bits
>0x378: Interrupts are ISA-Pulses
>0x378: ECP port cfgA=0x10 cfgB=0x00
>0x378: ECP settings irq=<none or set by other means> dma=<none or set by other means>
>parport0: PC-style at 0x378 (0x778), irq 7, dma 1 [PCSPP,TRISTATE,COMPAT,ECP,DMA]
>parport0: cpp_daisy: aa5500ff(38)
>parport0: assign_addrs: aa5500ff(38)
>parport0: cpp_daisy: aa5500ff(38)
>parport0: assign_addrs: aa5500ff(38)
>lp0: using parport0 (interrupt-driven).
>
>
>
>Very Respectfully,
>
>Stuart Blake Tener, IT3, USNR-R, N3GWG
>Beverly Hills, California
>VTU 1904G (Volunteer Training Unit)
>stuart@bh90210.net
>west coast: (310)-358-0202 P.O. Box 16043, Beverly Hills, CA 90209-2043
>east coast: (215)-338-6005 P.O. Box 45859, Philadelphia, PA 19149-5859
>
>Telecopier: (419)-715-6073 fax to email gateway via www.efax.com (it's free!)
>
>JOIN THE US NAVY RESERVE, SERVE YOUR COUNTRY, AND BENEFIT FROM IT ALL.
>
>Wednesday, September 12, 2001 7:00 PM
>
>-----Original Message-----
>From: Jason Edgecombe [mailto:jedgecombe@carolina.rr.com]
>Sent: Wednesday, September 12, 2001 6:02 PM
>To: stuart@bh90210.net
>Cc: linux-lvm@sistina.com
>Subject: Re: [linux-lvm] LVM
>
>hi,
>
>  according to reiserfs's FAQ:
>http://www.reiserfs.org/faq.html#ReiserFS-as-root
>
>you need the notail option on the /boot partition.
>the fstab might look as follows:
>/dev/hda1    /boot   reiserfs    defaults,notail  0 0
>/dev/hda2    /   reiserfs    defaults  0 0
>
>if there isn't the word "notail" in the fourth column of your root fstab
>entry, then you ARE booting with tails.
>
>according the lilo changelog:
>ftp://brun.dyndns.org/pub/linux/lilo/CHANGES
>
>lilo has been able to boot from a reiserfs partition with tail support
>since version 21.6 (Oct. 1, 2000)
>
>*under an rpm-based distro such as redhat or mandrake, "rpm -qi lilo"
>should give you the version. (assuming you haven't downloaded lilo as a
>tarball and compiled it.)
>
>Both were last modified in August 2001, I don't know which to believe.
>For safety sake, I made my /boot ext2. Most recent computers (within the
>past two years) can boot from a partition after the 1024 boundary. I
>just like to make a separate /boot at the beginning of the drive as a
>precaution.
>
>as for the matter of initrd's, this is the way that I understand it:
>in a non-lvm root fs, your root fs type must either be compiled in or in
>the initrd image.
>in a lvm root, you MUST have an initrd even if lvm is compiled into the
>kernel (not as a module) because you need to run a vgchange -ay and you
>need your lvm config files in the initrd.
>
>as for having /boot (booting the kernel) straight in an lvm fs, I have
>no idea.
>
>
>If I am wrong, someone please correct me.
>
>Sincerely,
>Jason Edgecombe
>
>"IT3 Stuart B. Tener, USNR-R" wrote:
>
>>        I am curious what version of lilo in fact supports ReiserFS tails. I am running Mandrake 8.0, and using the lilo supplied therewith, and have been booting a / partition as ReiserFS (with tails I believe, how do I check?).
>>



_______________________________________________
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

Re: [linux-lvm] LVM

[svetljo]

IT3 Stuart B. Tener, USNR-R wrote:

>Svetljo:
>
>	I did try ramdisk_size = 8192, perhaps 17,000 is the number to try. Some people told me the parameter was "ramdisk = 8192", you say "ramdisk_size = 8192", do you know which is accurate?
>
>	Also does it go in the append = "ramdisk_size=8192" or "ramdisk=8192"
>	Or is it placed into the lilo.conf as a separate entry underneath the append command (or other lilo entry) ramdisk = 8192
>
well lilo.conf has for each linux entry an append section
thats a part from my
###########################################################
image=/boot/vmlinuz-2.4.10-pre4
    label=2.4.10pre4lvm
    root=/dev/md0
    initrd=/boot/initrd-lvm-2.4.10-pre4-xfs.gz
    append="idebus=66 ramdisk_size=18000 hdd=ide-scsi hdb=ide-floppy"
    vga=788
    read-only
###########################################################
in the lvm how-to it's 8192
but i use 18000 because i use XFS and in the readme for mkinitrd.xfs is 
mentioned 15000
and i had the same problem, upon boot i was seeing a message
trieng to access beyound the end of the ramdisk
it was in your boot log
i think it was 17000 and smth
try it with a bit larger

you can ad it to lilo.conf and rerun lilo or you can tell it on boot prompt
in my case :
lilo: 2.4.10pre4lvm ramdisk_size=18000

>
>Very Respectfully, 
>
>Stuart Blake Tener, IT3, USNR-R, N3GWG 
>Beverly Hills, California
>VTU 1904G (Volunteer Training Unit) 
>stuart@bh90210.net 
>west coast: (310)-358-0202 P.O. Box 16043, Beverly Hills, CA 90209-2043 
>east coast: (215)-338-6005 P.O. Box 45859, Philadelphia, PA 19149-5859 
>
>Telecopier: (419)-715-6073 fax to email gateway via www.efax.com (it's free!) 
>
>JOIN THE US NAVY RESERVE, SERVE YOUR COUNTRY, AND BENEFIT FROM IT ALL. 
>
>Thursday, September 13, 2001 2:36 AM
>
>-----Original Message-----
>From: linux-lvm-admin@sistina.com [mailto:linux-lvm-admin@sistina.com]On Behalf Of svetljo
>Sent: Thursday, September 13, 2001 12:32 AM
>To: linux-lvm@sistina.com
>Subject: Re: [linux-lvm] LVM
>
>
>Hi
>
>have you tried to pass to lilo : linux ramdisk_size=8192 or
>ramdisk_size=17000
>after the lvm How-to you have to have in lilo.conf in the append section
>" ramdisk_size=8192 "
>
>>NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
>>RAMDISK: Compressed image found at block 0
>>Uncompressing.................................................................................................................................................................................................................................................................................done.
>>Freeing initrd memory: 869k freed
>>VFS: Mounted root (ext2 filesystem).
>>attempt to access beyond end of device
>>01:00: rw=0, want=8198 x(=0x), limit=8198
>>EXT2-fs error (device ramdisk(1,0)): ext2_read_inode: unable to read inode block - inode=8199, block=8197
>>attempt to access beyond end of device
>>01:00: rw=0, want=16390 x(=0x), limit=16390
>>EXT2-fs error (device ramdisk(1,0)): ext2_read_inode: unable to read inode block - inode=16387, block=16389
>>attempt to access beyond end of device
>>01:00: rw=0, want=8198 x(=0x), limit=8198
>>EXT2-fs error (device ramdisk(1,0)): ext2_read_inode: unable to read inode block - inode=8194, block=8197
>>reiserfs: checking transaction log (device 03:01) ...
>>Using r5 hash to sort names
>>ReiserFS version 3.6.25
>>VFS: Mounted root (reiserfs filesystem) readonly.
>>change_root: old root has d_count=2
>>Trying to unmount old root ... okay
>>Freeing unused kernel memory: 216k freed
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17519 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17519 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>LVM version 0.9.1_beta3  by Heinz Mauelshagen  (25/01/2001)
>>lvm -- Module successfully initialized
>>clm-6005: writing inode 17393 on readonly FS
>>clm-6005: writing inode 17519 on readonly FS
>>hdc: hdc1 hdc2 hdc3 hdc4
>>hdc: hdc1 hdc2 hdc3 hdc4
>>ide-floppy: hdc: I/O error, pc = 28, key =  5, asc = 21, ascq =  0
>>end_request: I/O error, dev 16:01 (hdc), sector 0
>>hdc: hdc1 hdc2 hdc3 hdc4
>>ide-floppy: hdc: I/O error, pc = 28, key =  5, asc = 21, ascq =  0
>>end_request: I/O error, dev 16:02 (hdc), sector 0
>>hdc: hdc1 hdc2 hdc3 hdc4
>>ide-floppy: hdc: I/O error, pc = 28, key =  5, asc = 21, ascq =  0
>>end_request: I/O error, dev 16:03 (hdc), sector 0
>>hdc: hdc1 hdc2 hdc3 hdc4
>>ide-floppy: hdc: I/O error, pc = 28, key =  5, asc = 21, ascq =  0
>>end_request: I/O error, dev 16:04 (hdc), sector 0
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6005: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6005: writing inode 17393 on readonly FS
>>SCSI subsystem driver Revision: 1.00
>>scsi0 : SCSI host adapter emulation for IDE ATAPI devices
>> Vendor: TOSHIBA   Model: DVD-ROM SD-R2002  Rev: 1D26
>> Type:   CD-ROM                             ANSI SCSI revision: 02
>>md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
>>Linux Kernel Card Services 3.1.22
>> options:  [pci] [cardbus] [pm]
>>PCI: Found IRQ 11 for device 02:0f.0
>>PCI: Sharing IRQ 11 with 00:1f.2
>>PCI: Sharing IRQ 11 with 02:0f.1
>>PCI: Sharing IRQ 11 with 02:0f.2
>>PCI: Found IRQ 11 for device 02:0f.1
>>PCI: Sharing IRQ 11 with 00:1f.2
>>PCI: Sharing IRQ 11 with 02:0f.0
>>PCI: Sharing IRQ 11 with 02:0f.2
>>Yenta IRQ list 06d8, PCI irq11
>>Socket status: 30000006
>>Yenta IRQ list 06d8, PCI irq11
>>Socket status: 30000006
>>cs: IO port probe 0x0c00-0x0cff: clean.
>>cs: IO port probe 0x0100-0x04ff: excluding 0x280-0x287 0x378-0x37f 0x4d0-0x4d7
>>cs: IO port probe 0x0a00-0x0aff: clean.
>>eepro100.c:v1.09j-t 9/29/99 Donald Becker http://cesdis.gsfc.nasa.gov/linux/drivers/eepro100.html
>>eepro100.c: $Revision: 1.36 $ 2000/11/17 Modified by Andrey V. Savochkin <saw@saw.sw.com.sg> and others
>>eth0: OEM i82557/i82558 10/100 Ethernet, 00:20:E0:66:C5:8A, I/O at 0xecc0, IRQ 11.
>> Receiver lock-up bug exists -- enabling work-around.
>> Board assembly 727095-002, Physical connectors present: RJ45
>> Primary interface chip i82555 PHY #1.
>> General self-test: passed.
>> Serial sub-system self-test: passed.
>> Internal registers self-test: passed.
>> ROM checksum self-test: passed (0x04f4518b).
>> Receiver lock-up workaround activated.
>>Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
>>Winbond Super-IO detection, now testing ports 3F0,370,250,4E,2E ...
>>SMSC Super-IO detection, now testing Ports 2F0, 370 ...
>>PnPBIOS: Parport found PNPBIOS PNP0401 at io=0378,0778 irq=7 dma=1
>>0x378: FIFO is 16 bytes
>>0x378: writeIntrThreshold is 8
>>0x378: readIntrThreshold is 8
>>0x378: PWord is 8 bits
>>0x378: Interrupts are ISA-Pulses
>>0x378: ECP port cfgA=0x10 cfgB=0x00
>>0x378: ECP settings irq=<none or set by other means> dma=<none or set by other means>
>>parport0: PC-style at 0x378 (0x778), irq 7, dma 1 [PCSPP,TRISTATE,COMPAT,ECP,DMA]
>>parport0: cpp_daisy: aa5500ff(38)
>>parport0: assign_addrs: aa5500ff(38)
>>parport0: cpp_daisy: aa5500ff(38)
>>parport0: assign_addrs: aa5500ff(38)
>>lp0: using parport0 (interrupt-driven).
>>
>>
>>
>>Very Respectfully,
>>
>>Stuart Blake Tener, IT3, USNR-R, N3GWG
>>Beverly Hills, California
>>VTU 1904G (Volunteer Training Unit)
>>stuart@bh90210.net
>>west coast: (310)-358-0202 P.O. Box 16043, Beverly Hills, CA 90209-2043
>>east coast: (215)-338-6005 P.O. Box 45859, Philadelphia, PA 19149-5859
>>
>>Telecopier: (419)-715-6073 fax to email gateway via www.efax.com (it's free!)
>>
>>JOIN THE US NAVY RESERVE, SERVE YOUR COUNTRY, AND BENEFIT FROM IT ALL.
>>
>>Wednesday, September 12, 2001 7:00 PM
>>
>>-----Original Message-----
>>From: Jason Edgecombe [mailto:jedgecombe@carolina.rr.com]
>>Sent: Wednesday, September 12, 2001 6:02 PM
>>To: stuart@bh90210.net
>>Cc: linux-lvm@sistina.com
>>Subject: Re: [linux-lvm] LVM
>>
>>hi,
>>
>> according to reiserfs's FAQ:
>>http://www.reiserfs.org/faq.html#ReiserFS-as-root
>>
>>you need the notail option on the /boot partition.
>>the fstab might look as follows:
>>/dev/hda1    /boot   reiserfs    defaults,notail  0 0
>>/dev/hda2    /   reiserfs    defaults  0 0
>>
>>if there isn't the word "notail" in the fourth column of your root fstab
>>entry, then you ARE booting with tails.
>>
>>according the lilo changelog:
>>ftp://brun.dyndns.org/pub/linux/lilo/CHANGES
>>
>>lilo has been able to boot from a reiserfs partition with tail support
>>since version 21.6 (Oct. 1, 2000)
>>
>>*under an rpm-based distro such as redhat or mandrake, "rpm -qi lilo"
>>should give you the version. (assuming you haven't downloaded lilo as a
>>tarball and compiled it.)
>>
>>Both were last modified in August 2001, I don't know which to believe.
>>For safety sake, I made my /boot ext2. Most recent computers (within the
>>past two years) can boot from a partition after the 1024 boundary. I
>>just like to make a separate /boot at the beginning of the drive as a
>>precaution.
>>
>>as for the matter of initrd's, this is the way that I understand it:
>>in a non-lvm root fs, your root fs type must either be compiled in or in
>>the initrd image.
>>in a lvm root, you MUST have an initrd even if lvm is compiled into the
>>kernel (not as a module) because you need to run a vgchange -ay and you
>>need your lvm config files in the initrd.
>>
>>as for having /boot (booting the kernel) straight in an lvm fs, I have
>>no idea.
>>
>>
>>If I am wrong, someone please correct me.
>>
>>Sincerely,
>>Jason Edgecombe
>>
>>"IT3 Stuart B. Tener, USNR-R" wrote:
>>
>>>       I am curious what version of lilo in fact supports ReiserFS tails. I am running Mandrake 8.0, and using the lilo supplied therewith, and have been booting a / partition as ReiserFS (with tails I believe, how do I check?).
>>>
>
>
>
>_______________________________________________
>linux-lvm mailing list
>linux-lvm@sistina.com
>http://lists.sistina.com/mailman/listinfo/linux-lvm
>

RE: [linux-lvm] LVM

[IT3 Stuart B. Tener, USNR-R]

Svetljo:

	Thank you again. I will also make sure my /etc/lilo.conf is configured appropriately as you indicate herein below.


Very Respectfully, 

Stuart Blake Tener, IT3, USNR-R, N3GWG 
Beverly Hills, California
VTU 1904G (Volunteer Training Unit) 
stuart@bh90210.net 
west coast: (310)-358-0202 P.O. Box 16043, Beverly Hills, CA 90209-2043 
east coast: (215)-338-6005 P.O. Box 45859, Philadelphia, PA 19149-5859 

Telecopier: (419)-715-6073 fax to email gateway via www.efax.com (it's free!) 

JOIN THE US NAVY RESERVE, SERVE YOUR COUNTRY, AND BENEFIT FROM IT ALL. 

Thursday, September 13, 2001 9:42 AM

-----Original Message-----
From: linux-lvm-admin@sistina.com [mailto:linux-lvm-admin@sistina.com]On Behalf Of svetljo
Sent: Thursday, September 13, 2001 6:32 AM
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] LVM


IT3 Stuart B. Tener, USNR-R wrote:

>Svetljo:
>
>       I did try ramdisk_size = 8192, perhaps 17,000 is the number to try. Some people told me the parameter was "ramdisk = 8192", you say "ramdisk_size = 8192", do you know which is accurate?
>
>       Also does it go in the append = "ramdisk_size=8192" or "ramdisk=8192"
>       Or is it placed into the lilo.conf as a separate entry underneath the append command (or other lilo entry) ramdisk = 8192
>
well lilo.conf has for each linux entry an append section
thats a part from my
###########################################################
image=/boot/vmlinuz-2.4.10-pre4
    label=2.4.10pre4lvm
    root=/dev/md0
    initrd=/boot/initrd-lvm-2.4.10-pre4-xfs.gz
    append="idebus=66 ramdisk_size=18000 hdd=ide-scsi hdb=ide-floppy"
    vga=788
    read-only
###########################################################
in the lvm how-to it's 8192
but i use 18000 because i use XFS and in the readme for mkinitrd.xfs is
mentioned 15000
and i had the same problem, upon boot i was seeing a message
trieng to access beyound the end of the ramdisk
it was in your boot log
i think it was 17000 and smth
try it with a bit larger

you can ad it to lilo.conf and rerun lilo or you can tell it on boot prompt
in my case :
lilo: 2.4.10pre4lvm ramdisk_size=18000

>
>Very Respectfully,
>
>Stuart Blake Tener, IT3, USNR-R, N3GWG
>Beverly Hills, California
>VTU 1904G (Volunteer Training Unit)
>stuart@bh90210.net
>west coast: (310)-358-0202 P.O. Box 16043, Beverly Hills, CA 90209-2043
>east coast: (215)-338-6005 P.O. Box 45859, Philadelphia, PA 19149-5859
>
>Telecopier: (419)-715-6073 fax to email gateway via www.efax.com (it's free!)
>
>JOIN THE US NAVY RESERVE, SERVE YOUR COUNTRY, AND BENEFIT FROM IT ALL.
>
>Thursday, September 13, 2001 2:36 AM
>
>-----Original Message-----
>From: linux-lvm-admin@sistina.com [mailto:linux-lvm-admin@sistina.com]On Behalf Of svetljo
>Sent: Thursday, September 13, 2001 12:32 AM
>To: linux-lvm@sistina.com
>Subject: Re: [linux-lvm] LVM
>
>
>Hi
>
>have you tried to pass to lilo : linux ramdisk_size=8192 or
>ramdisk_size=17000
>after the lvm How-to you have to have in lilo.conf in the append section
>" ramdisk_size=8192 "
>
>>NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
>>RAMDISK: Compressed image found at block 0
>>Uncompressing.................................................................................................................................................................................................................................................................................done.
>>Freeing initrd memory: 869k freed
>>VFS: Mounted root (ext2 filesystem).
>>attempt to access beyond end of device
>>01:00: rw=0, want=8198 x(=0x), limit=8198
>>EXT2-fs error (device ramdisk(1,0)): ext2_read_inode: unable to read inode block - inode=8199, block=8197
>>attempt to access beyond end of device
>>01:00: rw=0, want=16390 x(=0x), limit=16390
>>EXT2-fs error (device ramdisk(1,0)): ext2_read_inode: unable to read inode block - inode=16387, block=16389
>>attempt to access beyond end of device
>>01:00: rw=0, want=8198 x(=0x), limit=8198
>>EXT2-fs error (device ramdisk(1,0)): ext2_read_inode: unable to read inode block - inode=8194, block=8197
>>reiserfs: checking transaction log (device 03:01) ...
>>Using r5 hash to sort names
>>ReiserFS version 3.6.25
>>VFS: Mounted root (reiserfs filesystem) readonly.
>>change_root: old root has d_count=2
>>Trying to unmount old root ... okay
>>Freeing unused kernel memory: 216k freed
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17519 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17519 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>LVM version 0.9.1_beta3  by Heinz Mauelshagen  (25/01/2001)
>>lvm -- Module successfully initialized
>>clm-6005: writing inode 17393 on readonly FS
>>clm-6005: writing inode 17519 on readonly FS
>>hdc: hdc1 hdc2 hdc3 hdc4
>>hdc: hdc1 hdc2 hdc3 hdc4
>>ide-floppy: hdc: I/O error, pc = 28, key =  5, asc = 21, ascq =  0
>>end_request: I/O error, dev 16:01 (hdc), sector 0
>>hdc: hdc1 hdc2 hdc3 hdc4
>>ide-floppy: hdc: I/O error, pc = 28, key =  5, asc = 21, ascq =  0
>>end_request: I/O error, dev 16:02 (hdc), sector 0
>>hdc: hdc1 hdc2 hdc3 hdc4
>>ide-floppy: hdc: I/O error, pc = 28, key =  5, asc = 21, ascq =  0
>>end_request: I/O error, dev 16:03 (hdc), sector 0
>>hdc: hdc1 hdc2 hdc3 hdc4
>>ide-floppy: hdc: I/O error, pc = 28, key =  5, asc = 21, ascq =  0
>>end_request: I/O error, dev 16:04 (hdc), sector 0
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6005: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6006: writing inode 17393 on readonly FS
>>clm-6005: writing inode 17393 on readonly FS
>>SCSI subsystem driver Revision: 1.00
>>scsi0 : SCSI host adapter emulation for IDE ATAPI devices
>> Vendor: TOSHIBA   Model: DVD-ROM SD-R2002  Rev: 1D26
>> Type:   CD-ROM                             ANSI SCSI revision: 02
>>md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
>>Linux Kernel Card Services 3.1.22
>> options:  [pci] [cardbus] [pm]
>>PCI: Found IRQ 11 for device 02:0f.0
>>PCI: Sharing IRQ 11 with 00:1f.2
>>PCI: Sharing IRQ 11 with 02:0f.1
>>PCI: Sharing IRQ 11 with 02:0f.2
>>PCI: Found IRQ 11 for device 02:0f.1
>>PCI: Sharing IRQ 11 with 00:1f.2
>>PCI: Sharing IRQ 11 with 02:0f.0
>>PCI: Sharing IRQ 11 with 02:0f.2
>>Yenta IRQ list 06d8, PCI irq11
>>Socket status: 30000006
>>Yenta IRQ list 06d8, PCI irq11
>>Socket status: 30000006
>>cs: IO port probe 0x0c00-0x0cff: clean.
>>cs: IO port probe 0x0100-0x04ff: excluding 0x280-0x287 0x378-0x37f 0x4d0-0x4d7
>>cs: IO port probe 0x0a00-0x0aff: clean.
>>eepro100.c:v1.09j-t 9/29/99 Donald Becker http://cesdis.gsfc.nasa.gov/linux/drivers/eepro100.html
>>eepro100.c: $Revision: 1.36 $ 2000/11/17 Modified by Andrey V. Savochkin <saw@saw.sw.com.sg> and others
>>eth0: OEM i82557/i82558 10/100 Ethernet, 00:20:E0:66:C5:8A, I/O at 0xecc0, IRQ 11.
>> Receiver lock-up bug exists -- enabling work-around.
>> Board assembly 727095-002, Physical connectors present: RJ45
>> Primary interface chip i82555 PHY #1.
>> General self-test: passed.
>> Serial sub-system self-test: passed.
>> Internal registers self-test: passed.
>> ROM checksum self-test: passed (0x04f4518b).
>> Receiver lock-up workaround activated.
>>Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
>>Winbond Super-IO detection, now testing ports 3F0,370,250,4E,2E ...
>>SMSC Super-IO detection, now testing Ports 2F0, 370 ...
>>PnPBIOS: Parport found PNPBIOS PNP0401 at io=0378,0778 irq=7 dma=1
>>0x378: FIFO is 16 bytes
>>0x378: writeIntrThreshold is 8
>>0x378: readIntrThreshold is 8
>>0x378: PWord is 8 bits
>>0x378: Interrupts are ISA-Pulses
>>0x378: ECP port cfgA=0x10 cfgB=0x00
>>0x378: ECP settings irq=<none or set by other means> dma=<none or set by other means>
>>parport0: PC-style at 0x378 (0x778), irq 7, dma 1 [PCSPP,TRISTATE,COMPAT,ECP,DMA]
>>parport0: cpp_daisy: aa5500ff(38)
>>parport0: assign_addrs: aa5500ff(38)
>>parport0: cpp_daisy: aa5500ff(38)
>>parport0: assign_addrs: aa5500ff(38)
>>lp0: using parport0 (interrupt-driven).
>>
>>
>>
>>Very Respectfully,
>>
>>Stuart Blake Tener, IT3, USNR-R, N3GWG
>>Beverly Hills, California
>>VTU 1904G (Volunteer Training Unit)
>>stuart@bh90210.net
>>west coast: (310)-358-0202 P.O. Box 16043, Beverly Hills, CA 90209-2043
>>east coast: (215)-338-6005 P.O. Box 45859, Philadelphia, PA 19149-5859
>>
>>Telecopier: (419)-715-6073 fax to email gateway via www.efax.com (it's free!)
>>
>>JOIN THE US NAVY RESERVE, SERVE YOUR COUNTRY, AND BENEFIT FROM IT ALL.
>>
>>Wednesday, September 12, 2001 7:00 PM
>>
>>-----Original Message-----
>>From: Jason Edgecombe [mailto:jedgecombe@carolina.rr.com]
>>Sent: Wednesday, September 12, 2001 6:02 PM
>>To: stuart@bh90210.net
>>Cc: linux-lvm@sistina.com
>>Subject: Re: [linux-lvm] LVM
>>
>>hi,
>>
>> according to reiserfs's FAQ:
>>http://www.reiserfs.org/faq.html#ReiserFS-as-root
>>
>>you need the notail option on the /boot partition.
>>the fstab might look as follows:
>>/dev/hda1    /boot   reiserfs    defaults,notail  0 0
>>/dev/hda2    /   reiserfs    defaults  0 0
>>
>>if there isn't the word "notail" in the fourth column of your root fstab
>>entry, then you ARE booting with tails.
>>
>>according the lilo changelog:
>>ftp://brun.dyndns.org/pub/linux/lilo/CHANGES
>>
>>lilo has been able to boot from a reiserfs partition with tail support
>>since version 21.6 (Oct. 1, 2000)
>>
>>*under an rpm-based distro such as redhat or mandrake, "rpm -qi lilo"
>>should give you the version. (assuming you haven't downloaded lilo as a
>>tarball and compiled it.)
>>
>>Both were last modified in August 2001, I don't know which to believe.
>>For safety sake, I made my /boot ext2. Most recent computers (within the
>>past two years) can boot from a partition after the 1024 boundary. I
>>just like to make a separate /boot at the beginning of the drive as a
>>precaution.
>>
>>as for the matter of initrd's, this is the way that I understand it:
>>in a non-lvm root fs, your root fs type must either be compiled in or in
>>the initrd image.
>>in a lvm root, you MUST have an initrd even if lvm is compiled into the
>>kernel (not as a module) because you need to run a vgchange -ay and you
>>need your lvm config files in the initrd.
>>
>>as for having /boot (booting the kernel) straight in an lvm fs, I have
>>no idea.
>>
>>
>>If I am wrong, someone please correct me.
>>
>>Sincerely,
>>Jason Edgecombe
>>
>>"IT3 Stuart B. Tener, USNR-R" wrote:
>>
>>>       I am curious what version of lilo in fact supports ReiserFS tails. I am running Mandrake 8.0, and using the lilo supplied therewith, and have been booting a / partition as ReiserFS (with tails I believe, how do I check?).
>>>
>
>
>
>_______________________________________________
>linux-lvm mailing list
>linux-lvm@sistina.com
>http://lists.sistina.com/mailman/listinfo/linux-lvm
>



_______________________________________________
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

RE: [linux-lvm] LVM

[IT3 Stuart B. Tener, USNR-R]

Mr. Edgecombe:

Prior to using LVM, it did not matter that my single Linux partition (the root "/") was located beyond the 1024 cylinder. Why does LVM move me backwards in making it requisite to again have this limitation present? Perhaps I ought to wait until LVM becomes more mature then.


Very Respectfully, 

Stuart Blake Tener, IT3, USNR-R, N3GWG 
Beverly Hills, California
VTU 1904G (Volunteer Training Unit) 
stuart@bh90210.net 
west coast: (310)-358-0202 P.O. Box 16043, Beverly Hills, CA 90209-2043 
east coast: (215)-338-6005 P.O. Box 45859, Philadelphia, PA 19149-5859 

Telecopier: (419)-715-6073 fax to email gateway via www.efax.com (it's free!) 

JOIN THE US NAVY RESERVE, SERVE YOUR COUNTRY, AND BENEFIT FROM IT ALL. 

Wednesday, September 12, 2001 3:43 PM

-----Original Message-----
From: linux-lvm-admin@sistina.com [mailto:linux-lvm-admin@sistina.com]On Behalf Of Jason Edgecombe
Sent: Wednesday, September 12, 2001 6:45 AM
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] LVM

hi,

  I must ask what filesystem /boot is using. If you're using reiserfs,
then you MUST mount with the "notail" option for /boot. If you're using
ext2 of reiserfs with "notail" then I would recommend the you move /boot
to before the 1024th cylinder. (I like to always put /boot at the
beginning of the drive.)

Sincerely,
Jason Edgecombe


svetljo wrote:
>
> i should tell you about that
> that was the problem that i had when i tried with /boot behind the first
> 1024cyl of the first disk
> some people tells that the new lilo can handle this (it comes with MDK-8)
> some people tells that probably a BIOS update should solve the problem
> it didn't work for me
>
> you can try to update lilo to the latest beta version and to update the BIOS
> but with GRUB it works
> the problem is that LILO can not read from /boot
> my partitions
> /dev/hda1 470Mb win-boot
> extended
> /dev/hda5   32Mb /boot
> ......
>
> can you boot with a floppy and install grub?  it must work
> IT3 Stuart B. Tener, USNR-R wrote:
>
> >Svetjo:
> >
> >       /dev/hda1       w2k/pro
> >       /dev/hda2       /boot
> >       /dev/hda3       /
> >
> >       Something like the above?
> >
> >       Okay, I did that, and now I get "LI" when I booted up! What does "LI" in lilo mean? What part of my boot up sequence is broken?
> >
> >       Someone told me it meant my second stage boot loader was failing. What does that mean? What are the stages of booting? Can anyone hook me up here?
> >
> >       As far as I know, I have ReiserFS compiled into the kernel along with LVM support in the kernel.
> >
> >       I must admit ReiserFS has worked quite well for me, and is very bug-free. I am using the version that comes with the 2.4.8-12mdk (mandrake) kernel, so perhaps u tried an older version.
> >
> >
> >Very Respectfully,
> >
> >Stuart Blake Tener, IT3, USNR-R, N3GWG
> >Beverly Hills, California
> >VTU 1904G (Volunteer Training Unit)
> >stuart@bh90210.net
> >west coast: (310)-358-0202 P.O. Box 16043, Beverly Hills, CA 90209-2043
> >east coast: (215)-338-6005 P.O. Box 45859, Philadelphia, PA 19149-5859
> >
> >Telecopier: (419)-715-6073 fax to email gateway via www.efax.com (it's free!)
> >
> >JOIN THE US NAVY RESERVE, SERVE YOUR COUNTRY, AND BENEFIT FROM IT ALL.
> >
> >Wednesday, September 12, 2001 3:43 AM
> >
> >-----Original Message-----
> >From: linux-lvm-admin@sistina.com [mailto:linux-lvm-admin@sistina.com]On Behalf Of svetljo
> >Sent: Wednesday, September 12, 2001 2:59 AM
> >To: linux-lvm@sistina.com
> >Subject: Re: [linux-lvm] LVM
> >
> >Hi
> >you need a normal partition vor /boot not on LV and it would be good to
> >have also a normal partition as swap,
> >but in case you don't use swap you don't need to,
> >the thing is that the swap is much faster when it is on partition not file
> >you can try to do it without formating the second disk
> >you can shrink ReiserFS, then with diskdrake shrink the partition
> > and make a new one for boot and for the VG , make an LV on the VG ,
> >create filesystems on the LV and /boot, mount the LV /mnt/new-root ,
> >mkdir /mnt/new-root/boot and mount here the /boot partition
> >trasnfer your installation to /mnt/new-root:
> >cd /
> > find . -xdev | cpio -pm /mnt/new-root
> >
> >edit /mnt/new-root/etc/fstab to match the LV as / and ad an entry for /boot
> >
> >reboot
> >and pass to lilo root=/dev/[your VG]/[your / LV]
> >it should be working
> >
> >edit lilo.conf and reinstall lilo or grub ( i'm not shure that lilo can
> >boot from the end of 32Gb drive)
> >
> >reboot once more if everything is OK
> >you can make a PV from your old / and ad it to the VG
> >that should be it
> >
> >about the FS's
> >
> >smth important ( may be) as far i know only Reiserfs could be shrinked ,
> >you can only grow XFS and JFS you can not make them smaller
> >
> >i really like XFS,and not that much the others
> >i had some crashes and with reiserfs i have some file entries which are
> >reported to exist ,but they can not be stated when i try to delete them
> >or to see them
> >i have not much expiriance with JFS , but i'm hearing that it was not
> >that stable as of 1.0.3
> >and with XFS i found all lost files in " lost and find " and it was
> >pretty easy to bring them back
> >i mention only the journal ones becouse you are speaking about 32Gb
> >
> >
> >
> >
> >
> >
> >
> >IT3 Stuart B. Tener, USNR-R wrote:
> >
> >>LVM List members:
> >>
> >>      I have been doing some playing around and am not getting very far! Perhaps you can answer some questions and guide me.
> >>
> >>I have 2 32GB HDs, which I can have both in use on my laptop simultaneously. The 2nd HD I can erase to my hearts content. It's a staging drive.
> >>
> >>      My current configuration is:
> >>
> >>      /dev/hda1       windows 2000 pro
> >>      /dev/hda2       /       (Linux mandrake 8.0)
> >>
> >>      I do not have a swap partition at the moment (I have 512MB of ram, and I use a swap file if I need too), and have everything installed into the root (I know the drawbacks of this, but it made for simplicity at the time). I also use ReiserFS, and want to implement LVM.
> >>
> >>      The "How To" speaks of an example inclusive of a /boot partition and a swap partition. I ignored the swap partition, but was curious about the /boot partition in the how-to.
> >>
> >>a) Do I need to have a separate /boot partition, or can I create an LVM implementation (for the moment) with everything in the root (/)?
> >>b) The example seems to show the /boot being outside the LVM area, is that correct or does the how-to mean to show the /boot as being within the domain of the LVM controlled area?
> >>c) How will using ReiserFS on my root partition and LVM over the root affect what I need to do for an initrd and kernel compilation options?
> >>
> >>Once the LVM implementation is completed with everything in the / partition, and ReiserFS on the root, and it boots up, then I plan to break apart the / into separate filesystems within the LVM environment. At that point, recommendations of what filesystems to create will be helpful.
> >>
> >>
> >>Very Respectfully,
> >>
> >>Stuart Blake Tener, IT3, USNR-R, N3GWG
> >>Beverly Hills, California
> >>VTU 1904G (Volunteer Training Unit)
> >>stuart@bh90210.net
> >>west coast: (310)-358-0202 P.O. Box 16043, Beverly Hills, CA 90209-2043
> >>east coast: (215)-338-6005 P.O. Box 45859, Philadelphia, PA 19149-5859
> >>
> >>Telecopier: (419)-715-6073 fax to email gateway via www.efax.com (it's free!)
> >>
> >>JOIN THE US NAVY RESERVE, SERVE YOUR COUNTRY, AND BENEFIT FROM IT ALL.
> >>
> >>Wednesday, September 12, 2001 2:01 AM
> >>
> >>
> >
> >
> >
> >_______________________________________________
> >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
> >¥
> >
>
> _______________________________________________
> 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

_______________________________________________
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

Re: [linux-lvm] LVM

[Andreas Dilger]

On Sep 12, 2001  15:47 -0700, IT3 Stuart B. Tener, USNR-R wrote:
> Prior to using LVM, it did not matter that my single Linux partition
> (the root "/") was located beyond the 1024 cylinder. Why does LVM
> move me backwards in making it requisite to again have this limitation
> present? Perhaps I ought to wait until LVM becomes more mature then.

I doubt that this is necessary.  LILO doesn't understand anything but
BIOS-accessible disk blocks, whether it is LVM + ext2/ext3/reiserfs/other.
If you can use your partition beyond cylinder 1024 before, you can continue
to do so later.

That said, there are reasons for NOT putting all of your eggs in one
basket (e.g. LVM).  If there is any problem with LVM, you will not be
able to boot your system.  On my systems I have /boot in a regular
partition (about 70MB) which has my kernels/initrd in it, along with
enough tools from /bin and /sbin, and libs from /lib in order to have
a rescue boot partition in case of trouble.  Once I have tested the
booting from that partition, I don't touch it anymore (it has a
separate "rescue" kernel, modules, etc).

Cheers, Andreas
-- 
Andreas Dilger  \ "If a man ate a pound of pasta and a pound of antipasto,
                 \  would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/               -- Dogbert

RE: [linux-lvm] LVM

[IT3 Stuart B. Tener, USNR-R]

Dear Sir:

	This maybe true, however I plan to handle my disaster recovery scenario differently; I would much prefer to make my own rescue disc (which I did before ReiserFS was a standard part of the distributed kernel with Mandrake as part of its bootable rescue portion) which is inclusive of LVM.

	What I was trying to figure out was if it was NECESSARY to have a separate /boot partition or not. I am curious if there is a way to avoid a separate /boot partition by using either modules compiled into the kernel or otherwise. I presume from what you said it is not possible, and I am forced to have a separate /boot. I prefer to keep everything under the control of LVM. I also do two backups (via DD) of my entire hard disk, so I am not as concerned about not being able to boot. I have two separate drives I backup onto for just that purpose.


Very Respectfully, 

Stuart Blake Tener, IT3, USNR-R, N3GWG 
Beverly Hills, California
VTU 1904G (Volunteer Training Unit) 
stuart@bh90210.net 
west coast: (310)-358-0202 P.O. Box 16043, Beverly Hills, CA 90209-2043 
east coast: (215)-338-6005 P.O. Box 45859, Philadelphia, PA 19149-5859 

Telecopier: (419)-715-6073 fax to email gateway via www.efax.com (it's free!) 

JOIN THE US NAVY RESERVE, SERVE YOUR COUNTRY, AND BENEFIT FROM IT ALL. 

Wednesday, September 12, 2001 4:28 PM

-----Original Message-----
From: linux-lvm-admin@sistina.com [mailto:linux-lvm-admin@sistina.com]On Behalf Of Andreas Dilger
Sent: Wednesday, September 12, 2001 4:26 PM
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] LVM

On Sep 12, 2001  15:47 -0700, IT3 Stuart B. Tener, USNR-R wrote:
> Prior to using LVM, it did not matter that my single Linux partition
> (the root "/") was located beyond the 1024 cylinder. Why does LVM
> move me backwards in making it requisite to again have this limitation
> present? Perhaps I ought to wait until LVM becomes more mature then.

I doubt that this is necessary.  LILO doesn't understand anything but
BIOS-accessible disk blocks, whether it is LVM + ext2/ext3/reiserfs/other.
If you can use your partition beyond cylinder 1024 before, you can continue
to do so later.

That said, there are reasons for NOT putting all of your eggs in one
basket (e.g. LVM).  If there is any problem with LVM, you will not be
able to boot your system.  On my systems I have /boot in a regular
partition (about 70MB) which has my kernels/initrd in it, along with
enough tools from /bin and /sbin, and libs from /lib in order to have
a rescue boot partition in case of trouble.  Once I have tested the
booting from that partition, I don't touch it anymore (it has a
separate "rescue" kernel, modules, etc).

Cheers, Andreas
--
Andreas Dilger  \ "If a man ate a pound of pasta and a pound of antipasto,
                 \  would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/               -- Dogbert


_______________________________________________
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

RE: [linux-lvm] LVM

[IT3 Stuart B. Tener, USNR-R]

Dear Sir:

	The mandrake 8.0 version I am using has handled this from the time I installed it, but I got concerned when it got mentioned notwithstanding that fact, as new bugs always pop up. Perhaps I had missed something? It is very important to make sure you speak (or others) clearly in these forums, as you effect how people deal with their systems as a result.


Very Respectfully, 

Stuart Blake Tener, IT3, USNR-R, N3GWG 
Beverly Hills, California
VTU 1904G (Volunteer Training Unit) 
stuart@bh90210.net 
west coast: (310)-358-0202 P.O. Box 16043, Beverly Hills, CA 90209-2043 
east coast: (215)-338-6005 P.O. Box 45859, Philadelphia, PA 19149-5859 

Telecopier: (419)-715-6073 fax to email gateway via www.efax.com (it's free!) 

JOIN THE US NAVY RESERVE, SERVE YOUR COUNTRY, AND BENEFIT FROM IT ALL. 

Wednesday, September 12, 2001 4:34 PM

-----Original Message-----
From: linux-lvm-admin@sistina.com [mailto:linux-lvm-admin@sistina.com]On Behalf Of svetljo
Sent: Wednesday, September 12, 2001 4:48 AM
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] LVM

i should tell you about that
that was the problem that i had when i tried with /boot behind the first
1024cyl of the first disk
some people tells that the new lilo can handle this (it comes with MDK-8)
some people tells that probably a BIOS update should solve the problem
it didn't work for me

you can try to update lilo to the latest beta version and to update the BIOS
but with GRUB it works
the problem is that LILO can not read from /boot
my partitions
/dev/hda1 470Mb win-boot
extended
/dev/hda5   32Mb /boot
......

can you boot with a floppy and install grub?  it must work
IT3 Stuart B. Tener, USNR-R wrote:

>Svetjo:
>
>       /dev/hda1       w2k/pro
>       /dev/hda2       /boot
>       /dev/hda3       /
>
>       Something like the above?
>
>       Okay, I did that, and now I get "LI" when I booted up! What does "LI" in lilo mean? What part of my boot up sequence is broken?
>
>       Someone told me it meant my second stage boot loader was failing. What does that mean? What are the stages of booting? Can anyone hook me up here?
>
>       As far as I know, I have ReiserFS compiled into the kernel along with LVM support in the kernel.
>
>       I must admit ReiserFS has worked quite well for me, and is very bug-free. I am using the version that comes with the 2.4.8-12mdk (mandrake) kernel, so perhaps u tried an older version.
>
>
>Very Respectfully,
>
>Stuart Blake Tener, IT3, USNR-R, N3GWG
>Beverly Hills, California
>VTU 1904G (Volunteer Training Unit)
>stuart@bh90210.net
>west coast: (310)-358-0202 P.O. Box 16043, Beverly Hills, CA 90209-2043
>east coast: (215)-338-6005 P.O. Box 45859, Philadelphia, PA 19149-5859
>
>Telecopier: (419)-715-6073 fax to email gateway via www.efax.com (it's free!)
>
>JOIN THE US NAVY RESERVE, SERVE YOUR COUNTRY, AND BENEFIT FROM IT ALL.
>
>Wednesday, September 12, 2001 3:43 AM
>
>-----Original Message-----
>From: linux-lvm-admin@sistina.com [mailto:linux-lvm-admin@sistina.com]On Behalf Of svetljo
>Sent: Wednesday, September 12, 2001 2:59 AM
>To: linux-lvm@sistina.com
>Subject: Re: [linux-lvm] LVM
>
>Hi
>you need a normal partition vor /boot not on LV and it would be good to
>have also a normal partition as swap,
>but in case you don't use swap you don't need to,
>the thing is that the swap is much faster when it is on partition not file
>you can try to do it without formating the second disk
>you can shrink ReiserFS, then with diskdrake shrink the partition
> and make a new one for boot and for the VG , make an LV on the VG ,
>create filesystems on the LV and /boot, mount the LV /mnt/new-root ,
>mkdir /mnt/new-root/boot and mount here the /boot partition
>trasnfer your installation to /mnt/new-root:
>cd /
> find . -xdev | cpio -pm /mnt/new-root
>
>edit /mnt/new-root/etc/fstab to match the LV as / and ad an entry for /boot
>
>reboot
>and pass to lilo root=/dev/[your VG]/[your / LV]
>it should be working
>
>edit lilo.conf and reinstall lilo or grub ( i'm not shure that lilo can
>boot from the end of 32Gb drive)
>
>reboot once more if everything is OK
>you can make a PV from your old / and ad it to the VG
>that should be it
>
>about the FS's
>
>smth important ( may be) as far i know only Reiserfs could be shrinked ,
>you can only grow XFS and JFS you can not make them smaller
>
>i really like XFS,and not that much the others
>i had some crashes and with reiserfs i have some file entries which are
>reported to exist ,but they can not be stated when i try to delete them
>or to see them
>i have not much expiriance with JFS , but i'm hearing that it was not
>that stable as of 1.0.3
>and with XFS i found all lost files in " lost and find " and it was
>pretty easy to bring them back
>i mention only the journal ones becouse you are speaking about 32Gb
>
>
>
>
>
>
>
>IT3 Stuart B. Tener, USNR-R wrote:
>
>>LVM List members:
>>
>>      I have been doing some playing around and am not getting very far! Perhaps you can answer some questions and guide me.
>>
>>I have 2 32GB HDs, which I can have both in use on my laptop simultaneously. The 2nd HD I can erase to my hearts content. It's a staging drive.
>>
>>      My current configuration is:
>>
>>      /dev/hda1       windows 2000 pro
>>      /dev/hda2       /       (Linux mandrake 8.0)
>>
>>      I do not have a swap partition at the moment (I have 512MB of ram, and I use a swap file if I need too), and have everything installed into the root (I know the drawbacks of this, but it made for simplicity at the time). I also use ReiserFS, and want to implement LVM.
>>
>>      The "How To" speaks of an example inclusive of a /boot partition and a swap partition. I ignored the swap partition, but was curious about the /boot partition in the how-to.
>>
>>a) Do I need to have a separate /boot partition, or can I create an LVM implementation (for the moment) with everything in the root (/)?
>>b) The example seems to show the /boot being outside the LVM area, is that correct or does the how-to mean to show the /boot as being within the domain of the LVM controlled area?
>>c) How will using ReiserFS on my root partition and LVM over the root affect what I need to do for an initrd and kernel compilation options?
>>
>>Once the LVM implementation is completed with everything in the / partition, and ReiserFS on the root, and it boots up, then I plan to break apart the / into separate filesystems within the LVM environment. At that point, recommendations of what filesystems to create will be helpful.
>>
>>
>>Very Respectfully,
>>
>>Stuart Blake Tener, IT3, USNR-R, N3GWG
>>Beverly Hills, California
>>VTU 1904G (Volunteer Training Unit)
>>stuart@bh90210.net
>>west coast: (310)-358-0202 P.O. Box 16043, Beverly Hills, CA 90209-2043
>>east coast: (215)-338-6005 P.O. Box 45859, Philadelphia, PA 19149-5859
>>
>>Telecopier: (419)-715-6073 fax to email gateway via www.efax.com (it's free!)
>>
>>JOIN THE US NAVY RESERVE, SERVE YOUR COUNTRY, AND BENEFIT FROM IT ALL.
>>
>>Wednesday, September 12, 2001 2:01 AM
>>
>>
>
>
>
>_______________________________________________
>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
>¥
>



_______________________________________________
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