this process may still work for you:
http://www.redbooks.ibm.com/abstracts/redp3871.html
--
Jay Brenneman
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message:
All,
Being a zLinux Newbie I'm following Chapter 7. (installing and
configuring SLES10) in the 'z/VM and Linux on IBM System z The
Virtualization Cookbook'
Step 7.5.13 identifies modifications to make to the zipl.conf file.
Well... Here's where the problem lies... I fat fingered the
Has anyone ask Novell why YAST fails to grow a logical volume that has an ext3
filesystem on it?
I would, except we don't have support.
__
CONFIDENTIALITY NOTICE: This email from the State of
On Fri, 29 Aug 2008, Fargusson.Alan wrote:
Has anyone ask Novell why YAST fails to grow a logical volume that has
an ext3 filesystem on it?
I would, except we don't have support.
I don't either, but what error are you getting when you do the resize2fs
(or whatever it is you are using to
I am out of the office until 22-09-2008.
I have no access to my email. Contact Hans Wijngaard/Erik Bakker/Dick Jorna
for urgent matters,
Note: This is an automated response to your message Re: z/Linux cloning
sent on 29/8/08 19:35:04.
This is the only notification you will receive while this
On Aug 29, 2008, at 11:51 AM, Rakoczy, Dave wrote:
Can anyone offer any insight on how I can save this install without
starting all over again?
Boot from a rescue system, chroot to the new disk, edit, run zipl.
Adam
--
For
Dave,
See section 12.4 - Rescuing a Linux system.
Mike MacIsaac [EMAIL PROTECTED] (845) 433-7061
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO
Boot up your install system, and define the network. Get things up to the
point that ssh is started. Then log in via ssh, mount your real Linux
system's filesystem and once everything is in place beneath this mount
point, do a chroot to the mountpoint. Then edit your zipl.conf file, and
re-run
Works for me. Just did that a couple of days ago. With Yast. On SLES
10 SP 2. Volume still mounted too.
Marcy
This message may contain confidential and/or privileged information. If
you are not the addressee or authorized to receive this for the
addressee, you must not use, copy, disclose,
On 8/29/2008 at 2:54 PM, in message
[EMAIL PROTECTED],
Fargusson.Alan [EMAIL PROTECTED] wrote:
Has anyone ask Novell why YAST fails to grow a logical volume that has an
ext3 filesystem on it?
It should work just fine on systems that are at SLES10 SP2 or later, and the
file system itself
On 8/29/2008 at 3:01 PM, in message
[EMAIL PROTECTED], John McKown
[EMAIL PROTECTED] wrote:
On Fri, 29 Aug 2008, Fargusson.Alan wrote:
Has anyone ask Novell why YAST fails to grow a logical volume that has
an ext3 filesystem on it?
I would, except we don't have support.
I don't
How do you set the MTU so high? I'm trying to play with super jumbo
frames on a SLES10 guest under Z/VM and it doesnt appear to allow an
MTU value larger than 12256:
db1:~ # ifconfig hsi0 mtu 12257
SIOCSIFMTU: Invalid argument
db1:~ # ifconfig hsi0 mtu 12256
db1:~ # ifconfig hsi0 mtu 16384
If you have another zLinux guest running, you can link the disk from the DOA
image and repair your zipl.conf, chroot and run zipl.
Rakoczy, Dave [EMAIL PROTECTED] wrote:
All,
Being a zLinux Newbie I'm following Chapter 7. (installing and
configuring SLES10) in the 'z/VM and Linux on IBM
Cross-posted to ibm-main, ibmvm, and linux-390.
I've uploaded a whole boatload of Linux and z/VM-related presentations from
SHARE 111 in San Jose to the linuxvm.org website. (About 53 so far)
http://linuxvm.org/Present/#share111 Lots of good stuff there. Thanks to all
the presenters for
It says that it can't grow a mounted filesystem, however it give that message
if the filesystem is unmounted. From the command line I can do a lvexpand,
then ext2online, then the filesystem does grow even if it is mounted. I may
have the command names wrong, as I am not at work right now.
I forgot to say I am on SLES 10 SP1.
-Original Message-
From: Linux on 390 Port on behalf of Marcy Cortes
Sent: Fri 8/29/2008 12:08 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: YAST fails to grow an ext3 FS on LVM.
Works for me. Just did that a couple of days ago. With Yast. On SLES
So if I upgrade from SP1 to SP2 it still won't work?
-Original Message-
From: Linux on 390 Port on behalf of Mark Post
Sent: Fri 8/29/2008 12:09 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: YAST fails to grow an ext3 FS on LVM.
On 8/29/2008 at 2:54 PM, in message
[EMAIL PROTECTED],
It doesn't work from the YAST panels. I suppose this is because it is SP1.
-Original Message-
From: Linux on 390 Port on behalf of Mark Post
Sent: Fri 8/29/2008 12:10 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: YAST fails to grow an ext3 FS on LVM.
On 8/29/2008 at 3:01 PM, in
On 8/29/2008 at 5:40 PM, in message
[EMAIL PROTECTED],
Fargusson.Alan [EMAIL PROTECTED] wrote:
So if I upgrade from SP1 to SP2 it still won't work?
It might, or it might not. The support was put into YaST with SP2, but some
ext3 file systems created prior to SP2 had (something I don't know
Mark,
I've uploaded a whole boatload of Linux and z/VM-related presentations
from SHARE 111 ...
An amazing array of presentations. This is a great resource. Thanks for
your tireless work!
Mike MacIsaac [EMAIL PROTECTED] (845) 433-7061
20 matches
Mail list logo
