can't you make partition1 dasda1 /boot and partition2 dasda2 the PV for
LVM?


--------------------------------------------------------
This e-mail, including any attachments, may be confidential, privileged or 
otherwise legally protected. It is intended only for the addressee. If you 
received this e-mail in error or from someone who was not authorized to send it 
to you, do not disseminate, copy or otherwise use this e-mail or its 
attachments.  Please notify the sender immediately by reply e-mail and delete 
the e-mail from your system.


-----Original Message-----

From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Brad Hinson
Sent: Tuesday, April 08, 2008 10:06 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: What is a good generic disk layout?

Hi all,

Just a followup question (Mike and I are working together on this):

We're considering this layout due to some difficulty we had in the SLES
installer.  Ideally, we'd like a 3338 cylinder 100 disk with /boot (ext3
filesystem) and the remaining space used for an LVM volume, so 2
partitions total.  However, when we create the /boot ext3 partition, the
LVM button doesn't allow us to use dasda any longer for a Volume Group.
If we take off /boot, we can use dasda, but since /boot can't be on the
LVM this won't work either.  It's almost like once you put an ext3
filesystem on dasda, you can no longer use it for LVM.

Has anyone run into this situation before?  If so, is there a way to put
2 partitions (1 ext3, 1 LVM PV) on dasda during install?

Thanks,
-Brad

On Tue, 2008-04-08 at 09:44 -0400, Michael MacIsaac wrote:
> Hello list,
>
> It's difficult to come up with a one-size-fits-all disk layout for
Linux.
> In the past I've just "punted" and created a single 3390-3-sized root
file
> system. That often fills up quickly, so most would probably agree that
> more space is require.  Here is a proposed minidisk layout for two
> 3390-3s:
>
>    MDISK 100 3390 0001 0050 => for /boot => cannot boot from a logical
> volume
>    MDISK 101 3390 0051 0500 => for /     => in event that lv is hosed,
> system will not boot
>    MDISK 102 3390 0551 2788 => for LVM volume group => to break file
> systems out of the root
>    MDISK 103 3390 0001 3338 => for LVM volume group => to be able to
grow
> in other than / and /boot
>
> A volume group can then be carved into the following logical volumes
>
>    /usr   usr-lv  1.6GB => to allow for a fair number of packages
>    /var   var-lv  300MB
>    /opt   opt-lv  400MB => to allow for X and a graphical desktop
>    /srv   srv-lv   50MB
>    /home  home-lv  50MB => utilize central NFS-automounted space later
>    /tmp   tmp-lv  400MB => (or put it into a tmpfs?)
>    ???                  => any missing that could fill up?
>
> These LVs would leave the volume group with more than 1GB free for
growth.
>
> Comments on this proposal? Thanks.
>
> "Mike MacIsaac" <[EMAIL PROTECTED]>   (845) 433-7061
>
> ----------------------------------------------------------------------
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to [EMAIL PROTECTED] with the message: INFO LINUX-390
or visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
--
Brad Hinson <[EMAIL PROTECTED]>
Sr. Support Engineer Lead, System z
Red Hat, Inc.
(919) 754-4198

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or
visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Reply via email to