Re: YAST fails to grow an ext3 FS on LVM.
Fargusson.Alan wrote: Has anyone ask Novell why YAST fails to grow a logical volume that has an ext3 filesystem on it? Alan, I see from this thread that you mention SLES-10-SP1. With this level you can only grow a 4KB bs filesystem to the next 16GB boundary. With SLES-10-SP2 any newly created filesystems are pre-configured to allow growth. Any filesystems created on SP1 will still have limitations even under SP2. I have not yet found any way to upgrade an SP1 filesystem without recreating it from scratch. The man page for ext2online mentions an ext2prepare command, but this is not shipped with SLES-10-SP2. Neither does tune2fs seem to cover this, its a mystery to me right now. It would be nice if SLES had a method to upgrade filesystems, even if this had to be done one-time offline. mark -- 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
Fw: Help with network settings on z/Linux (fwd)
Eric, HiperSocket interfaces use already a high MTU-size as default. You can increase this value only by additional 4064 bytes. The default MTU-size depends on the CHPARM-value of your IQD CHPID definition. CHPARMmax. frame sizeMTU size = 00 (default) 16KB 8KB 40 24KB16KB 80 40KB32KB C0 64KB56KB Probably you are using a HiperSocket interface with CHPARM 00, while Terry is using CHPARM 40. Regards, Ursula Braun IBM Germany, Linux on System z development Forwarded Message Eric Hunter [EMAIL PROTECTED] Sent by: Linux on 390 Port LINUX-390@VM.MARIST.EDU 29.08.2008 22:49 Please respond to Linux on 390 Port LINUX-390@VM.MARIST.EDU To LINUX-390@VM.MARIST.EDU cc Subject Re: Help with network settings on z/Linux 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 SIOCSIFMTU: Invalid argument What did you have to do to get yours to accept 16384? -Original Message- From: Martin, Terry R. (CMS/CTR) (CTR) [EMAIL PROTECTED] To: LINUX-390@VM.MARIST.EDU Sent: Tue, 19 Aug 2008 12:01 pm Subject: Re: Help with network settings on z/Linux Hi Alan, I did some research based on your response I this is what I found: In my case the E3 (HiperSockets CHPID) with a CHPARM=40k is being used in the environment that is working. The E2 (HiperSockets CHPID) with a CHPARM=64k is being used in the environment that is NOT working. Can the difference in these sizes alone cause me the issue I am having? The MTU size for both HiperSockets is set to 16,348 across the board. Thank You, Terry Martin Lockheed Martin - Information Technology z/OS z/VM Systems - Performance and Tuning Cell - 443 632-4191 Work - 410 786-0386 [EMAIL PROTECTED] -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Alan Altmark Sent: Tuesday, August 19, 2008 11:10 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Help with network settings on z/Linux On Tuesday, 08/19/2008 at 10:41 EDT, Martin, Terry R. (CMS/CTR) (CTR) [EMAIL PROTECTED] wrote: We have two environments that we are building as part of our POC. We ship data via DB2 Connect from the mainframe DB2 to a Linux guest via a HiperSockets Network. In our DEV environment all of our tables process without issue. In our VAL environment there are six tables that the SQL fails for. We have been engaged with IBM via a PMR on this and have been going back and forth. At this point it appears that the issue is with the number of rows. In the SQL when they do an SELECT * and do not specify the rows it works. When they specify the tables in the Select it apparently increases the size of the SQL and it never gets to the mainframe. It looks like it is a 2k buffer limitation somewhere. Is there anything in the TCP/IP stack in z/Linux or any network setting in z/Linux that would enforce this limitation? Verify that the MFS (CHPARM= or OS= in IOCP) and MTU for the HiperSockets connection are the same for your DEV and VAL environments. Alan Altmark z/VM Development IBM Endicott -- 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 -- 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 -- End Forwarded Message -- -- 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
Automatic activation of LVM
Dear all, Does somebody know when exactly a LVM volume group is activated during startup of SLES 10 SP2? I have defined a LVM with two 3390-25. After a reboot of my LINUX image, the logical volume is not active and therefore the mount in FSTAB is not working. I must do a lvchange -a y system and then the mount is working. Is the activation also done during the init phase from the initrd and do I have to make a zipl for this? Thanks for your help. -- Best regards Florian Bilek -- 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
Re: [CentOS-devel] slow Perl on CentOS 5
Notes to RHEL5 users. I'm sending this to the RHEL5 list because it affects RHEL5 users. The full discussion can be read from the archive for centos-devel at centos.org. RH has promised its fix in RHEL5U3. CentOS has it now, the remaining discussion is how it's distributed. If you need it now, use the CentOS5 rpm and/or lean on RH. Note to RHEL5 on Linux-390. The CentOS fixed rpm needs to be built for Zeds, but (probably) the CentOS src.rpm will build fine. Note to SLES10 users on linux-390 I don't have a clue whether this applies to you, it could. Code to test it can be found in the archive I mentioned above. Marcus Moeller wrote: Dear John. _I_ would prefer to pick it up automatically, without having to make special configuration changes or use unusual commandline arguments. I'm looking for someone to explain why it should not be so, and binary compatibility isn't it. Nor does the overview at www.centos.org explain why not. It's not only about binary compatibility (of course this patch might not break with it). It's more about dividing from upstream. That's not, afaics, a stated objective. There is a downside (prospective problems for users) in not fixing the problem for all C5 users. What disadvantage is there to CentOS supplying its fix through the regular updates repo? MM, like me, doesn't see a problem with binary compatibility. The fix is available and implemented and (to some extent) tested. Apparently, RH has promised to fix it properly at some point in the future and the RH fix will automatically supersede the C fix. As mentioned before RH will push out a fix sooner or later. Those systems that are affected (which is non of mine, at least) may be patched using testing or even fasttrack repo. As I've said before, I don't think most people would know, unless they run over the problem in their own code, and if they do encounter it and use Google as I did, the fix they are more likely to find is build your own perl. I value compatibility with RH even though, in practice, it's probably not going to affect me directly - I'm unlikely to use commercial certified software - but I don't see a reason for retaining RH bugs just for compatibility. Note, my C5 system doesn't even have a definition of a testing or fasttrack repo. -- Cheers John -- spambait [EMAIL PROTECTED] [EMAIL PROTECTED] -- Advice http://webfoot.com/advice/email.top.php http://www.catb.org/~esr/faqs/smart-questions.html http://support.microsoft.com/kb/555375 You cannot reply off-list:-) -- 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
Re: Automatic activation of LVM
On 9/1/2008 at 5:13 PM, in message [EMAIL PROTECTED], Florian Bilek [EMAIL PROTECTED] wrote: Dear all, Does somebody know when exactly a LVM volume group is activated during startup of SLES 10 SP2? I have defined a LVM with two 3390-25. After a reboot of my LINUX image, the logical volume is not active and therefore the mount in FSTAB is not working. I must do a lvchange -a y system and then the mount is working. Is the activation also done during the init phase from the initrd and do I have to make a zipl for this? Actually, you'll likely need to do both a mkinitrd and zipl, since it appears the necessary LVM kernel modules aren't being included in your current initrd. To make sure, you can do mkinitrd -f lvm2 and you should be set. 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
