>>> On Tue, Apr 8, 2008 at 10:06 AM, in message
<[EMAIL PROTECTED]>, Brad Hinson
<[EMAIL PROTECTED]> wrote:
-snip-
> 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?
It's always worked fine for me. I just went through a new SP1 install on my
test system, just to make sure nothing had changed with SP1. I even tried it a
couple of ways:
/dev/dasda1 -> /boot
/dev/dasda2 -> PV for VG system
/dev/dasda1 -> /
/dev/dasda2 -> PV for VG system
Worked fine both ways. What, exactly, are you doing, and in what order? What
error messages are you seeing? Etc.
For all you folks out there that keep wanting to put / in an LV, all I can say
is "masochists." I keep /boot in the root file system, and break out
everything else.
# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/dasda1 388M 125M 243M 35% /
/dev/mapper/vg01-home
97M 4.2M 88M 5% /home
/dev/mapper/vg01-opt 74M 21M 50M 30% /opt
/dev/mapper/vg01-srv 100M 33M 67M 33% /srv
/dev/mapper/vg01-tmp 291M 33M 244M 12% /tmp
/dev/mapper/vg01-usr 1.2G 1022M 76M 94% /usr
/dev/mapper/vg01-var 245M 81M 152M 35% /var
Mark Post
----------------------------------------------------------------------
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
