Re: Using Tivoli Storage Manager w/SAN
I understand it from the TSM side, it's the Linux side that I'm not sure about. What does it take(ie hardware, software) to get to a SAN, so that we can use the disk for a storage pool? We are running a Z/890 with an IFL, and SuSE Linux running under VM 5.1. Gene Walters System Programmer WV Dept of Administration - OT 304-558-5914 ext 8902 Fax 304-558-1351 [EMAIL PROTECTED] 5/31/2007 3:40 PM Where is it documented? The description is in the TSM Administrators Guide in the Using Magnetic Disk Devices with TSM chapter (my manuals are old, but this hasn't changed since the ADSM days). The important stuff is in the description of DEVTYPE=FILE and DEVTYPE=DISK options for device classes and storage pools. With DEVTYPE=FILE, you essentially define the SAN storage as a bunch of files emulating tapes, and have TSM spool directly to them. TSM doesn't care about what kind of disk storage the files live on as long as the operating system can access it. DEVTYPE=FILE volumes can also be used for database dumps and export/import processing, so if you're tape-constrained on the Linux guest or you want to use normal 390 tape drives, this is a partial way to cheat on the TSM stupidity of not supporting channel-attached tape. With DEVTYPE=DISK, you use DEFINE VOLUME, and add the volumes to a storage group as normal. DEVTYPE=DISK volumes are better suited for random-access work, but can't be used for database dumps, etc. -- 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
Using Tivoli Storage Manager w/SAN
Hello, Has anyone here setup TSM on Linux using a SAN as their main storage pool? Is it possible? Gene Walters System Programmer WV Dept of Administration - OT 304-558-5914 ext 8902 Fax 304-558-1351 -- 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: Using Tivoli Storage Manager w/SAN
Where is it documented? Gene Walters System Programmer WV Dept of Administration - OT 304-558-5914 ext 8902 Fax 304-558-1351 [EMAIL PROTECTED] 5/31/2007 9:42 AM Has anyone here setup TSM on Linux using a SAN as their main storage pool? Is it possible? Yes, it works as documented although you should use the DASDtape (disk emulates tape) approach, and ensure you have defined a high number of devices for that pool. -- 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: Guest Lan/VSwitch/VLAN
I appreciate everyone's input. We are going to try to implement the VSWITCH. Thanks Gene Gene Walters System Programmer WV Dept of Administration - OT 304-558-5914 ext 8902 Fax 304-558-1351 [EMAIL PROTECTED] 5/14/2007 1:42:51 PM If it were me, I'd probably go with the VSWITCH. Heartbeat packets really don't exploit the best parts of real hipersockets (high volume bulk data transfer) much, and the ability to separate stuff easily later is a big architectural win in my book. Makes sense, particularly in our case where we have redundant OSA cards. Although since real hipersockets run over the system memory backplane, you also have multiple buses to work with there, so you get built-in redundancy. If that memory bus isn't working, then you're not doing much with the machine anyway, and it's always built in, so you don't have to worry about it at DR sites. I'd still do the VSWITCH, though. IMHO, it's a more flexible option. -- 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
Guest Lan/VSwitch/VLAN
Hi All, I know this is a broad question, but I am trying to understand some things. We currently are using CTC connections for our network access to our Linux Instances running under VM. We were told that CTC's were doing it the hard way. So I am trying to figure out what the other way is. We have Z/VM 5.1 running on an IFL and an OSA-Express card. What should we be using instead of CTC's for network connection, VGuest, VSwitch VLAN? I'm confused as to what each actually does. Any help would be appreciated. Thanks Gene Gene Walters System Programmer WV Dept of Administration - OT 304-558-5914 ext 8902 Fax 304-558-1351 -- 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
Apache2 Problem
I am getting the following errors when I start Apache2. They repeat over and over and over. Any ideas? [Fri Feb 03 08:09:01 2006] [error] (13)Permission denied: apr_global_mutex_lock(jk_log_lock) failed [Fri Feb 03 08:09:01 2006] [notice] Apache/2.0.49 (Linux/SuSE) configured -- resuming normal operations [Fri Feb 03 08:09:01 2006] [notice] child pid 20388 exit signal Segmentation fault (11) [Fri Feb 03 08:09:01 2006] [notice] child pid 20389 exit signal Segmentation fault (11) [Fri Feb 03 08:09:02 2006] [error] (13)Permission denied: apr_global_mutex_lock(jk_log_lock) failed [Fri Feb 03 08:09:03 2006] [notice] child pid 20393 exit signal Segmentation fault (11) [Fri Feb 03 08:09:05 2006] [error] (13)Permission denied: apr_global_mutex_lock(jk_log_lock) failed [Fri Feb 03 08:09:05 2006] [notice] child pid 20398 exit signal Segmentation fault (11) -- 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: Linux Monitoring
We had the same problem a couple of years ago, and adjusting those buffers fixed ours. [EMAIL PROTECTED] 1/20/2006 10:06:44 AM Sounds like our similar problem that was caused by developing scheduler Eligible lists, because we had not increased the CP default SRM STORBUF values of STORBUF: Q1=125% Q2=105% Q3=095% When problem recurs again do CP INDICATE to see if VM has userids in the Eligible lists: CP INDICATE AVGPROC-014% 02 XSTORE-03/SEC MIGRATE-/SEC MDC READS-01/SEC WRITES-00/SEC HIT RATIO-100% STORAGE-052% PAGING-0001/SEC STEAL-000% Q0-2(0) DORMANT-00034 Q1-00011(0) E1-0(0) Q2-7(0) EXPAN-002 E2-0(0) Q3-4(0) EXPAN-002 E3-0(0) You have an Eligible list if the E1-,E2-,E3- counts are not 0; the above sample shows 0 users in the Eligible lists. If you have an eligible list do CP Q SRM, look at the response's STORBUF line, and set the SRM STORBUF values higher with something like CP SET SRM STORBUF 300% 250% 200% If it works then put the CP SET SRM command in your AUTOLOG1 userid's PROFILE EXEC to run when VM IPL's. This e-mail, including any attachments, may be confidential, privileged or otherwise legally protected. It is intended only for the addressee. If you received this e-mail in error or from someone who was not authorized to send it to you, do not disseminate, copy or otherwise use this e-mail or its attachments. Please notify the sender immediately by reply e-mail and delete the e-mail from your system. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Kreiter, Chuck Sent: Friday, January 20, 2006 9:09 AM To: LINUX-390@VM.MARIST.EDU Subject: Linux Monitoring We are running four SUSE 9 Linux guests under z/VM 5.1. z/VM and Linux have all current maintenance and fixes applied. All 4 guests were cloned from the same base install. The problem we have is that occasionally, Linux will stop functioning. Our connection is via VNC. I haven't been able to establish a pattern as to what is causing this. The symptoms are as follows: Linux could be up for hours or days running fine. Working on anything from YaST to web browsing to accessing a SMB share, upon clicking something, the VNC session will hang and then disconnect. We've tried logging on to the guest under VM, but even VM doesn't allow us to do anything. We end up forcing the guest off using MAINT. Then, we can reboot the image fine and it could run fine for hours or weeks. I've checked our HMC for CPU activity on the IFL, but it is 5% utilized so I don't think something is looping. If anyone has experienced this, I'd be curious to hear how your resolved it. Or, if anyone knows of a way to log what is happening, that might help as well. As we are still evaluating this as a viable platform, we haven't purchased SUSE support yet. Chuck Kreiter Lead Systems Programmer State Auto Insurance * This message was scanned by State Auto's mail server for viruses and objectionable content. -- 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
Re: SQR for SUSE
on Zlinux [EMAIL PROTECTED] 11/4/2005 9:26 AM Hi, On Zlinux or Linux ? - Original Message - From: Gene Walters [EMAIL PROTECTED] To: LINUX-390@VM.MARIST.EDU Sent: Friday, November 04, 2005 11:02 AM Subject: SQR for SUSE Hi, Does anyone know if SQR will run on SUSE Linux? -- 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
Moving root to a new volume
Hi all, When I initially installed my Linux Instances, I used MOD-3's. I would now like to move them to MOD-9's because my boss wants to reconfigure all the DASD to MOD-9's. How can I accomplish moving root to a new volume and get it to IPL off that new volume? Thanks Gene -- 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
Linux Administration tools
Hi all, I am trying to get a feel for how people are managing their Linux Instances on the S/390. Are you using any tools like Levanta? If not, what are you using? Thanks Gene -- 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: Linux Administration tools
Well, Actually, both monitoring and maintenance of the instances. I am trying to figure out where is the best place to spend the money. Is it better to monitor in VM, or linux or both. We basically arent monitoring anthing, and I need to figure out where to start. Thanks Gene [EMAIL PROTECTED] 04/06/04 01:27PM In what sense do you mean manage? Do you mean monitoring resources? and in what aspect, from VM or from Linux? We have not found a much in the way of VM tools. We use Big Brother (www.bb4.com) to monitor processes and performance on each instance. Cheers; E! - Eric Wilson IBM Certified Advanced Technical Expert RedHat Certified Engineer -Original Message- From: Gene Walters [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 06, 2004 12:23 PM To: [EMAIL PROTECTED] Subject: Linux Administration tools Hi all, I am trying to get a feel for how people are managing their Linux Instances on the S/390. Are you using any tools like Levanta? If not, what are you using? Thanks Gene -- 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
Re: SuSE SP3 Kernel panic: VFS: Unable to mount root fs on 5e: 01 ( was Re: Myth of the 1K blocksize
Hi Daniel, As you can probably tell, I'm real fluent with a lot of the Linux commands, so I really appreciate your help. I tried that command, and here is what I got: rpm: only one major mode may be specified [EMAIL PROTECTED] 04/01/04 09:14AM It's funny, this is the one I use to clone, and I just went to another instance, found it and copied it back. Once tar was there, it worked great. I really appreciate your help Glad you are back in business now, though the missing binary IS disconcerting. You should probably take inventory and figure out what else is missing, and why... There's probably a shorter way to do this, but: for i in `rpm -qa`; do rpm -V $i; done |grep missing should work for any rpm packages in your database, though it will take a long time to finish. If some of the files listed as missing seem important, you should consider finding them again :). Good luck, ~ Daniel --- This message is the property of Time Inc. or its affiliates. It may be legally privileged and/or confidential and is intended only for the use of the addressee(s). No addressee should forward, print, copy, or otherwise reproduce this message in any manner that would allow it to be viewed by any individual not originally listed as a recipient. If the reader of this message is not the intended recipient, you are hereby notified that any unauthorized disclosure, dissemination, distribution, copying or the taking of any action in reliance on the information herein is strictly prohibited. If you have received this communication in error, please immediately notify the sender and delete this message. Thank you. -- 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: SuSE SP3 Kernel panic: VFS: Unable to mount root fs on 5e: 01 ( was Re: Myth of the 1K blocksize
You hit it right on the head. Somehow tar was gone from this instance of Linux. It's funny, this is the one I use to clone, and I just went to another instance, found it and copied it back. Once tar was there, it worked great. I really appreciate your help Thanks Gene [EMAIL PROTECTED] 03/31/04 04:10PM It looks like that messages is generated around line 837 in the mkinird, before your change. Ugh, my find had wrapped back to the beginning without me realizing. Okay, on line 844 tar -C $root_dir -cf - $x 2/dev/null | tar -C $tmp_mnt -xpf - 2/dev/null you're getting a rc 127. It's as if there is no tar command in your path. If you have one (preferably in /bin/tar), then try taking out the 2/dev/null's on that line and run it again and see what tar complains about. Pretty sure tar exits with 0, 1, or 2 though, so it really seems like the shell can't find tar. + x=lib/modules/2.4.21-83-default/kernel/drivers/s390/block/dasd_mod.o + '[' lib/modules/2.4.21-83-default/kernel/drivers/s390/block/dasd_mod.o ']' + tar -C / -cf - lib/modules/2.4.21-83- default/kernel/drivers/s390/block/dasd_mo d.o + tar -C /var/tmp/mnt3883 -xpf - + '[' 127 '!=' 0 ']' + echo 'dasd_mod: failed to add module /lib/modules/2.4.21-83- --- This message is the property of Time Inc. or its affiliates. It may be legally privileged and/or confidential and is intended only for the use of the addressee(s). No addressee should forward, print, copy, or otherwise reproduce this message in any manner that would allow it to be viewed by any individual not originally listed as a recipient. If the reader of this message is not the intended recipient, you are hereby notified that any unauthorized disclosure, dissemination, distribution, copying or the taking of any action in reliance on the information herein is strictly prohibited. If you have received this communication in error, please immediately notify the sender and delete this message. Thank you. -- 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
Xwindows for Windows
I discovered something last week, and I don't know if most of you know about it or not so I thought I would share. I found a program called cygwin. The feature I like is that it lets you do Xwindows stuff from Linux back to your windows desktop(Ie yast2 etc.) Up til now I had been looking at Hummingbird exceed and a couple others, but they all wanted a couple hundred dollars for theirs. cygwin is free You can download it at www.cygwin.com If you already knew it, ignore this message. Thanks Gene -- 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: Myth of the 1K blocksize on eckd - revisited
Hi Everyone, I just put on SuSE SP3. When I IPL'd, it gives me these messages: Loading module dasd_mod dasd=$dasd ... insmod: dasd_mod: no module by that name found Loading module dasd_eckd_mod ... insmod: dasd_eckd_mod: no module by that name found kmod: failed to exec /sbin/modprobe -s -k block-major-94, errno = 2 VFS: Cannot open root device dasda1 or 5e:01 Please append a correct root= boot option Kernel panic: VFS: Unable to mount root fs on 5e:01 HCPGIR450W CP entered; disabled wait PSW 000A 8022CD08 All the modules appear to be in the right place, and the modules.dep has all the right directories in it. Did anyone else experience this when they put on Service Pack 3? Thanks Gene -- 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
SuSE SP3 Kernel panic: VFS: Unable to mount root fs on 5e:01 ( was Re: Myth of the 1K blocksize on e
Yes, I checked the zipl.conf and then ran zipl. Yes the Kernel reports the new version which is: Linux version 2.4.21-83-default I'm stumped. Thanks Gene [EMAIL PROTECTED] 03/31/04 08:17AM I just put on SuSE SP3. When I IPL'd, it gives me these messages: Loading module dasd_mod dasd=$dasd ... insmod: dasd_mod: no module by that name found Loading module dasd_eckd_mod ... insmod: dasd_eckd_mod: no module by that name found kmod: failed to exec /sbin/modprobe -s -k block-major-94, errno = 2 VFS: Cannot open root device dasda1 or 5e:01 Please append a correct root= boot option Kernel panic: VFS: Unable to mount root fs on 5e:01 HCPGIR450W CP entered; disabled wait PSW 000A 8022CD08 All the modules appear to be in the right place, and the modules.dep has all the right directories in it. Did anyone else experience this when they put on Service Pack 3? Did you check that your /etc/zipl.conf is correct and re-run zipl? When linux first starts, does it report the kernel version that you'd expect? ~ Daniel --- This message is the property of Time Inc. or its affiliates. It may be legally privileged and/or confidential and is intended only for the use of the addressee(s). No addressee should forward, print, copy, or otherwise reproduce this message in any manner that would allow it to be viewed by any individual not originally listed as a recipient. If the reader of this message is not the intended recipient, you are hereby notified that any unauthorized disclosure, dissemination, distribution, copying or the taking of any action in reliance on the information herein is strictly prohibited. If you have received this communication in error, please immediately notify the sender and delete this message. Thank you. -- 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: SuSE SP3 Kernel panic: VFS: Unable to mount root fs on 5e: 01 ( was Re: Myth of the 1K blocksize
My zipl.conf does have that statement, but I didn't run the mkinitrd. I just tried, but I get this error: using /dev/dasda1 as root device (mounted on / as ext2) Found ECKD dasd, adding dasd eckd discipline! Note: If you want to add ECKD dasd support for later mkinitrd calls where possibly no ECKD dasd is found, add dasd_eckd_mod to INITRD_MODULES in /etc/sysconfig/kernel creating initrd /boot/initrd for kernel /boot/kernel/image (version 2.4.21-83-default) (s390) dasd_mod: failed to add module /lib/modules/2.4.21-83-default/kernel/drivers/s3 90/block/dasd_mod.o initrd too small Run zipl now to update the IPL record! how do I make it bigger? Thanks gene [EMAIL PROTECTED] 03/31/04 08:55AM Yes, I checked the zipl.conf and then ran zipl. Does your zipl.conf have a line like ramdisk=/boot/initrd ? If not, you should probably add it (run mkinitrd if you haven't), and then run zipl again. Loading module dasd_mod dasd=$dasd ... insmod: dasd_mod: no module by that name found Loading module dasd_eckd_mod ... insmod: dasd_eckd_mod: no module by that name found When built as modules, the DASD drivers need to be in the initrd or else the kernel has no way of reading them (since the object files reside on DASD). ~ Daniel --- This message is the property of Time Inc. or its affiliates. It may be legally privileged and/or confidential and is intended only for the use of the addressee(s). No addressee should forward, print, copy, or otherwise reproduce this message in any manner that would allow it to be viewed by any individual not originally listed as a recipient. If the reader of this message is not the intended recipient, you are hereby notified that any unauthorized disclosure, dissemination, distribution, copying or the taking of any action in reliance on the information herein is strictly prohibited. If you have received this communication in error, please immediately notify the sender and delete this message. Thank you. -- 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: SuSE SP3 Kernel panic: VFS: Unable to mount root fs on 5e: 01 ( was Re: Myth of the 1K blocksize
I did as you suggested, but I don't get any additional messages, it's the exact same thing. [EMAIL PROTECTED] 03/31/04 12:04PM creating initrd /boot/initrd for kernel /boot/kernel/image (version 2.4.21-83-default) (s390) dasd_mod: failed to add module /lib/modules/2.4.21-83- default/kernel/drivers/s3 90/block/dasd_mod.o initrd too small Run zipl now to update the IPL record! how do I make it bigger? How much freespace do you have for files placed in /var/tmp/? Is it possible you are about full? Looking at /sbin/mkinitrd, it looks like SuSE first makes one initrd (20480k), populates it, then figures out how much it REALLY needs. It creates a second initrd of the really needed size, then copies everything over. Your error is during that last copy part, indicating that the second initrd really isn't big enough. Either mkinitrd's img_size calculation on line 1058 is wrong, or you run out of room while creating the new one. At line at 1061 which is: dd if=/dev/zero of=$tmp_initrd_small bs=1k count=$img_size 2/dev/null Can you remove the 2/dev/null portion of that, run mkinitrd again and see if you get any No space left on device errors? ~ Daniel --- This message is the property of Time Inc. or its affiliates. It may be legally privileged and/or confidential and is intended only for the use of the addressee(s). No addressee should forward, print, copy, or otherwise reproduce this message in any manner that would allow it to be viewed by any individual not originally listed as a recipient. If the reader of this message is not the intended recipient, you are hereby notified that any unauthorized disclosure, dissemination, distribution, copying or the taking of any action in reliance on the information herein is strictly prohibited. If you have received this communication in error, please immediately notify the sender and delete this message. Thank you. -- 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: SuSE SP3 Kernel panic: VFS: Unable to mount root fs on 5e: 01 ( was Re: Myth of the 1K blocksize
Well, i tried upping the initial size, I quadrupled it, to no avail. It looks like that messages is generated around line 837 in the mkinird, before your change. Here is the results of the bash on mkinitrd: bash -x mkinitrd + kernels_default=vmlinuz vmlinuz.shipped + initrds_default=initrd initrd.shipped + kernels= + initrds= + modules= + boot_dir= + splash=auto + oem= ++ uname -m + arch=s390 + arch=s390 + arch=s390 + kernels_default=kernel/image + initrds_default=initrd + splash=off + getopts :hk:i:m:b:d:o:s:t:D: a ++ expr 1 - 1 + shift 0 + '[' -n '' ']' + '[' '' ']' + root_dir=/ + '[' xoff = xoff ']' + splash= + '[' x = xauto ']' + '[' -n '' ']' + '[' -z '' ']' + '[' -n '' ']' + '[' s390 = ppc -a kernel/image = vmlinux ']' + '[' -z '' ']' + kernels=kernel/image + '[' -z '' ']' + initrds=initrd ++ echo kernel/image ++ wc -w + kc= 1 ++ echo initrd ++ wc -w + ic= 1 + '[' 1 '!=' 1 ']' + '[' -z '' ']' + boot_dir=/boot + '[' -z '' ']' + tmp_dir=/var/tmp + static_shell=/bin/ash.static + static_insmod=/sbin/insmod.static + bootsplash_picture_dir=//usr/share/splash/themes/current + image_blocks=80980 + image_inodes=8096 + PATH=/sbin:/usr/sbin:/sbin:/usr/sbin:/usr/local/sbin:/root/bin:/usr/local/bin: /usr/bin:/usr/X11R6/bin:/bin:/usr/games:/opt/gnome2/bin:/opt/gnome/bin:/opt/kde3 /bin:/opt/gnome/bin:/opt/oracle/product/9ir2/bin + tmp_mnt=/var/tmp/mnt3883 + tmp_mnt_small=/var/tmp/mnt3883_small + tmp_msg=/var/tmp/msg3883 + tmp_modconf=/var/tmp/modconf3883 + lx_rc=/var/tmp/mnt3883/linuxrc + is_mounted= + is_mounted_small= + tmp_initrd=///var/tmp/initrd3883 + tmp_initrd_small=///var/tmp/initrd3883_small + mounted_proc= + '[' '!' -r /proc/mounts ']' + '[' -z '' ']' ++ sed -e '/^[ ]*#/d' + read fstab_device fstab_mountpoint fstab_type fstab_options dummy + test / = / + rootdev=/dev/dasda1 + rootfstype=ext2 + break + test -z '' + test -z /dev/dasda1 + realrootdev=/dev/dasda1 + root_lvm=0 + '[' -n /dev/dasda1 -a -b /dev/dasda1 ']' ++ ls -l /dev/dasda1 ++ sed -e 's/.* \([0-9]\+\), *[0-9]\+.*/\1/' + major=94 + '[' 94 -ne 58 ']' + '[' / '!=' / ']'
Re: TSM Scripts
thanks for the scripts
Gene
[EMAIL PROTECTED] 01/30/04 02:54AM
This script works fine (with SUSE).
#! /bin/sh
BIN=/opt/tivoli/tsm/client/ba/bin/dsmc
test -x $BIN || exit 5
. /etc/rc.status
rc_reset
case $1 in
start)
echo -n Starting TSM
$BIN schedule /var/log/adsm.log 21
rc_status -v
;;
stop)
echo -n Stopping TSM
killproc -TERM $BIN
rc_status -v
;;
restart)
$0 stop
$0 start
rc_status
;;
reload)
$0 stop
$0 start
rc_status
;;
status)
echo -n Checking for dsmc:
checkproc $BIN
rc_status -v
;;
*)
echo Usage: $0 {start|stop|status|restart|reload}
exit 1
;;
esac
rc_exit
--
+++ GMX - die erste Adresse f|r Mail, Message, More +++
Bis 31.1.: TopMail + Digicam f|r nur 29 EUR http://www.gmx.net/topmail
TSM Scripts
Hi all, Does anyone have a Tivoli Storage Manager Start and stop scripts for SUSE 8 that they would be willing to share. I haven't had a lot of time to figure out the new way of starting and stoping things. Any help would be appreciated. Gene
SLES 8 and IBM Shark
We are getting ready to move our VM/SUSE installations from an EMC DASD box to an IBM Shark DASD box. I have two questions. 1. Does anyone know of any issues with Linux/VM when the DASD UCB's are genned above the 32MB line. 2. Are there any issues using 3390-9's with VM/LINUX. Thanks for your time. Gene
Going from Full Volume to Minidisks
Hello, Up until now, I have been dedicating entire 3390 volumes for my linux ROOT. Now I want to switch to minidisks so that I can share the DASD between multiple Linux Instances. I would normally use DDR in VM to clone my Image, but DDR is a byte-by-byte copy. Can I copy from a full volume to a minidisk using DDR?, is there a better way? Thanks Gene
CPU Limit
Is there any type of a workload manager for SuSe Linux? I have a situation that a task is taking up all available CPU and not even TCP/IP can get a word in. I don't want to purge the task, I just want to limit how much CPU it can eat. Thanks Gene
Re: Anyone tried Levanta
Anyone tried BMC's Deployment Manager? How's it compare to Levanta? Thanks Gene [EMAIL PROTECTED] 09/10/03 06:27PM We're using Levanta. Started with version 1 and are now using version 2. Currently have a few production Version 1 instances. In 3 weeks we have some mission-critical Linux instances going into production using Levanta. Version 2 is based on VM-level minidisk sharing (instead of NFS as used in version 1) which allows packages to be shared amongst instances. There is then a read/write file system layer that allows for customizations to the products. Also the product now supports non-RPM packages which is GREAT!! Since our VM environment is dedicated to Linux instances I even use Levanta as our USER DIRECT manager. The two interfaces provided (Web UI and command level) are both POWERFUL!!! This sophistication does come with a bit of a learning curve. Some new concepts and terminology.. nothing like rocket science... Heck I learned it!! haha We're very happy with the product!!! Version 2 is much stronger than version 1 mainly in that it can handle packages that are other than RPMs. - Original Message - From: Gene Walters [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, September 10, 2003 10:56 AM Subject: Anyone tried Levanta Hi, Has anyone on the list tried Levanta? If so, what do you think of it? thanks Gene
Anyone tried Levanta
Hi, Has anyone on the list tried Levanta? If so, what do you think of it? thanks Gene
