Re: Basic question
I recommend visudo. ~ Wayne From: Smith, Ann (ISD, IT) ann.sm...@thehartford.com To: LINUX-390@VM.MARIST.EDU Sent: Wednesday, December 31, 2008 12:28:11 PM Subject: Basic question I need to update sudoers and don't know proper procedure. Figured I'd ask before I mess it up. I did at least create a backup of /etc/sudoers This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential and/or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this communication and destroy all copies. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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 lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Buggered up zipl.conf file
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 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 parameter line and went ahead and executed the zipl command. Now when I try to IPL I get the following message. Waiting for device /dev/dasd1 to appear: ..not found -- exiting to /bin/sh $ The device I should be looking for is /dev/dasda1not /dev/dasd1. Can anyone offer any insight on how I can save this install without starting all over again? This is just a sandbox system I'm playing with for the time being, I was hoping this was going to become my Gold system eventually. Thanks in advance for any assistance. And yes... I do have a backup of the zipl.conf file, I just have no idea on how to restore it and re-run the zipl command without the actual system. David Rakoczy Operating Systems Programmer Thermo Fisher Scientific He who laughs last probably made a backup. -- 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
Re: How to tell if LVM is striped
Check the results of vgdisplay -v against the volume group (klnmal1 maybe?) to see if what the Physical Extent (PE) size is and the number of available PEs. You may need to add another PV into the volume group. HTH, Wayne Lee Stewart wrote: I have a client with a SLES8 LVM that he's having trouble extending.. Is there a command to tell if an LV or VG is striped or not? There's roughly 13G free space in the VG. From what I can tell, SLES8 is LVM1 which won't let you extend a striped volume. That's supposedly one of the reasons he could get: klnmal1:~ # lvextend -L +1G /dev/klnmal1/klnmal1 lvextend -- rounding size to stripe boundary size lvextend -- extending logical volume /dev/klnmal1/klnmal1 to 35.31 GB lvextend -- not enough free/allocatable physical extents to extend logical volume /dev/klnmal1/klnmal1 Thanks for any thoughts... Lee -- Lee Stewart, Senior SE Sirius Enterprise Systems Group Office: (303) 996-7170 Home Office: (303) 798-2954 Fax: (720) 228-2321 [EMAIL PROTECTED] www.siriuscom.com -- 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
Re: NFS problem
Marcy Cortes wrote: Anyone have an ideal what could cause this? This is from my WebSphere guy. I have to use an NFS mount to mount a remote directory from my group's depot server, which has a share set up on the requisite file system. So, I issue the command as follows: mount -t nfs hisservername.win.wellsfargo.com:/export/depot/WebSphere/5.1 /mnt Subsequent to this, my session completely hangs. - SNIP This may have something to do with NFS foreground and background mounts. I think you were almost there, trying to put the mount progress int he background, but what you are looking for is the bg option to your mount command. It's been a wile since I've worked with NFS, but I do remember having to mount NFS filesystems with the bg option to keep the client machine from becoming blocked on I/O when the source was unavailable or slow. HTH, Wayne -- 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: EMC storage
I've had success with EMC Symm 8830 (I Think) FCP attached to a z800 and a z900. We were running SLES8 under zVM v4 in an LPAR. Just make sure that EMC and whoever is doing your iogen are working together. Wayne Biggs, Eric J [ITS] wrote: I know this question has been discussed here before and I've tried to search the archives, but with no luck Has anyone used (or attempted to use) EMC storage attached via FCP with either Red Hat or Suse on the zSeries? I know EMC is not listed at http://www-1.ibm.com/servers/eserver/zseries/connectivity/#fcp but I was told in the past that it should work. Anybody tried it? Eric Biggs Sprint -- 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
Re: Logical Volumes Disappeared after IPL
Did you run mkinitrd, and zipl to update the initrd to include the lvm module? Does your /etc/modules.conf include the lvm module? Nothing else comes directly to mind... Wayne Uriel Carrasquilla wrote: I was so proud of myself yesterday after I created two Logical-Volume-Groups, then their Logical-Volumes along with their mount-points using Yast2 on a SuSE 9/LPAR-zSeries. Today, the IPL could not take place due to the following messages: Activating device mapper ... device-mapper: 4.3.0-ioctl (2004-09-30) initialized: ... done Scanning for LVM Volume Groups No volume groups found To get around, copy my backed up fstab in /etc, rebooted and went on to check: /sbin/vgscan lnxtech:~ # vgscan Reading all physical volumes. This may take a while... Found volume group vgsys01 using metadata type lvm2 Found volume group vgcaplan using metadata type lvm2 Before I try to do a vgcfgrestore, I'd like to find out what am I doing wrong. I thought Yast2 would take care of all the commands behind the scenes. Regards, [EMAIL PROTECTED] NCCI Boca Raton, Florida 561.893.2415 greetings / avec mes meilleures salutations / Cordialmente mit freundlichen Gr|_en / Med vdnlig hdlsning The information contained in this e-mail message is intended only for the personal and confidential use of the recipient(s) named above. This message may be an attorney-client communication and/or work product and as such is privileged and confidential. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original 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 -- 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: Computerworld Article: First National Bank of Omaha throws Sun ou t
Try: http://www.computerworld.com/softwaretopics/os/linux/story/0,10801,99667,00.html?from=story_kc On Wed, 2005-02-16 at 12:42, Peter E. Abresch Jr. - at Pepco wrote: I am interested in this article but this link does not work. Can you verify and repost. Thanks. Peter Steve Gentry [EMAIL PROTECTED] Sent by: Linux on 390 Port LINUX-390@VM.MARIST.EDU 02/15/2005 03:24 PM Please respond to Linux on 390 Port LINUX-390@VM.MARIST.EDU To LINUX-390@VM.MARIST.EDU cc Subject Re: Computerworld Article: First National Bank of Omaha throws Sun ou t I think Bob Herrdink mentioned something about it last week. Steve G. (Bob, sorry if the spelling is wrong) Post, Mark K [EMAIL PROTECTED] Sent by: Linux on 390 Port LINUX-390@VM.MARIST.EDU 02/15/2005 02:09 PM Please respond to Linux on 390 Port To: LINUX-390@VM.MARIST.EDU cc: Subject:Computerworld Article: First National Bank of Omaha throws Sun ou t I don't recall seeing this mentioned previously. FEBRUARY 10, 2005 - First National Bank of Omaha said this week that it's nearing completion of a complete changeout of its distributed server infrastructure for a mainframe and blade-server architecture based on Linux. While only 80% complete, the move is already expected to save the company $1.8 million this year in operating expenses and another $9.6 million through 2011. The bank expects to complete the project by April and said much of the savings will come from a reduction in the number of systems engineers from 24 to eight. http://www.computerworld.com/softwaretopics/os/linux/story/0,10801,99667,00 . html 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 -- 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 This Email message and any attachment may contain information that is proprietary, legally privileged, confidential and/or subject to copyright belonging to Pepco Holdings, Inc. or its affiliates (PHI). This Email is intended solely for the use of the person(s) to which it is addressed. If you are not an intended recipient, or the employee or agent responsible for delivery of this Email to the intended recipient(s), you are hereby notified that any dissemination, distribution or copying of this Email is strictly prohibited. If you have received this message in error, please immediately notify the sender and permanently delete this Email and any copies. PHI policies expressly prohibit employees from making defamatory or offensive statements and infringing any copyright or any other legal right by Email communication. PHI will not accept any liability in respect of such communications. -- 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
Re: Any caveats moving root filesystem to LVM?
I have done this on a fresh install. /boot was it's own filesystem / was in lvm vgwhatever SUSE appends LVM to the /etc/sysconfig/modules so that the lvm module is available in the initial ramd. HTH Wh Michael MacIsaac [EMAIL PROTECTED] wrote: At IPL how will the Suse initrd find the Volume group and mount the root file system? I don't think it can. We boot from a 100 cyl /boot fs and have a logical volume mounted over /. Maybe the easiest way is to try this type of migration is to play tricks with minidisks: - Shut down the Linux to be migrated - Define a new user ID with the two or three new volumes as well as the volumes with the old / and /usr/ as different minidisks - Install a fresh sles8 with a 100 cyl /boot and a two or three volume LVM over / - Temporarily mount and recursively copy the old / to the new / - Do the same for /usr/ - Reboot and cross your fingers - if it doesn't work, at least the old user ID is unchanged and can still be booted I've never tried this, but it sounds good on paper. (During the time I was writing this I see Mark and Brandon's posts. I tend to agree - you may want to avoid logical volumes over / altogether.) Mike MacIsaac (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 -- 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: Adding an additional volume using LVM
Graeme, Did you also extend the filesystem? For SLES8, if you are using ReiserFS, you can do this while the filesystem is mounted with resize_reiserfs. Cheers, Wayne Graeme Westerman NFU Mutual Insurance wrote: Hi list, we are currently running SLES8 under z/VM. I have 1 lvm group consisting of 3 3390-9 disks and have added an additional volume, dasdg1. When I issue various display cmds as shown below, the df -ah cmd still shows the previous configuration. pvscan -- reading all physical volumes (this may take a while...) pvscan -- ACTIVE PV /dev/dasdd1 of VG system [6.88 GB / 0 free] pvscan -- ACTIVE PV /dev/dasde1 of VG system [6.88 GB / 0 free] pvscan -- ACTIVE PV /dev/dasdf1 of VG system [6.88 GB / 0 free] pvscan -- ACTIVE PV /dev/dasdg1 of VG system [6.87 GB / 0 free] pvscan -- total: 4 [27.51 GB] / in use: 4 [27.51 GB] / in no VG: 0 [0] lvscan -- ACTIVE/dev/system/samba [27.50 GB] lvscan -- 1 logical volumes with 27.50 GB total in 1 volume group lvscan -- 1 active logical volumes # df -ah FilesystemSize Used Avail Use% Mounted on /dev/dasda1 2.2G 245M 1.9G 12% / proc 0 0 0 - /proc devpts 0 0 0 - /dev/pts /dev/dasdb1 2.3G 578M 1.6G 27% /usr /dev/system/samba 21G 18G 1.7G 92% /opt/smb shmfs 62M 0 62M 0% /dev/shm When I add additional data to extend past the current free 1.7G I get the following error msg; cp: writing `temp3/SLES-9-s390-RC5a-CD1.iso': No space left on device Has anyone else seen this problem or can give me a few pointers as to what the problem might be ? Thanks, Graeme __ IMPORTANT The information contained in this e-mail and in any attachments is intended only for the named recipient or entity. The e-mail and any attachments may contain legally privileged or confidential information and may not be disclosed to anyone else. If you are not the intended recipient, please notify us immediately on 01789-202121 and delete the material from any computer that may contain it and destroy any printed copies you may have made. We accept no liability for any direct, indirect or consequential loss or damage arising from any action taken in reliance on or use of the information contained in this e-mail and give no warranty or representation as to its accuracy or reliability. NFU Mutual has the facility to monitor and read both incoming and outgoing communications by e-mail and these may be intercepted by its automated e-mail administrators. NFU Mutual will not accept e-mail communications found to contain viruses. Parent Company: The National Farmers Union Mutual Insurance Society Ltd (No. 111982). Authorised and regulated by the Financial Services Authority for Life, Pension and Investment business. Registered in England Registered office : Tiddington Road, Stratford-upon-Avon, CV37 7BJ. Tel: 01789 204211 NFU Mutual is a member of the General Insurance Standards Council, ABI and FOS. http://www.nfumutual.co.uk -- 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
