unsubscribe
Dale Slaughter AEGON Global Technology | Technology Operations / Mainframe Transaction Processing Cedar Rapids, Iowa | Phone: 319.355.6277 internal: 120.6277 | dale.slaugh...@transamerica.com -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Neale Ferguson Sent: Tuesday, March 05, 2013 1:45 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Issues using VMUR ls -l /usr/bin/netdatax Is the x permission set? On 3/5/13 2:40 PM, Shumate, Scott scshum...@bbandt.com wrote: This is what I get. [root@wil-zvmdb01 tmp]# netdatax -h -bash: /usr/bin/netdatax: cannot execute binary file [root@wil-zvmdb01 tmp]# -- 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 more information on Linux on System z, visit http://wiki.linuxvm.org/ -- 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 more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: sles11 - adding dasd yast problem
For question 2 concerning yast2, if you're using PuTTY to connect, have you loaded the session and changed the Connection-SSH-X11 to use X11 forwarding and XDM-Authorization-1, and also started Exceed, or whatever whatever product you use to accept X11 output? |-Original Message- |From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of |Sue Sivets |Sent: Wednesday, January 06, 2010 9:18 PM |To: LINUX-390@VM.MARIST.EDU |Subject: sles11 - adding dasd yast problem | |I have just finished installing Sles 11, and now I need to add two |mini-disks. The first is read only, the second is read-write. I tried |running mkinitrd zipl like I would for sles10, but it doesn't seem to |be working. Mkinitrd is only writing 6 or 8 lines to the console (it |writes almost a screen full on sles10), and it seems to be changing the |disk identifier from dasdc dasdd to dasda or dasdb so that /etc/fstab |ends up being correct for the current ipl, but not the next. I guess |zipl is working, at least the system seems to boot. If I run mkinitrd |zipl manually, the new disks don't seem to be picked up and added to the |dasd configuration so they are avail for the next ipl. If I use |yast-hardware-dasd to activate them, then the dasd id is changed, and |the disks seem to be varied online at the next ipl. | |How do I get the dasd added and mounted at each ipl? |Can I add dasd without using yast and if so how? What commands do I need |to run? | |Problem #2 - When I try to run yast2, I get an error message that Xlib: |extension RANDR missing on display localhost:10.0 along with a bunch |of other messages. I thought I saw something about Gnome in an earlier |error message, and I did not install either Gnome of KDE since I was |doing a z/linux install, and neither of these have worked very well on |previous sles versions. yast seems to work so far, but I much prefer |yast2. | |Can anyone shed any light on either of these problems? | |Thank you | |Sue Sivets | |-- | Suzanne Sivets | Systems Programmer | Innovation Data Processing | 275 Paterson Ave | Little Falls, NJ 07424-1658 | 973-890-7300 | Fax 973-890-7147 | ssiv...@fdrinnovation.com | | | |This email (and attachments, if any) is confidential and access by |anyone other than the addressee(s) is unauthorized. We would appreciate |your notifying the sender and supp...@fdrinnovation.com immediately if |you are not the intended recipient of this message. | |-- |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
FW: sles11 - adding dasd yast problem
For question 2 concerning yast2, if you're using PuTTY to connect, have you loaded the session and changed the Connection-SSH-X11 to use X11 forwarding and XDM-Authorization-1, and also started Exceed, or whatever whatever product you use to accept X11 output? ||-Original Message- ||From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of ||Sue Sivets ||Sent: Wednesday, January 06, 2010 9:18 PM ||To: LINUX-390@VM.MARIST.EDU ||Subject: sles11 - adding dasd yast problem || ||I have just finished installing Sles 11, and now I need to add two ||mini-disks. The first is read only, the second is read-write. I tried ||running mkinitrd zipl like I would for sles10, but it doesn't seem to ||be working. Mkinitrd is only writing 6 or 8 lines to the console (it ||writes almost a screen full on sles10), and it seems to be changing the ||disk identifier from dasdc dasdd to dasda or dasdb so that /etc/fstab ||ends up being correct for the current ipl, but not the next. I guess ||zipl is working, at least the system seems to boot. If I run mkinitrd ||zipl manually, the new disks don't seem to be picked up and added to |the ||dasd configuration so they are avail for the next ipl. If I use ||yast-hardware-dasd to activate them, then the dasd id is changed, and ||the disks seem to be varied online at the next ipl. || ||How do I get the dasd added and mounted at each ipl? ||Can I add dasd without using yast and if so how? What commands do I |need ||to run? || ||Problem #2 - When I try to run yast2, I get an error message that |Xlib: ||extension RANDR missing on display localhost:10.0 along with a |bunch ||of other messages. I thought I saw something about Gnome in an earlier ||error message, and I did not install either Gnome of KDE since I was ||doing a z/linux install, and neither of these have worked very well on ||previous sles versions. yast seems to work so far, but I much prefer ||yast2. || ||Can anyone shed any light on either of these problems? || ||Thank you || ||Sue Sivets || ||-- || Suzanne Sivets || Systems Programmer || Innovation Data Processing || 275 Paterson Ave || Little Falls, NJ 07424-1658 || 973-890-7300 || Fax 973-890-7147 || ssiv...@fdrinnovation.com || || || ||This email (and attachments, if any) is confidential and access by ||anyone other than the addressee(s) is unauthorized. We would |appreciate ||your notifying the sender and supp...@fdrinnovation.com immediately if ||you are not the intended recipient of this message. || ||-- ||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: SLES 10 SP2 upgrade to SLES 10 SP3 error
To increase the size of /usr, the VM guys have added a disk for me, which has been formatted and mounted as /usrnew. I then ran the command cp -Rv --preserve /usr/* /usrnew as root from the / directory'. However, the USED space is different - 1.9G for /usr and 2.1G for /usrnew. I've looked on the web, and see that some recommend using switches -dpr or -a also. Using the --preserve switch kept the file/directory dates, but the dates on the symlink's were today's date. output of df -h: FilesystemSize Used Avail Use% Mounted on /dev/dasdb1 1.2G 158M 1016M 14% / udev 184M 200K 184M 1% /dev /dev/dasda169M 14M 52M 21% /boot /dev/dasdh1 2.3G 85M 2.3G 4% /home /dev/dasdg1 1.2G 843M 331M 72% /opt /dev/dasdc1 2.3G 1.9G 366M 84% /usr /dev/dasdd1 1.1G 321M 713M 32% /var /dev/mapper/tmpvg-tmpvol 14G 98M 14G 1% /tmp /dev/dasdq1 2.3G 33M 2.3G 2% /unused /dev/dasdp1 4.6G 2.1G 2.6G 45% /usrnew Snippet of mount: /dev/dasdc1 on /usr type reiserfs (rw,acl,user_xattr) /dev/dasdp1 on /usrnew type reiserfs (rw,acl,user_xattr) Question 1. Is cp to correct command to do the copy, and if so what are the correct switches? Beside keeping the symlinks, I'd also want to copy any files that start with ., and any other file types I may not be aware of. I also considered using tar to backup and restore the files, and possibly rsync. Question 2. I then want to rename the /usr directory to /usrold , and then rename /usrnew to /usr, and then I will update fstab and reboot. What is the correct way to do the two renames above - is it the mv command, and if so what switches would I want to use so I copy all files types and preserve dates, permissions, etc.? Question 3. Is there a command that will compare /usr and /usrnew for differences, or that will show number of files and exact space used? |-Original Message- |From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of |Mark Post |Sent: Monday, January 04, 2010 9:00 PM |To: LINUX-390@VM.MARIST.EDU |Subject: Re: SLES 10 SP2 upgrade to SLES 10 SP3 error | | On 1/4/2010 at 5:36 PM, Slaughter, Dale dslaugh...@aegonusa.com |wrote: |-snip- | What is the solution to this problem? | |You need to add more space to /usr, or remove enough packages (that |contain files in /usr). | | |Mark Post | |-- |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
FW: SLES 10 SP2 upgrade to SLES 10 SP3 error
To increase the size of /usr, the VM guys have added a disk for me, which has been formatted and mounted as /usrnew. I then ran the command cp -Rv --preserve /usr/* /usrnew as root from the / directory'. However, the USED space is different - 1.9G for /usr and 2.1G for /usrnew. I've looked on the web, and see that some recommend using switches -dpr or -a also. Using the --preserve switch kept the file/directory dates, but the dates on the symlink's were today's date. output of df -h: FilesystemSize Used Avail Use% Mounted on /dev/dasdb1 1.2G 158M 1016M 14% / udev 184M 200K 184M 1% /dev /dev/dasda169M 14M 52M 21% /boot /dev/dasdh1 2.3G 85M 2.3G 4% /home /dev/dasdg1 1.2G 843M 331M 72% /opt /dev/dasdc1 2.3G 1.9G 366M 84% /usr /dev/dasdd1 1.1G 321M 713M 32% /var /dev/mapper/tmpvg-tmpvol 14G 98M 14G 1% /tmp /dev/dasdq1 2.3G 33M 2.3G 2% /unused /dev/dasdp1 4.6G 2.1G 2.6G 45% /usrnew Snippet of mount: /dev/dasdc1 on /usr type reiserfs (rw,acl,user_xattr) /dev/dasdp1 on /usrnew type reiserfs (rw,acl,user_xattr) Question 1. Is cp to correct command to do the copy, and if so what are the correct switches? Beside keeping the symlinks, I'd also want to copy any files that start with ., and any other file types I may not be aware of. I also considered using tar to backup and restore the files, and possibly rsync. Question 2. I then want to rename the /usr directory to /usrold , and then rename /usrnew to /usr, and then I will update fstab and reboot. What is the correct way to do the two renames above - is it the mv command, and if so what switches would I want to use so I copy all files types and preserve dates, permissions, etc.? Question 3. Is there a command that will compare /usr and /usrnew for differences, or that will show number of files and exact space used? |-Original Message- |From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of |Mark Post |Sent: Monday, January 04, 2010 9:00 PM |To: LINUX-390@VM.MARIST.EDU |Subject: Re: SLES 10 SP2 upgrade to SLES 10 SP3 error | | On 1/4/2010 at 5:36 PM, Slaughter, Dale dslaugh...@aegonusa.com |wrote: |-snip- | What is the solution to this problem? | |You need to add more space to /usr, or remove enough packages (that |contain files in /usr). | | |Mark Post | |-- |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: SLES 10 SP2 upgrade to SLES 10 SP3 error
After using tar command, the diff command showed the below messages - I suspect they are OK? I didn't do the mount umount commands since I had already updated fstab with the new disk and rebooted. The dfh -h command does now show that the two files are both at 1.9G, vs. there being 0.2G difference before when using the cp command. LINUX9D:/usr # tar -clpSf - . | (cd /usrnew ; tar -xpSf - ) tar: Semantics of -l option will change in the future releases. tar: Please use --one-file-system option instead. LINUX9D:/usr # cd / LINUX9D:/ # diff -r /usr /usrnew diff: /usr/bin/X11/Xwrapper: No such file or directory diff: /usrnew/bin/X11/Xwrapper: No such file or directory File /usr/lib/rsc/keystroke.pipe is a fifo while file /usrnew/lib/rsc/keystroke.pipe is a fifo File /usr/lib/rsc/rscd.pipe is a fifo while file /usrnew/lib/rsc/rscd.pipe is a fifo File /usr/lib64/32/rsc/keystroke.pipe is a fifo while file /usrnew/lib64/32/rsc/keystroke.pipe is a fifo File /usr/lib64/32/rsc/rscd.pipe is a fifo while file /usrnew/lib64/32/rsc/rscd.pipe is a fifo diff: /usr/lib64/samba/nss_info/rfc2307.so: No such file or directory diff: /usrnew/lib64/samba/nss_info/rfc2307.so: No such file or directory diff: /usr/lib64/samba/nss_info/sfu.so: No such file or directory diff: /usrnew/lib64/samba/nss_info/sfu.so: No such file or directory diff: /usr/X11/bin/Xwrapper: No such file or directory diff: /usrnew/X11/bin/Xwrapper: No such file or directory diff: /usr/X11R6/bin/Xwrapper: No such file or directory diff: /usrnew/X11R6/bin/Xwrapper: No such file or directory LINUX9D:/ # |-Original Message- |From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of |Marcy Cortes |Sent: Wednesday, January 06, 2010 10:18 AM |To: LINUX-390@VM.MARIST.EDU |Subject: Re: SLES 10 SP2 upgrade to SLES 10 SP3 error | |Dale, I always use the incantaion found here |http://www.linuxvm.org/Info/HOWTOs/movefs.html | | |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, or take any action based on |this message or any information herein. If you have received this |message in error, please advise the sender immediately by reply e-mail |and delete this message. Thank you for your cooperation. | | |-Original Message- |From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of |Slaughter, Dale |Sent: Wednesday, January 06, 2010 8:04 AM |To: LINUX-390@VM.MARIST.EDU |Subject: Re: [LINUX-390] SLES 10 SP2 upgrade to SLES 10 SP3 error | |To increase the size of /usr, the VM guys have added a disk for me, |which has been formatted and mounted as /usrnew. I then ran the command |cp -Rv --preserve /usr/* /usrnew as root from the / directory'. |However, the USED space is different - 1.9G for /usr and 2.1G for |/usrnew. I've looked on the web, and see that some recommend using |switches -dpr or -a also. Using the --preserve switch kept the |file/directory dates, but the dates on the symlink's were today's date. | | |output of df -h: | |FilesystemSize Used Avail Use% Mounted on |/dev/dasdb1 1.2G 158M 1016M 14% / |udev 184M 200K 184M 1% /dev |/dev/dasda169M 14M 52M 21% /boot |/dev/dasdh1 2.3G 85M 2.3G 4% /home |/dev/dasdg1 1.2G 843M 331M 72% /opt |/dev/dasdc1 2.3G 1.9G 366M 84% /usr |/dev/dasdd1 1.1G 321M 713M 32% /var |/dev/mapper/tmpvg-tmpvol | 14G 98M 14G 1% /tmp |/dev/dasdq1 2.3G 33M 2.3G 2% /unused |/dev/dasdp1 4.6G 2.1G 2.6G 45% /usrnew | | | |Snippet of mount: | |/dev/dasdc1 on /usr type reiserfs (rw,acl,user_xattr) |/dev/dasdp1 on /usrnew type reiserfs (rw,acl,user_xattr) | | | | | |Question 1. Is cp to correct command to do the copy, and if so what |are the correct switches? Beside keeping the symlinks, I'd also want to |copy any files that start with ., and any other file types I may not |be aware of. I also considered using tar to backup and restore the |files, and possibly rsync. | |Question 2. I then want to rename the /usr directory to /usrold , and |then rename /usrnew to /usr, and then I will update fstab and reboot. |What is the correct way to do the two renames above - is it the mv |command, and if so what switches would I want to use so I copy all files |types and preserve dates, permissions, etc.? | |Question 3. Is there a command that will compare /usr and /usrnew for |differences, or that will show number of files and exact space used? | | | ||-Original Message- ||From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of ||Mark Post ||Sent: Monday, January 04, 2010 9:00 PM ||To: LINUX-390@VM.MARIST.EDU ||Subject: Re: SLES 10 SP2 upgrade to SLES 10 SP3 error || || On 1/4/2010 at 5:36 PM, Slaughter, Dale |dslaugh...@aegonusa.com ||wrote: ||-snip- || What
FW: SLES 10 SP2 upgrade to SLES 10 SP3 error
After using tar command, the diff command showed the below messages - I suspect they are OK? I didn't do the mount umount commands since I had already updated fstab with the new disk and rebooted. The df -h command does now show that the two files are both at 1.9G, vs. there being 0.2G difference before when using the cp command. LINUX9D:/usr # tar -clpSf - . | (cd /usrnew ; tar -xpSf - ) tar: Semantics of -l option will change in the future releases. tar: Please use --one-file-system option instead. LINUX9D:/usr # cd / LINUX9D:/ # diff -r /usr /usrnew diff: /usr/bin/X11/Xwrapper: No such file or directory diff: /usrnew/bin/X11/Xwrapper: No such file or directory File /usr/lib/rsc/keystroke.pipe is a fifo while file /usrnew/lib/rsc/keystroke.pipe is a fifo File /usr/lib/rsc/rscd.pipe is a fifo while file /usrnew/lib/rsc/rscd.pipe is a fifo File /usr/lib64/32/rsc/keystroke.pipe is a fifo while file /usrnew/lib64/32/rsc/keystroke.pipe is a fifo File /usr/lib64/32/rsc/rscd.pipe is a fifo while file /usrnew/lib64/32/rsc/rscd.pipe is a fifo diff: /usr/lib64/samba/nss_info/rfc2307.so: No such file or directory diff: /usrnew/lib64/samba/nss_info/rfc2307.so: No such file or directory diff: /usr/lib64/samba/nss_info/sfu.so: No such file or directory diff: /usrnew/lib64/samba/nss_info/sfu.so: No such file or directory diff: /usr/X11/bin/Xwrapper: No such file or directory diff: /usrnew/X11/bin/Xwrapper: No such file or directory diff: /usr/X11R6/bin/Xwrapper: No such file or directory diff: /usrnew/X11R6/bin/Xwrapper: No such file or directory LINUX9D:/ # ||-Original Message- ||From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of ||Marcy Cortes ||Sent: Wednesday, January 06, 2010 10:18 AM ||To: LINUX-390@VM.MARIST.EDU ||Subject: Re: SLES 10 SP2 upgrade to SLES 10 SP3 error || ||Dale, I always use the incantaion found here ||http://www.linuxvm.org/Info/HOWTOs/movefs.html || || ||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, or take any action based |on ||this message or any information herein. If you have received this ||message in error, please advise the sender immediately by reply e-mail ||and delete this message. Thank you for your cooperation. || || ||-Original Message- ||From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of ||Slaughter, Dale ||Sent: Wednesday, January 06, 2010 8:04 AM ||To: LINUX-390@VM.MARIST.EDU ||Subject: Re: [LINUX-390] SLES 10 SP2 upgrade to SLES 10 SP3 error || ||To increase the size of /usr, the VM guys have added a disk for me, ||which has been formatted and mounted as /usrnew. I then ran the |command ||cp -Rv --preserve /usr/* /usrnew as root from the / directory'. ||However, the USED space is different - 1.9G for /usr and 2.1G for ||/usrnew. I've looked on the web, and see that some recommend using ||switches -dpr or -a also. Using the --preserve switch kept the ||file/directory dates, but the dates on the symlink's were today's date. || || ||output of df -h: || ||FilesystemSize Used Avail Use% Mounted on ||/dev/dasdb1 1.2G 158M 1016M 14% / ||udev 184M 200K 184M 1% /dev ||/dev/dasda169M 14M 52M 21% /boot ||/dev/dasdh1 2.3G 85M 2.3G 4% /home ||/dev/dasdg1 1.2G 843M 331M 72% /opt ||/dev/dasdc1 2.3G 1.9G 366M 84% /usr ||/dev/dasdd1 1.1G 321M 713M 32% /var ||/dev/mapper/tmpvg-tmpvol || 14G 98M 14G 1% /tmp ||/dev/dasdq1 2.3G 33M 2.3G 2% /unused ||/dev/dasdp1 4.6G 2.1G 2.6G 45% /usrnew || || || ||Snippet of mount: || ||/dev/dasdc1 on /usr type reiserfs (rw,acl,user_xattr) ||/dev/dasdp1 on /usrnew type reiserfs (rw,acl,user_xattr) || || || || || ||Question 1. Is cp to correct command to do the copy, and if so what ||are the correct switches? Beside keeping the symlinks, I'd also want |to ||copy any files that start with ., and any other file types I may not ||be aware of. I also considered using tar to backup and restore the ||files, and possibly rsync. || ||Question 2. I then want to rename the /usr directory to /usrold , and ||then rename /usrnew to /usr, and then I will update fstab and reboot. ||What is the correct way to do the two renames above - is it the mv ||command, and if so what switches would I want to use so I copy all |files ||types and preserve dates, permissions, etc.? || ||Question 3. Is there a command that will compare /usr and /usrnew for ||differences, or that will show number of files and exact space used? || || || |||-Original Message- |||From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of |||Mark Post |||Sent: Monday, January 04, 2010 9:00 PM |||To: LINUX-390@VM.MARIST.EDU |||Subject: Re: SLES 10 SP2 upgrade to SLES 10 SP3 error ||| ||| On 1/4/2010
Re: SLES 10 SP2 upgrade to SLES 10 SP3 error
Thanks to everyone who's replied. I followed the process that was sent in http://www.linuxvm.org/Info/HOWTOs/movefs.html with the following deviation: I had already used yast to activate and format the disk as ReiserFS, and assigned it a mountpoint of /usrnew. I've followed steps 4 and 5. The yast process had already updated /etc/fstab to include the new disk with the /usrnew mount. For step 7, after the tar command was done, I edited /etc/fstab to change the mountpoint of /usrnew to /usr, and changed the old /usr to /usrsp2. I then rebooted. df -h doesn't show /usrsp2, even though there was an entry for it in /etc/fstab. I then check the partitioner in yast and there is an * besides it name in the column that has the mountpoint name. The /usr below is the new /usr that was just created. The old /usr, which I had updated /etc/fstab with a mountpoint of /usrsp2 doesn't show up under mount either. Question 1: What is happening that I can't see the old /usr, which I thought would have been mounted under /usrsp2? Question 2: Is everything OK? Question 3: Why do I still see /usrnew, which is not mounted? It's possible that when I was trying a 'mv yesterday it was created by me. Question 4: I'm not sure of the purpose of step 8 in the HOWTO. I did the telinit 1 and then the umount comes back with 'umount: /usr: device is busy', which I think subsequently killed the system. If the old /usr is on a disk that isn't mounted, is it necessary to delete what's on it, since the disk will probably be return to the VM guys for other purposes. Question 5: Is everything OK as it now sits? df -h: FilesystemSize Used Avail Use% Mounted on /dev/dasdb1 1.2G 158M 1016M 14% / udev 184M 200K 184M 1% /dev /dev/dasda169M 14M 52M 21% /boot /dev/dasdh1 2.3G 85M 2.3G 4% /home /dev/dasdg1 1.2G 843M 331M 72% /opt /dev/dasdd1 1.1G 323M 711M 32% /var /dev/mapper/tmpvg-tmpvol 14G 98M 14G 1% /tmp /dev/dasdq1 2.3G 33M 2.3G 2% /unused /dev/dasdp1 4.6G 1.9G 2.8G 41% /usr mount: /dev/dasdb1 on / type reiserfs (rw,acl,user_xattr) proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) debugfs on /sys/kernel/debug type debugfs (rw) udev on /dev type tmpfs (rw) devpts on /dev/pts type devpts (rw,mode=0620,gid=5) /dev/dasda1 on /boot type ext2 (rw,acl,user_xattr) /dev/dasdh1 on /home type reiserfs (rw,acl,user_xattr) /dev/dasdg1 on /opt type reiserfs (rw,acl,user_xattr) /dev/dasdd1 on /var type reiserfs (rw,acl,user_xattr) /dev/mapper/tmpvg-tmpvol on /tmp type reiserfs (rw,acl,user_xattr) /dev/dasdq1 on /unused type reiserfs (rw,acl,user_xattr) /dev/dasdp1 on /usr type reiserfs (rw,acl,user_xattr) l command: total 33 drwxr-xr-x 30 root root 728 2010-01-06 13:40 ./ drwxr-xr-x 30 root root 728 2010-01-06 13:40 ../ drwxr-xr-x 2 root root 2384 2009-04-23 15:10 bin/ drwxr-xr-x 4 root root 4096 2010-01-06 13:40 boot/ drwx-- 8 20631 uuxstaff 584 2009-04-23 15:17 candle/ drwxr-xr-x 9 root root 2800 2010-01-06 13:40 dev/ drwxr-xr-x 81 root root 6928 2010-01-06 13:40 etc/ drwxr-xr-x 16 root root 400 2009-10-23 05:32 home/ lrwxrwxrwx 1 root root5 2009-05-01 13:35 homedir - /home/ drwxr-xr-x 10 root root 3808 2009-04-23 09:49 lib/ drwxr-xr-x 5 root root 4720 2009-11-11 11:49 lib64/ drwxr-xr-x 5 root root 128 2009-06-19 10:10 local/ drwxr-xr-x 2 root root 48 2009-06-10 11:39 .mc/ drwxr-xr-x 2 root root 48 2007-05-03 11:05 media/ drwxr-xr-x 3 root root 72 2009-04-23 10:46 mnt/ drwxr-xr-x 11 root root 248 2009-08-27 08:26 opt/ dr-xr-xr-x 68 root root0 2010-01-06 13:40 proc/ drwx-- 12 root root 536 2010-01-06 11:23 root/ drwxr-xr-x 3 root root 9568 2009-05-07 07:14 sbin/ drwxr-xr-x 4 root root 96 2009-04-23 09:45 srv/ drwxr-xr-x 3 root root 72 2009-05-06 20:31 stage/ drwxr-xr-x 2 root root 48 2009-05-11 10:40 swap/ drwxr-xr-x 3 root root 72 2009-05-06 15:38 .swdis/ drwxr-xr-x 11 root root0 2010-01-06 13:40 sys/ drwxrwxrwt 24 root root 1288 2010-01-06 14:00 tmp/ drwxr-xr-x 4 root root 80 2010-01-05 15:54 unused/ drwxr-xr-x 16 root root 424 2009-04-23 11:24 usr/ drwxr-xr-x 2 root root 48 2010-01-05 15:08 usrnew/ drwxr-xr-x 16 root root 392 2009-09-02 11:52 var/ |-Original Message- |From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of |Scott Rohling |Sent: Wednesday, January 06, 2010 10:55 AM |To: LINUX-390@VM.MARIST.EDU |Subject: Re: SLES 10 SP2 upgrade to SLES 10 SP3 error | |Good points .. you're right - that would have been messy. | |And actually - since these are mount points -- no rename is really |necessary |-- just mount the correct device under /usr. | |Scot | |On Wed, Jan 6, 2010 at 9:47 AM, Kim Goldenberg
FW: SLES 10 SP2 upgrade to SLES 10 SP3 error
Thanks to everyone who's replied. I followed the process that was sent in http://www.linuxvm.org/Info/HOWTOs/movefs.html with the following deviation: I had already used yast to activate and format the disk as ReiserFS, and assigned it a mountpoint of /usrnew. I've followed steps 4 and 5. The yast process had already updated /etc/fstab to include the new disk with the /usrnew mount. For step 7, after the tar command was done, I edited /etc/fstab to change the mountpoint of /usrnew to /usr, and changed the old /usr to /usrsp2. I then rebooted. df -h doesn't show /usrsp2, even though there was an entry for it in /etc/fstab. I then check the partitioner in yast and there is an * besides it name in the column that has the mountpoint name. The /usr below is the new /usr that was just created. The old /usr, which I had updated /etc/fstab with a mountpoint of /usrsp2 doesn't show up under mount either. Question 1: What is happening that I can't see the old /usr, which I thought would have been mounted under /usrsp2? Question 2: Is everything OK? Question 3: Why do I still see /usrnew, which is not mounted? It's possible that when I was trying a 'mv yesterday it was created by me. Question 4: I'm not sure of the purpose of step 8 in the HOWTO. I did the telinit 1 and then the umount comes back with 'umount: /usr: device is busy', which I think subsequently killed the system. If the old /usr is on a disk that isn't mounted, is it necessary to delete what's on it, since the disk will probably be return to the VM guys for other purposes. Question 5: Is everything OK as it now sits? df -h: FilesystemSize Used Avail Use% Mounted on /dev/dasdb1 1.2G 158M 1016M 14% / udev 184M 200K 184M 1% /dev /dev/dasda169M 14M 52M 21% /boot /dev/dasdh1 2.3G 85M 2.3G 4% /home /dev/dasdg1 1.2G 843M 331M 72% /opt /dev/dasdd1 1.1G 323M 711M 32% /var /dev/mapper/tmpvg-tmpvol 14G 98M 14G 1% /tmp /dev/dasdq1 2.3G 33M 2.3G 2% /unused /dev/dasdp1 4.6G 1.9G 2.8G 41% /usr mount: /dev/dasdb1 on / type reiserfs (rw,acl,user_xattr) proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) debugfs on /sys/kernel/debug type debugfs (rw) udev on /dev type tmpfs (rw) devpts on /dev/pts type devpts (rw,mode=0620,gid=5) /dev/dasda1 on /boot type ext2 (rw,acl,user_xattr) /dev/dasdh1 on /home type reiserfs (rw,acl,user_xattr) /dev/dasdg1 on /opt type reiserfs (rw,acl,user_xattr) /dev/dasdd1 on /var type reiserfs (rw,acl,user_xattr) /dev/mapper/tmpvg-tmpvol on /tmp type reiserfs (rw,acl,user_xattr) /dev/dasdq1 on /unused type reiserfs (rw,acl,user_xattr) /dev/dasdp1 on /usr type reiserfs (rw,acl,user_xattr) l command: total 33 drwxr-xr-x 30 root root 728 2010-01-06 13:40 ./ drwxr-xr-x 30 root root 728 2010-01-06 13:40 ../ drwxr-xr-x 2 root root 2384 2009-04-23 15:10 bin/ drwxr-xr-x 4 root root 4096 2010-01-06 13:40 boot/ drwx-- 8 20631 uuxstaff 584 2009-04-23 15:17 candle/ drwxr-xr-x 9 root root 2800 2010-01-06 13:40 dev/ drwxr-xr-x 81 root root 6928 2010-01-06 13:40 etc/ drwxr-xr-x 16 root root 400 2009-10-23 05:32 home/ lrwxrwxrwx 1 root root5 2009-05-01 13:35 homedir - /home/ drwxr-xr-x 10 root root 3808 2009-04-23 09:49 lib/ drwxr-xr-x 5 root root 4720 2009-11-11 11:49 lib64/ drwxr-xr-x 5 root root 128 2009-06-19 10:10 local/ drwxr-xr-x 2 root root 48 2009-06-10 11:39 .mc/ drwxr-xr-x 2 root root 48 2007-05-03 11:05 media/ drwxr-xr-x 3 root root 72 2009-04-23 10:46 mnt/ drwxr-xr-x 11 root root 248 2009-08-27 08:26 opt/ dr-xr-xr-x 68 root root0 2010-01-06 13:40 proc/ drwx-- 12 root root 536 2010-01-06 11:23 root/ drwxr-xr-x 3 root root 9568 2009-05-07 07:14 sbin/ drwxr-xr-x 4 root root 96 2009-04-23 09:45 srv/ drwxr-xr-x 3 root root 72 2009-05-06 20:31 stage/ drwxr-xr-x 2 root root 48 2009-05-11 10:40 swap/ drwxr-xr-x 3 root root 72 2009-05-06 15:38 .swdis/ drwxr-xr-x 11 root root0 2010-01-06 13:40 sys/ drwxrwxrwt 24 root root 1288 2010-01-06 14:00 tmp/ drwxr-xr-x 4 root root 80 2010-01-05 15:54 unused/ drwxr-xr-x 16 root root 424 2009-04-23 11:24 usr/ drwxr-xr-x 2 root root 48 2010-01-05 15:08 usrnew/ drwxr-xr-x 16 root root 392 2009-09-02 11:52 var/ ||-Original Message- ||From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of ||Scott Rohling ||Sent: Wednesday, January 06, 2010 10:55 AM ||To: LINUX-390@VM.MARIST.EDU ||Subject: Re: SLES 10 SP2 upgrade to SLES 10 SP3 error || ||Good points .. you're right - that would have been messy. || ||And actually - since these are mount points -- no rename is really ||necessary ||-- just mount the correct device under /usr. || ||Scot || ||On Wed, Jan 6, 2010 at 9:47 AM,
Re: SLES 10 SP2 upgrade to SLES 10 SP3 error
The directories existing before the mount makes sense, and explains what I'm seeing - I knew that at one time. Thanks to everyone that replied - I've learned some things! Output of lsdasd, 0202 was the old /usr, 0208 is the new /usr 0.0.0200(ECKD) at ( 94: 0) is dasda : n/f 0.0.0201(ECKD) at ( 94: 4) is dasdb : n/f 0.0.0202(ECKD) at ( 94: 8) is dasdc : n/f 0.0.0203(ECKD) at ( 94: 12) is dasdd : n/f 0.0.0204(ECKD) at ( 94: 16) is dasde : n/f 0.0.0205(ECKD) at ( 94: 20) is dasdf : n/f 0.0.0206(ECKD) at ( 94: 24) is dasdg : n/f 0.0.0207(ECKD) at ( 94: 28) is dasdh : n/f 0.0.0b00(ECKD) at ( 94: 32) is dasdi : n/f 0.0.0b01(ECKD) at ( 94: 36) is dasdj : n/f 0.0.0104(FBA ) at ( 94: 40) is dasdk : n/f 0.0.0191(ECKD) at ( 94: 44) is dasdl : n/f 0.0.191c(ECKD) at ( 94: 48) is dasdm : n/f 0.0.fb01(ECKD) at ( 94: 52) is dasdn : n/f 0.0.fb00(ECKD) at ( 94: 56) is dasdo : n/f 0.0.0208(ECKD) at ( 94: 60) is dasdp : n/f 0.0.0209(ECKD) at ( 94: 64) is dasdq : n/f /etc/fstab looks like: /dev/disk/by-path/ccw-0.0.0201-part1 / reiserfs acl,user_xattr 1 1 /dev/disk/by-path/ccw-0.0.0200-part1 /boot ext2acl,user_xattr 1 2 /dev/disk/by-path/ccw-0.0.0207-part1 /home reiserfs acl,user_xattr 1 2 /dev/disk/by-path/ccw-0.0.0206-part1 /optreiserfs acl,user_xattr 1 2 /dev/disk/by-path/ccw-0.0.0202-part1 /usrsp2 reiserfs acl,user_xattr 1 2 /dev/disk/by-path/ccw-0.0.0203-part1 /varreiserfs acl,user_xattr 1 2 proc/proc procdefaults 0 0 sysfs /syssysfs noauto 0 0 debugfs /sys/kernel/debug debugfs noauto 0 0 devpts /dev/ptsdevpts mode=0620,gid=5 0 0 /dev/tmpvg/tmpvol/tmp reiserfs acl,user_xattr1 2 /dev/disk/by-path/ccw-0.0.0204-part1 swap swap pri=50 0 0 /dev/dasdm1 swap swap pri=100 0 0 /dev/disk/by-path/ccw-0.0.0209-part1 /unused reiserfs acl,user_xattr1 2 /dev/disk/by-path/ccw-0.0.0208-part1 /usr reiserfs acl,user_xattr1 2 |-Original Message- |From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of |Scott Rohling |Sent: Wednesday, January 06, 2010 2:50 PM |To: LINUX-390@VM.MARIST.EDU |Subject: Re: SLES 10 SP2 upgrade to SLES 10 SP3 error | |1) You're old /usr showed up as dasdc1 on your previous posts.. What |does |lsdasd and cat /etc/fstab look like? Also - does the directory /usrsp2 |exist? It must before it can be mounted to. | |2) It looks like it :-) | |3) You had to create /usrnew directory to mount to it ... now that |you |don't need it - you need to 'rm -r /usrnew' to get rid of it. Do an ls |/usrnew to make sure nothing's under it. | |4) That's to unmount/remount things like /usr which will show as busy |if |you try and unmount them at higher init levels. A reboot works just as |well - if you have /etc/fstab setup correctly. | |5) See #2 | | |Scott | |On Wed, Jan 6, 2010 at 1:21 PM, Slaughter, Dale |dslaugh...@aegonusa.comwrote: | | Thanks to everyone who's replied. I followed the process that was |sent in | http://www.linuxvm.org/Info/HOWTOs/movefs.html | with the following deviation: I had already used yast to activate and | format the disk as ReiserFS, and assigned it a mountpoint of /usrnew. |I've | followed steps 4 and 5. The yast process had already updated |/etc/fstab to | include the new disk with the /usrnew mount. For step 7, after the |tar | command was done, I edited /etc/fstab to change the mountpoint of |/usrnew to | /usr, and changed the old /usr to /usrsp2. I then rebooted. | | df -h doesn't show /usrsp2, even though there was an entry for it in | /etc/fstab. I then check the partitioner in yast and there is an * |besides | it name in the column that has the mountpoint name. The /usr below is |the | new /usr that was just created. The old /usr, which I had updated | /etc/fstab with a mountpoint of /usrsp2 doesn't show up under mount | either. | | Question 1: What is happening that I can't see the old /usr, which I | thought would have been mounted under /usrsp2? | | Question 2: Is everything OK? | | Question 3: Why do I still see /usrnew, which is not mounted? It's | possible that when I was trying a 'mv yesterday it was created by me. | | Question 4: I'm not sure of the purpose of step 8 in the HOWTO. I |did the | telinit 1 and then the umount comes back with 'umount: /usr: device |is | busy', which I think subsequently killed the system. If the old /usr |is on | a disk that isn't mounted, is it necessary to delete what's on it, |since the | disk will probably be return to the VM guys for other purposes. | | Question 5: Is everything OK as it now sits? | | | | df -h: | | FilesystemSize Used Avail Use% Mounted on | /dev/dasdb1 1.2G 158M 1016M 14% / | udev 184M 200K 184M 1
FW: SLES 10 SP2 upgrade to SLES 10 SP3 error
The directories existing before the mount makes sense, and explains what I'm seeing. Thanks to everyone that replied - I've learned some things! Output of lsdasd, 0202 was the old /usr, 0208 is the new /usr 0.0.0200(ECKD) at ( 94: 0) is dasda : n/f 0.0.0201(ECKD) at ( 94: 4) is dasdb : n/f 0.0.0202(ECKD) at ( 94: 8) is dasdc : n/f 0.0.0203(ECKD) at ( 94: 12) is dasdd : n/f 0.0.0204(ECKD) at ( 94: 16) is dasde : n/f 0.0.0205(ECKD) at ( 94: 20) is dasdf : n/f 0.0.0206(ECKD) at ( 94: 24) is dasdg : n/f 0.0.0207(ECKD) at ( 94: 28) is dasdh : n/f 0.0.0b00(ECKD) at ( 94: 32) is dasdi : n/f 0.0.0b01(ECKD) at ( 94: 36) is dasdj : n/f 0.0.0104(FBA ) at ( 94: 40) is dasdk : n/f 0.0.0191(ECKD) at ( 94: 44) is dasdl : n/f 0.0.191c(ECKD) at ( 94: 48) is dasdm : n/f 0.0.fb01(ECKD) at ( 94: 52) is dasdn : n/f 0.0.fb00(ECKD) at ( 94: 56) is dasdo : n/f 0.0.0208(ECKD) at ( 94: 60) is dasdp : n/f 0.0.0209(ECKD) at ( 94: 64) is dasdq : n/f /etc/fstab looks like: /dev/disk/by-path/ccw-0.0.0201-part1 / reiserfs acl,user_xattr 1 1 /dev/disk/by-path/ccw-0.0.0200-part1 /boot ext2acl,user_xattr 1 2 /dev/disk/by-path/ccw-0.0.0207-part1 /home reiserfs acl,user_xattr 1 2 /dev/disk/by-path/ccw-0.0.0206-part1 /optreiserfs acl,user_xattr 1 2 /dev/disk/by-path/ccw-0.0.0202-part1 /usrsp2 reiserfs acl,user_xattr 1 2 /dev/disk/by-path/ccw-0.0.0203-part1 /varreiserfs acl,user_xattr 1 2 proc/proc procdefaults 0 0 sysfs /syssysfs noauto 0 0 debugfs /sys/kernel/debug debugfs noauto 0 0 devpts /dev/ptsdevpts mode=0620,gid=5 0 0 /dev/tmpvg/tmpvol/tmp reiserfs acl,user_xattr 1 2 /dev/disk/by-path/ccw-0.0.0204-part1 swap swap pri=50 0 0 /dev/dasdm1 swap swap pri=100 0 0 /dev/disk/by-path/ccw-0.0.0209-part1 /unused reiserfs acl,user_xattr1 2 /dev/disk/by-path/ccw-0.0.0208-part1 /usr reiserfs acl,user_xattr1 2 ||-Original Message- ||From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of ||Scott Rohling ||Sent: Wednesday, January 06, 2010 2:50 PM ||To: LINUX-390@VM.MARIST.EDU ||Subject: Re: SLES 10 SP2 upgrade to SLES 10 SP3 error || ||1) You're old /usr showed up as dasdc1 on your previous posts.. What ||does ||lsdasd and cat /etc/fstab look like? Also - does the directory /usrsp2 ||exist? It must before it can be mounted to. || ||2) It looks like it :-) || ||3) You had to create /usrnew directory to mount to it ... now that ||you ||don't need it - you need to 'rm -r /usrnew' to get rid of it. Do an |ls ||/usrnew to make sure nothing's under it. || ||4) That's to unmount/remount things like /usr which will show as busy ||if ||you try and unmount them at higher init levels. A reboot works just |as ||well - if you have /etc/fstab setup correctly. || ||5) See #2 || || ||Scott || ||On Wed, Jan 6, 2010 at 1:21 PM, Slaughter, Dale ||dslaugh...@aegonusa.comwrote: || || Thanks to everyone who's replied. I followed the process that was ||sent in || http://www.linuxvm.org/Info/HOWTOs/movefs.html || with the following deviation: I had already used yast to activate |and || format the disk as ReiserFS, and assigned it a mountpoint of /usrnew. ||I've || followed steps 4 and 5. The yast process had already updated ||/etc/fstab to || include the new disk with the /usrnew mount. For step 7, after the ||tar || command was done, I edited /etc/fstab to change the mountpoint of ||/usrnew to || /usr, and changed the old /usr to /usrsp2. I then rebooted. || || df -h doesn't show /usrsp2, even though there was an entry for it |in || /etc/fstab. I then check the partitioner in yast and there is an * ||besides || it name in the column that has the mountpoint name. The /usr below |is ||the || new /usr that was just created. The old /usr, which I had updated || /etc/fstab with a mountpoint of /usrsp2 doesn't show up under mount || either. || || Question 1: What is happening that I can't see the old /usr, which I || thought would have been mounted under /usrsp2? || || Question 2: Is everything OK? || || Question 3: Why do I still see /usrnew, which is not mounted? It's || possible that when I was trying a 'mv yesterday it was created by |me. || || Question 4: I'm not sure of the purpose of step 8 in the HOWTO. I ||did the || telinit 1 and then the umount comes back with 'umount: /usr: device ||is || busy', which I think subsequently killed the system. If the old /usr ||is on || a disk that isn't mounted, is it necessary to delete what's on it, ||since the || disk will probably be return to the VM guys for other purposes. || || Question 5: Is everything OK as it now sits? || || || || df -h: || || FilesystemSize Used Avail Use% Mounted on || /dev/dasdb1 1.2G 158M 1016M 14% / || udev
SLES 10 SP2 upgrade to SLES 10 SP3 error
I'm attempting to update SLES 10 SP2 to SLES 10 SP3. The DVD ISOs have been downloaded to a server, and I can get the update to start. However, during package installation I get an Installation of package /suse/s390x/kernel-source-2.6.16.60-0.54.5.s390x.rpm failed with details of installing package lernel-source-2.6.16.60-0.54.5 needs 304MB on the /mnt/usr filesystem I restored the image back to SLES 10 SP2 and restarted the upgrade. I then opened a second PuTTY session and looked at the filesystems, and saw /mnt/usr had 364M available. inst-sys:/mnt/usr # df -h FilesystemSize Used Avail Use% Mounted on /dev/loop0259M 259M 0 100% /mounts/instsys /dev/dasdi1 1.2G 158M 1016M 14% /mnt /dev/dasdk1 1.1G 280M 753M 28% /mnt/var /dev/dasdh169M 14M 52M 21% /mnt/boot /dev/dasdo1 2.3G 85M 2.3G 4% /mnt/home /dev/dasdn1 1.2G 843M 331M 72% /mnt/opt /dev/dasdj1 2.3G 1.9G 364M 85% /mnt/usr /dev/mapper/tmpvg-tmpvol 14G 98M 14G 1% /mnt/tmp inst-sys:/mnt/usr # later, before the update failed again, the /mnt/usr space was down to ~151M. What is the solution to this problem? Dale Slaughter AEGON Information Technology / Transaction Processing | phone 319.355.6277 | e-mail dslaugh...@aegonusa.com -- 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
SLES 10 SP3 upgrade paths clarification
Has anyone attempted upgrading SLES 10 SP2 to SLES 10 SP3? I've noticed that the SLES 10 SP3 README says For the installation server you need at least SLES 9 SP4 or SLES 10 SP2 with all patches installed. Looks like that means that only SLES 9 SP4 or SLES 10 SP2 can be upgraded to SLES 10 SP3? And how can I tell if all patches have been installed? I suspect that the SLES 10 SP2 images haven't had any fixes/patches installed since SLES 10 SP2 images were created. Wouldn't the SLES 10 SP3 replace anything that had patches? What happens if SLES 10 SP2 doesn't have all patches installed? And this means that we cannot upgrade from SLES 9 SP3 to SLES 10 SP3 at all? -- 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
