Pat ...

Good point,  to be sure.  But I suspect that the pain you mention is
alleviated when

1 -- you run disks unpartitioned (note the trouble Mark reports),  and
2 -- you use FBA disks (either SAN or 9336 work-alikes) or enforce
reliable "low level formatting"

Of course,  both of those are suggestions which have perhaps "been slapped
down",  similar to your experience when endorsing LV root.   :-(

If a "disk" (as presented to Linux) can be expanded out from under Linux,
and there is no partition table to worry about,  then enlarging the FS
becomes no more difficult than that step of enlarging a logical volume.
The difference then becomes ... which thing is handling your volumes?
Linux or something else?  I guess I'm a VM bigot because I like for VM to
manage all volumes present to Linux.  This would be true for Linux on
VMware as well,  so it's not peculiar to the mainframe flavor of
virtualized Linux.

-- R;





Patrick Spinler <[EMAIL PROTECTED]>

Sent by: Linux on 390 Port <[email protected]>




05/10/2007 11:08 AM
Please respond to Linux on 390 Port <[email protected]>

From
Patrick Spinler <[EMAIL PROTECTED]>
To
[email protected]
cc

Subject
Re: Increase space within linux OS






-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


I hate to bring this up, since this opinion was slapped down before, but:

This is exactly why we run even our root in a LVM volume group.  It's
simply not true that you *never* need to resize root, here's someone
else who needed to, and is having a PITA doing it.

Ideally, of course, you want to be at suse9/redhat4 or above, so you
can do an ext2online filesystem expansion, without taking the system
down.  Otherwise, even with volume groups, you still have to drop into
single user mode.

- -- Pat

Mark Post wrote:
> It turns out there's one more thing you need to do before running
resize2fs (assuming you did use DDR or dd to do the copying of the whole
minidisk/device).  The partition table will still say it is the old size.
You'll need to use fdasd to re-create the VTOC and delete all partitions
(option r), create a new partition spanning the whole space, then write
the new partition table out to disk.  After that, resize2fs should work
(after the mandatory e2fsck -f command).
>
> Simply trying to delete the old partition and then add a new one didn't
work for me (but I'm running an older copy of s390-tools on the system
where I tested this).
>
> Mark Post
>
>>>> Mark Post 05/09/07 7:44 PM >>>
>>>> On Wed, May 9, 2007 at 11:49 AM, in message
<[EMAIL PROTECTED]>, Rich
> Smrcina <[EMAIL PROTECTED]> wrote:
>> How did you copy the root filesystem to a larger minidisk?
>>
>> Just using DDR won't work.
> -snip-
> It should if the system is down.  For example, add a minidisk to a
guest, take the guest down and IPL CMS, DDR the old to the new, bring back
up the guest.
>
>
> 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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGQzVrNObCqA8uBswRArhLAKCNaMTxKvK5LF8fKstuZr0gZc8DDACgghc5
dlZ7nvRhrygt+MurjE1mx5U=
=yh1I
-----END PGP SIGNATURE-----

----------------------------------------------------------------------
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




Attachment(s) have been removed by Richard Troth
spinler.patrick.vcf


----------------------------------------------------------------------
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