Re: SwapCache
On Thu, 2 Jun 2011 05:43:14 -0700 Dave Czajkowski wrote: > Is there a way to disable or limit the amount of SwapCache? I > understand it's function, but the double allocation of these pages is > causing my low memory alerts to trip. This would imply to me that your triggers are poorly set. Would you care to expand on "the double allocation of these pages" ?. My understanding is that the swap-cache is merely a different "state" of pages in the page-cache. > I can remove the swap copy with a swapoff/swapon. Is there a more > elegant way to remove? Not that I've found. Past discussions on LKML have elicited little (no) sympathy for including controls for specific memory controls. Perhaps Allan Cox will pass by again and offer an opinion. Shane ... -- 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: bad entry in fstab
>>> On 6/2/2011 at 03:21 PM, Scott Rohling wrote: > You also want to make very sure that the system you are on does not have the > same LVM name in use. It's just not worth messing with if it does.. (imo). Which is why having a rescue system around with either no LVM in use, or with different VG names is nice. 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 more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: bad entry in fstab
well - then you have to link all of the disks that are part of the LVM - so rinse and repeat the previous steps. You also want to make very sure that the system you are on does not have the same LVM name in use. It's just not worth messing with if it does.. (imo). But - if you have all the disks linked and activated: pvscan vgscan vgchange -ay volume_group(make volume_group active) mount /dev/volume_group/logical_volume /mnt Scott Rohling On Thu, Jun 2, 2011 at 1:05 PM, Bauer, Bobby (NIH/CIT) [E] < baue...@mail.nih.gov> wrote: > Thanks Scott, could I ask for the steps for LVM? > > Bobby Bauer > Center for Information Technology > National Institutes of Health > Bethesda, MD 20892-5628 > 301-594-7474 > > > > -Original Message- > From: Scott Rohling [mailto:scott.rohl...@gmail.com] > Sent: Thursday, June 02, 2011 2:59 PM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: bad entry in fstab > > chccwdev -e 2201 (activate it) > lsdasd (find out what dasd 2201 is) > mount /dev/dasdx1 /mnt > > This assumes 2201 contains a single filesystem.. if it's part of an LVM, > there's more to all this.. > > Scott Rohling > > On Thu, Jun 2, 2011 at 12:51 PM, Bauer, Bobby (NIH/CIT) [E] < > baue...@mail.nih.gov> wrote: > > > Aria, please explain further because I don't know how to do this. > > First I would: > > vmcp link servername 201 2201 mw password > > > > then what? > > > > > > Bobby Bauer > > Center for Information Technology > > National Institutes of Health > > Bethesda, MD 20892-5628 > > 301-594-7474 > > > > > > -Original Message- > > From: Aria Bamdad [mailto:a...@bsc.gwu.edu] > > Sent: Thursday, June 02, 2011 1:50 PM > > To: LINUX-390@VM.MARIST.EDU > > Subject: Re: bad entry in fstab > > > > Or just link the VM minidisk with the root file system for this failing > > system as R/W on an working linux system, let's call that the maintenance > > system. On the maintenance system, enable and mount that temporary > volume. > > Now you have a fully functional linux system and can use any tool you > like > > to correct the typo. > > > > Unmount, release/detach the minidisk when done and then boot the original > > failing system. > > > > Aria > > -Original Message- > > From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of > > Bauer, > > Bobby (NIH/CIT) [E] > > Sent: Thursday, June 02, 2011 1:32 PM > > To: LINUX-390@VM.MARIST.EDU > > Subject: Re: bad entry in fstab > > > > Thanks to everybody for help, especially for the remount command. > > > > Never did find a way to send Control-D > > > > The sed command worked perfect when I tested it on a running system but > > would not work from the maintenance mode. I kept getting the > "Unterminated > > `s'" error and it looked like the # was causing a problem. We escaped the > # > > like this \# and sed added a new line above the LogVol08 line. One of the > > guys said we should just use sed to delete the line and sure enough, we > > deleted the bad line in fstab and was able to ipl it. > > > > I think I learned my lesson to make backups no matter how simple a change > > it > > is. > > > > Bobby Bauer > > Center for Information Technology > > National Institutes of Health > > Bethesda, MD 20892-5628 > > 301-594-7474 > > > > > > > > -Original Message- > > From: Brent Kincer [mailto:dev.bkin...@gmail.com] > > Sent: Thursday, June 02, 2011 12:19 PM > > To: LINUX-390@VM.MARIST.EDU > > Subject: Re: bad entry in fstab > > > > In case you're not using IUCV terminals and don't have access to > something > > like 'vi', just use sed to comment out the offending line and reboot. > > > > Would go something like this: > > mount -o remount,rw / > > sed -i 's/.*LogVol08.*/#&/g' /etc/fstab > > shutdown -r now > > > > That sed statement will comment out any line containing LogVol08 in > > /etc/fstab. Correct your typo after the reboot. > > > > Hope this helps! > > > > On , Rogério Soares wrote: > > > do a CTRL+D, you will got aa single user mode,, just correct you > > > > > /etc/fstab and reboot :) > > > > > > > > > > > > > > > > > On Thu, Jun 2, 2011 at 12:55 PM, Bauer, Bobby (NIH/CIT) [E] > > > baue...@mail.nih.gov> wrote: > > > > > > > > > > I made a typo when I added a new logical volume to fstab, I > misspelled > > > the > > > > > > logical volume mane. The reboot fails with: > > > > > > > > > > > > [/sbin/fsck.ext4 (1) -- /LAData] fsck.ext4 -a > > > > > > /dev/mapper/vg_labarc-LogVol08 > > > > > > fsck.ext4: No such file or directory while trying to open > > > > > > /dev/mapper/vg_labarc-LogVol08 > > > > > > /dev/mapper/vg_labarc-LogVol08: > > > > > > > > > > > > The superblock could not be read or does not describe a correct ext2 > > > > > > filesystem. If the device is valid and it really contains an ext2 > > > > > > filesystem (and not swap or ufs or something else), then the > superblock > > > > > > is corrupt, and you might try running e2fsck with an alternate > > > superblock: > > > > > > e2fsck -b 8193 > > > > > > > > > > > >
Re: bad entry in fstab
> I made a typo when I added a new logical volume to fstab, ... It's a common and easy mistake. Here's a tip ... before rebooting, if there have been changes to /etc/fstab, then do this: mount -a It will cause the system to [re]examine /etc/fstab and try to mount everything which would be mounted at boot time. It will let you know if it doesn't like something. Pass it on. -- R; <>< Rick Troth Velocity Software http://www.velocitysoftware.com/ On Thu, Jun 2, 2011 at 11:55, Bauer, Bobby (NIH/CIT) [E] wrote: > I made a typo when I added a new logical volume to fstab, I misspelled the > logical volume mane. The reboot fails with: > > [/sbin/fsck.ext4 (1) -- /LAData] fsck.ext4 -a /dev/mapper/vg_labarc-LogVol08 > fsck.ext4: No such file or directory while trying to open > /dev/mapper/vg_labarc-LogVol08 > /dev/mapper/vg_labarc-LogVol08: > > The superblock could not be read or does not describe a correct ext2 > filesystem. If the device is valid and it really contains an ext2 > filesystem (and not swap or ufs or something else), then the superblock > is corrupt, and you might try running e2fsck with an alternate superblock: > e2fsck -b 8193 > > [FAILED] > > *** An error occurred during the file system check. > *** Dropping you to a shell; the system will reboot > *** when you leave the shell. > *** Warning -- SELinux is active > *** Disabling security enforcement for system recovery. > *** Run 'setenforce 1' to reenable. > Give root password for maintenance > (or type Control-D to continue): > > > If I give it the root password, the filesystem is read only. Not sure what > the Control-D will do for me but I don't seem to be able to pass it to the > system anyway. Any suggestions how to fix fstab without rebuilding the > system? Or some other method? > > Thanks > Bobby Bauer > Center for Information Technology > National Institutes of Health > Bethesda, MD 20892-5628 > 301-594-7474 > > > > -- > 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: bad entry in fstab
Bobby, First make sure the problem server is down and logged off to make sure the disks are not linked and are not in use in write mode anywhere else. You don't want to link to a minidisk in write mode from more than one place. So, on SLES 11, you can do this: vmcp link deadserver 201 2201 w password dasd_configure 0.0.2201 1 0 mount /dev/disk/by-path/ccw-0.0.2201-part1 /mnt/somedirectory fix the problem, then unmount and release the disk. umount /dev/disk/by-path/ccw-0.0.2201-part1 dasd_configure 0.0.2201 0 0 vmcp detach 2201 Aria -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Bauer, Bobby (NIH/CIT) [E] Sent: Thursday, June 02, 2011 2:52 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: bad entry in fstab Aria, please explain further because I don't know how to do this. First I would: vmcp link servername 201 2201 mw password then what? Bobby Bauer Center for Information Technology National Institutes of Health Bethesda, MD 20892-5628 301-594-7474 -Original Message- From: Aria Bamdad [mailto:a...@bsc.gwu.edu] Sent: Thursday, June 02, 2011 1:50 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: bad entry in fstab Or just link the VM minidisk with the root file system for this failing system as R/W on an working linux system, let's call that the maintenance system. On the maintenance system, enable and mount that temporary volume. Now you have a fully functional linux system and can use any tool you like to correct the typo. Unmount, release/detach the minidisk when done and then boot the original failing system. Aria -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Bauer, Bobby (NIH/CIT) [E] Sent: Thursday, June 02, 2011 1:32 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: bad entry in fstab Thanks to everybody for help, especially for the remount command. Never did find a way to send Control-D The sed command worked perfect when I tested it on a running system but would not work from the maintenance mode. I kept getting the "Unterminated `s'" error and it looked like the # was causing a problem. We escaped the # like this \# and sed added a new line above the LogVol08 line. One of the guys said we should just use sed to delete the line and sure enough, we deleted the bad line in fstab and was able to ipl it. I think I learned my lesson to make backups no matter how simple a change it is. Bobby Bauer Center for Information Technology National Institutes of Health Bethesda, MD 20892-5628 301-594-7474 -Original Message- From: Brent Kincer [mailto:dev.bkin...@gmail.com] Sent: Thursday, June 02, 2011 12:19 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: bad entry in fstab In case you're not using IUCV terminals and don't have access to something like 'vi', just use sed to comment out the offending line and reboot. Would go something like this: mount -o remount,rw / sed -i 's/.*LogVol08.*/#&/g' /etc/fstab shutdown -r now That sed statement will comment out any line containing LogVol08 in /etc/fstab. Correct your typo after the reboot. Hope this helps! On , Rogério Soares wrote: > do a CTRL+D, you will got aa single user mode,, just correct you > /etc/fstab and reboot :) > On Thu, Jun 2, 2011 at 12:55 PM, Bauer, Bobby (NIH/CIT) [E] > baue...@mail.nih.gov> wrote: > > I made a typo when I added a new logical volume to fstab, I misspelled > the > > logical volume mane. The reboot fails with: > > > > [/sbin/fsck.ext4 (1) -- /LAData] fsck.ext4 -a > > /dev/mapper/vg_labarc-LogVol08 > > fsck.ext4: No such file or directory while trying to open > > /dev/mapper/vg_labarc-LogVol08 > > /dev/mapper/vg_labarc-LogVol08: > > > > The superblock could not be read or does not describe a correct ext2 > > filesystem. If the device is valid and it really contains an ext2 > > filesystem (and not swap or ufs or something else), then the superblock > > is corrupt, and you might try running e2fsck with an alternate > superblock: > > e2fsck -b 8193 > > > > [FAILED] > > > > *** An error occurred during the file system check. > > *** Dropping you to a shell; the system will reboot > > *** when you leave the shell. > > *** Warning -- SELinux is active > > *** Disabling security enforcement for system recovery. > > *** Run 'setenforce 1' to reenable. > > Give root password for maintenance > > (or type Control-D to continue): > > > > > > If I give it the root password, the filesystem is read only. Not sure > what > > the Control-D will do for me but I don't seem to be able to pass it to > the > > system anyway. Any suggestions how to fix fstab without rebuilding the > > system? Or some other method? > > > > Thanks > > Bobby Bauer > > Center for Information Technology > > National Institutes of Health > > Bethesda, MD 20892-5628 > > 301-594-7474 > > > > > > > >
Re: bad entry in fstab
Thanks Scott, could I ask for the steps for LVM? Bobby Bauer Center for Information Technology National Institutes of Health Bethesda, MD 20892-5628 301-594-7474 -Original Message- From: Scott Rohling [mailto:scott.rohl...@gmail.com] Sent: Thursday, June 02, 2011 2:59 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: bad entry in fstab chccwdev -e 2201 (activate it) lsdasd (find out what dasd 2201 is) mount /dev/dasdx1 /mnt This assumes 2201 contains a single filesystem.. if it's part of an LVM, there's more to all this.. Scott Rohling On Thu, Jun 2, 2011 at 12:51 PM, Bauer, Bobby (NIH/CIT) [E] < baue...@mail.nih.gov> wrote: > Aria, please explain further because I don't know how to do this. > First I would: > vmcp link servername 201 2201 mw password > > then what? > > > Bobby Bauer > Center for Information Technology > National Institutes of Health > Bethesda, MD 20892-5628 > 301-594-7474 > > > -Original Message- > From: Aria Bamdad [mailto:a...@bsc.gwu.edu] > Sent: Thursday, June 02, 2011 1:50 PM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: bad entry in fstab > > Or just link the VM minidisk with the root file system for this failing > system as R/W on an working linux system, let's call that the maintenance > system. On the maintenance system, enable and mount that temporary volume. > Now you have a fully functional linux system and can use any tool you like > to correct the typo. > > Unmount, release/detach the minidisk when done and then boot the original > failing system. > > Aria > -Original Message- > From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of > Bauer, > Bobby (NIH/CIT) [E] > Sent: Thursday, June 02, 2011 1:32 PM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: bad entry in fstab > > Thanks to everybody for help, especially for the remount command. > > Never did find a way to send Control-D > > The sed command worked perfect when I tested it on a running system but > would not work from the maintenance mode. I kept getting the "Unterminated > `s'" error and it looked like the # was causing a problem. We escaped the # > like this \# and sed added a new line above the LogVol08 line. One of the > guys said we should just use sed to delete the line and sure enough, we > deleted the bad line in fstab and was able to ipl it. > > I think I learned my lesson to make backups no matter how simple a change > it > is. > > Bobby Bauer > Center for Information Technology > National Institutes of Health > Bethesda, MD 20892-5628 > 301-594-7474 > > > > -Original Message- > From: Brent Kincer [mailto:dev.bkin...@gmail.com] > Sent: Thursday, June 02, 2011 12:19 PM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: bad entry in fstab > > In case you're not using IUCV terminals and don't have access to something > like 'vi', just use sed to comment out the offending line and reboot. > > Would go something like this: > mount -o remount,rw / > sed -i 's/.*LogVol08.*/#&/g' /etc/fstab > shutdown -r now > > That sed statement will comment out any line containing LogVol08 in > /etc/fstab. Correct your typo after the reboot. > > Hope this helps! > > On , Rogério Soares wrote: > > do a CTRL+D, you will got aa single user mode,, just correct you > > > /etc/fstab and reboot :) > > > > > > > > > On Thu, Jun 2, 2011 at 12:55 PM, Bauer, Bobby (NIH/CIT) [E] > > baue...@mail.nih.gov> wrote: > > > > > > I made a typo when I added a new logical volume to fstab, I misspelled > > the > > > > logical volume mane. The reboot fails with: > > > > > > > > [/sbin/fsck.ext4 (1) -- /LAData] fsck.ext4 -a > > > > /dev/mapper/vg_labarc-LogVol08 > > > > fsck.ext4: No such file or directory while trying to open > > > > /dev/mapper/vg_labarc-LogVol08 > > > > /dev/mapper/vg_labarc-LogVol08: > > > > > > > > The superblock could not be read or does not describe a correct ext2 > > > > filesystem. If the device is valid and it really contains an ext2 > > > > filesystem (and not swap or ufs or something else), then the superblock > > > > is corrupt, and you might try running e2fsck with an alternate > > superblock: > > > > e2fsck -b 8193 > > > > > > > > [FAILED] > > > > > > > > *** An error occurred during the file system check. > > > > *** Dropping you to a shell; the system will reboot > > > > *** when you leave the shell. > > > > *** Warning -- SELinux is active > > > > *** Disabling security enforcement for system recovery. > > > > *** Run 'setenforce 1' to reenable. > > > > Give root password for maintenance > > > > (or type Control-D to continue): > > > > > > > > > > > > If I give it the root password, the filesystem is read only. Not sure > > what > > > > the Control-D will do for me but I don't seem to be able to pass it to > > the > > > > system anyway. Any suggestions how to fix fstab without rebuilding the > > > > system? Or some other method? > > > > > > > > Thanks > > > > Bobby Bauer > > > > Center for Information Technology > > > > National Institutes of Health > > > > Bethesda, MD 20
Re: bad entry in fstab
chccwdev -e 2201 (activate it) lsdasd (find out what dasd 2201 is) mount /dev/dasdx1 /mnt This assumes 2201 contains a single filesystem.. if it's part of an LVM, there's more to all this.. Scott Rohling On Thu, Jun 2, 2011 at 12:51 PM, Bauer, Bobby (NIH/CIT) [E] < baue...@mail.nih.gov> wrote: > Aria, please explain further because I don't know how to do this. > First I would: > vmcp link servername 201 2201 mw password > > then what? > > > Bobby Bauer > Center for Information Technology > National Institutes of Health > Bethesda, MD 20892-5628 > 301-594-7474 > > > -Original Message- > From: Aria Bamdad [mailto:a...@bsc.gwu.edu] > Sent: Thursday, June 02, 2011 1:50 PM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: bad entry in fstab > > Or just link the VM minidisk with the root file system for this failing > system as R/W on an working linux system, let's call that the maintenance > system. On the maintenance system, enable and mount that temporary volume. > Now you have a fully functional linux system and can use any tool you like > to correct the typo. > > Unmount, release/detach the minidisk when done and then boot the original > failing system. > > Aria > -Original Message- > From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of > Bauer, > Bobby (NIH/CIT) [E] > Sent: Thursday, June 02, 2011 1:32 PM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: bad entry in fstab > > Thanks to everybody for help, especially for the remount command. > > Never did find a way to send Control-D > > The sed command worked perfect when I tested it on a running system but > would not work from the maintenance mode. I kept getting the "Unterminated > `s'" error and it looked like the # was causing a problem. We escaped the # > like this \# and sed added a new line above the LogVol08 line. One of the > guys said we should just use sed to delete the line and sure enough, we > deleted the bad line in fstab and was able to ipl it. > > I think I learned my lesson to make backups no matter how simple a change > it > is. > > Bobby Bauer > Center for Information Technology > National Institutes of Health > Bethesda, MD 20892-5628 > 301-594-7474 > > > > -Original Message- > From: Brent Kincer [mailto:dev.bkin...@gmail.com] > Sent: Thursday, June 02, 2011 12:19 PM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: bad entry in fstab > > In case you're not using IUCV terminals and don't have access to something > like 'vi', just use sed to comment out the offending line and reboot. > > Would go something like this: > mount -o remount,rw / > sed -i 's/.*LogVol08.*/#&/g' /etc/fstab > shutdown -r now > > That sed statement will comment out any line containing LogVol08 in > /etc/fstab. Correct your typo after the reboot. > > Hope this helps! > > On , Rogério Soares wrote: > > do a CTRL+D, you will got aa single user mode,, just correct you > > > /etc/fstab and reboot :) > > > > > > > > > On Thu, Jun 2, 2011 at 12:55 PM, Bauer, Bobby (NIH/CIT) [E] > > baue...@mail.nih.gov> wrote: > > > > > > I made a typo when I added a new logical volume to fstab, I misspelled > > the > > > > logical volume mane. The reboot fails with: > > > > > > > > [/sbin/fsck.ext4 (1) -- /LAData] fsck.ext4 -a > > > > /dev/mapper/vg_labarc-LogVol08 > > > > fsck.ext4: No such file or directory while trying to open > > > > /dev/mapper/vg_labarc-LogVol08 > > > > /dev/mapper/vg_labarc-LogVol08: > > > > > > > > The superblock could not be read or does not describe a correct ext2 > > > > filesystem. If the device is valid and it really contains an ext2 > > > > filesystem (and not swap or ufs or something else), then the superblock > > > > is corrupt, and you might try running e2fsck with an alternate > > superblock: > > > > e2fsck -b 8193 > > > > > > > > [FAILED] > > > > > > > > *** An error occurred during the file system check. > > > > *** Dropping you to a shell; the system will reboot > > > > *** when you leave the shell. > > > > *** Warning -- SELinux is active > > > > *** Disabling security enforcement for system recovery. > > > > *** Run 'setenforce 1' to reenable. > > > > Give root password for maintenance > > > > (or type Control-D to continue): > > > > > > > > > > > > If I give it the root password, the filesystem is read only. Not sure > > what > > > > the Control-D will do for me but I don't seem to be able to pass it to > > the > > > > system anyway. Any suggestions how to fix fstab without rebuilding the > > > > system? Or some other method? > > > > > > > > Thanks > > > > Bobby Bauer > > > > Center for Information Technology > > > > National Institutes of Health > > > > Bethesda, MD 20892-5628 > > > > 301-594-7474 > > > > > > > > > > > > > > > > -- > > > > 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/wlvinde
Re: bad entry in fstab
Aria, please explain further because I don't know how to do this. First I would: vmcp link servername 201 2201 mw password then what? Bobby Bauer Center for Information Technology National Institutes of Health Bethesda, MD 20892-5628 301-594-7474 -Original Message- From: Aria Bamdad [mailto:a...@bsc.gwu.edu] Sent: Thursday, June 02, 2011 1:50 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: bad entry in fstab Or just link the VM minidisk with the root file system for this failing system as R/W on an working linux system, let's call that the maintenance system. On the maintenance system, enable and mount that temporary volume. Now you have a fully functional linux system and can use any tool you like to correct the typo. Unmount, release/detach the minidisk when done and then boot the original failing system. Aria -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Bauer, Bobby (NIH/CIT) [E] Sent: Thursday, June 02, 2011 1:32 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: bad entry in fstab Thanks to everybody for help, especially for the remount command. Never did find a way to send Control-D The sed command worked perfect when I tested it on a running system but would not work from the maintenance mode. I kept getting the "Unterminated `s'" error and it looked like the # was causing a problem. We escaped the # like this \# and sed added a new line above the LogVol08 line. One of the guys said we should just use sed to delete the line and sure enough, we deleted the bad line in fstab and was able to ipl it. I think I learned my lesson to make backups no matter how simple a change it is. Bobby Bauer Center for Information Technology National Institutes of Health Bethesda, MD 20892-5628 301-594-7474 -Original Message- From: Brent Kincer [mailto:dev.bkin...@gmail.com] Sent: Thursday, June 02, 2011 12:19 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: bad entry in fstab In case you're not using IUCV terminals and don't have access to something like 'vi', just use sed to comment out the offending line and reboot. Would go something like this: mount -o remount,rw / sed -i 's/.*LogVol08.*/#&/g' /etc/fstab shutdown -r now That sed statement will comment out any line containing LogVol08 in /etc/fstab. Correct your typo after the reboot. Hope this helps! On , Rogério Soares wrote: > do a CTRL+D, you will got aa single user mode,, just correct you > /etc/fstab and reboot :) > On Thu, Jun 2, 2011 at 12:55 PM, Bauer, Bobby (NIH/CIT) [E] > baue...@mail.nih.gov> wrote: > > I made a typo when I added a new logical volume to fstab, I misspelled > the > > logical volume mane. The reboot fails with: > > > > [/sbin/fsck.ext4 (1) -- /LAData] fsck.ext4 -a > > /dev/mapper/vg_labarc-LogVol08 > > fsck.ext4: No such file or directory while trying to open > > /dev/mapper/vg_labarc-LogVol08 > > /dev/mapper/vg_labarc-LogVol08: > > > > The superblock could not be read or does not describe a correct ext2 > > filesystem. If the device is valid and it really contains an ext2 > > filesystem (and not swap or ufs or something else), then the superblock > > is corrupt, and you might try running e2fsck with an alternate > superblock: > > e2fsck -b 8193 > > > > [FAILED] > > > > *** An error occurred during the file system check. > > *** Dropping you to a shell; the system will reboot > > *** when you leave the shell. > > *** Warning -- SELinux is active > > *** Disabling security enforcement for system recovery. > > *** Run 'setenforce 1' to reenable. > > Give root password for maintenance > > (or type Control-D to continue): > > > > > > If I give it the root password, the filesystem is read only. Not sure > what > > the Control-D will do for me but I don't seem to be able to pass it to > the > > system anyway. Any suggestions how to fix fstab without rebuilding the > > system? Or some other method? > > > > Thanks > > Bobby Bauer > > Center for Information Technology > > National Institutes of Health > > Bethesda, MD 20892-5628 > > 301-594-7474 > > > > > > > > -- > > 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 > --
Re: bad entry in fstab
I usually don't use sed to remove a line, I make a copy of the file and use "grep -v" to rip the offending line out of existence... It's simpler. mount -o rw,remount / cp /etc/fstab /etc/fstab.1 grep -v 'LogVol08' /etc/fstab.1 > /etc/fstab And you are good to go. Reboot and you can edit the file with vi/emacs/nano/wine winword.exe later... I personally try to, when adding something to /etc/fstab, do a "mount -a" and check if everything was mounted as expected. Saves the trouble of finding a mistyping only at reboot. Mauro http://mauro.limeiratem.com - registered Linux User: 294521 Scripture is both history, and a love letter from God. On Thu, Jun 2, 2011 at 2:50 PM, Aria Bamdad wrote: > Or just link the VM minidisk with the root file system for this failing > system as R/W on an working linux system, let's call that the maintenance > system. On the maintenance system, enable and mount that temporary volume. > Now you have a fully functional linux system and can use any tool you like > to correct the typo. > > Unmount, release/detach the minidisk when done and then boot the original > failing system. > > Aria > -Original Message- > From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of > Bauer, > Bobby (NIH/CIT) [E] > Sent: Thursday, June 02, 2011 1:32 PM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: bad entry in fstab > > Thanks to everybody for help, especially for the remount command. > > Never did find a way to send Control-D > > The sed command worked perfect when I tested it on a running system but > would not work from the maintenance mode. I kept getting the "Unterminated > `s'" error and it looked like the # was causing a problem. We escaped the # > like this \# and sed added a new line above the LogVol08 line. One of the > guys said we should just use sed to delete the line and sure enough, we > deleted the bad line in fstab and was able to ipl it. > > I think I learned my lesson to make backups no matter how simple a change > it > is. > > Bobby Bauer > Center for Information Technology > National Institutes of Health > Bethesda, MD 20892-5628 > 301-594-7474 > > > > -Original Message- > From: Brent Kincer [mailto:dev.bkin...@gmail.com] > Sent: Thursday, June 02, 2011 12:19 PM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: bad entry in fstab > > In case you're not using IUCV terminals and don't have access to something > like 'vi', just use sed to comment out the offending line and reboot. > > Would go something like this: > mount -o remount,rw / > sed -i 's/.*LogVol08.*/#&/g' /etc/fstab > shutdown -r now > > That sed statement will comment out any line containing LogVol08 in > /etc/fstab. Correct your typo after the reboot. > > Hope this helps! > > On , Rogério Soares wrote: > > do a CTRL+D, you will got aa single user mode,, just correct you > > > /etc/fstab and reboot :) > > > > > > > > > On Thu, Jun 2, 2011 at 12:55 PM, Bauer, Bobby (NIH/CIT) [E] > > baue...@mail.nih.gov> wrote: > > > > > > I made a typo when I added a new logical volume to fstab, I misspelled > > the > > > > logical volume mane. The reboot fails with: > > > > > > > > [/sbin/fsck.ext4 (1) -- /LAData] fsck.ext4 -a > > > > /dev/mapper/vg_labarc-LogVol08 > > > > fsck.ext4: No such file or directory while trying to open > > > > /dev/mapper/vg_labarc-LogVol08 > > > > /dev/mapper/vg_labarc-LogVol08: > > > > > > > > The superblock could not be read or does not describe a correct ext2 > > > > filesystem. If the device is valid and it really contains an ext2 > > > > filesystem (and not swap or ufs or something else), then the superblock > > > > is corrupt, and you might try running e2fsck with an alternate > > superblock: > > > > e2fsck -b 8193 > > > > > > > > [FAILED] > > > > > > > > *** An error occurred during the file system check. > > > > *** Dropping you to a shell; the system will reboot > > > > *** when you leave the shell. > > > > *** Warning -- SELinux is active > > > > *** Disabling security enforcement for system recovery. > > > > *** Run 'setenforce 1' to reenable. > > > > Give root password for maintenance > > > > (or type Control-D to continue): > > > > > > > > > > > > If I give it the root password, the filesystem is read only. Not sure > > what > > > > the Control-D will do for me but I don't seem to be able to pass it to > > the > > > > system anyway. Any suggestions how to fix fstab without rebuilding the > > > > system? Or some other method? > > > > > > > > Thanks > > > > Bobby Bauer > > > > Center for Information Technology > > > > National Institutes of Health > > > > Bethesda, MD 20892-5628 > > > > 301-594-7474 > > > > > > > > > > > > > > > > -- > > > > 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: bad entry in fstab
Or just link the VM minidisk with the root file system for this failing system as R/W on an working linux system, let's call that the maintenance system. On the maintenance system, enable and mount that temporary volume. Now you have a fully functional linux system and can use any tool you like to correct the typo. Unmount, release/detach the minidisk when done and then boot the original failing system. Aria -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Bauer, Bobby (NIH/CIT) [E] Sent: Thursday, June 02, 2011 1:32 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: bad entry in fstab Thanks to everybody for help, especially for the remount command. Never did find a way to send Control-D The sed command worked perfect when I tested it on a running system but would not work from the maintenance mode. I kept getting the "Unterminated `s'" error and it looked like the # was causing a problem. We escaped the # like this \# and sed added a new line above the LogVol08 line. One of the guys said we should just use sed to delete the line and sure enough, we deleted the bad line in fstab and was able to ipl it. I think I learned my lesson to make backups no matter how simple a change it is. Bobby Bauer Center for Information Technology National Institutes of Health Bethesda, MD 20892-5628 301-594-7474 -Original Message- From: Brent Kincer [mailto:dev.bkin...@gmail.com] Sent: Thursday, June 02, 2011 12:19 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: bad entry in fstab In case you're not using IUCV terminals and don't have access to something like 'vi', just use sed to comment out the offending line and reboot. Would go something like this: mount -o remount,rw / sed -i 's/.*LogVol08.*/#&/g' /etc/fstab shutdown -r now That sed statement will comment out any line containing LogVol08 in /etc/fstab. Correct your typo after the reboot. Hope this helps! On , Rogério Soares wrote: > do a CTRL+D, you will got aa single user mode,, just correct you > /etc/fstab and reboot :) > On Thu, Jun 2, 2011 at 12:55 PM, Bauer, Bobby (NIH/CIT) [E] > baue...@mail.nih.gov> wrote: > > I made a typo when I added a new logical volume to fstab, I misspelled > the > > logical volume mane. The reboot fails with: > > > > [/sbin/fsck.ext4 (1) -- /LAData] fsck.ext4 -a > > /dev/mapper/vg_labarc-LogVol08 > > fsck.ext4: No such file or directory while trying to open > > /dev/mapper/vg_labarc-LogVol08 > > /dev/mapper/vg_labarc-LogVol08: > > > > The superblock could not be read or does not describe a correct ext2 > > filesystem. If the device is valid and it really contains an ext2 > > filesystem (and not swap or ufs or something else), then the superblock > > is corrupt, and you might try running e2fsck with an alternate > superblock: > > e2fsck -b 8193 > > > > [FAILED] > > > > *** An error occurred during the file system check. > > *** Dropping you to a shell; the system will reboot > > *** when you leave the shell. > > *** Warning -- SELinux is active > > *** Disabling security enforcement for system recovery. > > *** Run 'setenforce 1' to reenable. > > Give root password for maintenance > > (or type Control-D to continue): > > > > > > If I give it the root password, the filesystem is read only. Not sure > what > > the Control-D will do for me but I don't seem to be able to pass it to > the > > system anyway. Any suggestions how to fix fstab without rebuilding the > > system? Or some other method? > > > > Thanks > > Bobby Bauer > > Center for Information Technology > > National Institutes of Health > > Bethesda, MD 20892-5628 > > 301-594-7474 > > > > > > > > -- > > 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/ -- 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: bad entry in fstab
Thanks to everybody for help, especially for the remount command. Never did find a way to send Control-D The sed command worked perfect when I tested it on a running system but would not work from the maintenance mode. I kept getting the "Unterminated `s'" error and it looked like the # was causing a problem. We escaped the # like this \# and sed added a new line above the LogVol08 line. One of the guys said we should just use sed to delete the line and sure enough, we deleted the bad line in fstab and was able to ipl it. I think I learned my lesson to make backups no matter how simple a change it is. Bobby Bauer Center for Information Technology National Institutes of Health Bethesda, MD 20892-5628 301-594-7474 -Original Message- From: Brent Kincer [mailto:dev.bkin...@gmail.com] Sent: Thursday, June 02, 2011 12:19 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: bad entry in fstab In case you're not using IUCV terminals and don't have access to something like 'vi', just use sed to comment out the offending line and reboot. Would go something like this: mount -o remount,rw / sed -i 's/.*LogVol08.*/#&/g' /etc/fstab shutdown -r now That sed statement will comment out any line containing LogVol08 in /etc/fstab. Correct your typo after the reboot. Hope this helps! On , Rogério Soares wrote: > do a CTRL+D, you will got aa single user mode,, just correct you > /etc/fstab and reboot :) > On Thu, Jun 2, 2011 at 12:55 PM, Bauer, Bobby (NIH/CIT) [E] > baue...@mail.nih.gov> wrote: > > I made a typo when I added a new logical volume to fstab, I misspelled > the > > logical volume mane. The reboot fails with: > > > > [/sbin/fsck.ext4 (1) -- /LAData] fsck.ext4 -a > > /dev/mapper/vg_labarc-LogVol08 > > fsck.ext4: No such file or directory while trying to open > > /dev/mapper/vg_labarc-LogVol08 > > /dev/mapper/vg_labarc-LogVol08: > > > > The superblock could not be read or does not describe a correct ext2 > > filesystem. If the device is valid and it really contains an ext2 > > filesystem (and not swap or ufs or something else), then the superblock > > is corrupt, and you might try running e2fsck with an alternate > superblock: > > e2fsck -b 8193 > > > > [FAILED] > > > > *** An error occurred during the file system check. > > *** Dropping you to a shell; the system will reboot > > *** when you leave the shell. > > *** Warning -- SELinux is active > > *** Disabling security enforcement for system recovery. > > *** Run 'setenforce 1' to reenable. > > Give root password for maintenance > > (or type Control-D to continue): > > > > > > If I give it the root password, the filesystem is read only. Not sure > what > > the Control-D will do for me but I don't seem to be able to pass it to > the > > system anyway. Any suggestions how to fix fstab without rebuilding the > > system? Or some other method? > > > > Thanks > > Bobby Bauer > > Center for Information Technology > > National Institutes of Health > > Bethesda, MD 20892-5628 > > 301-594-7474 > > > > > > > > -- > > 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/ -- 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: bad entry in fstab
I always keep a copy of the old file when working with Linux on z - for key files like /etc/fstab especially. That way I can issue single command from the 3270 terminal to get things back and not worry about vi/sed/etc. Next time maybe ;-) Scott Rohling On Thu, Jun 2, 2011 at 10:19 AM, Brent Kincer wrote: > In case you're not using IUCV terminals and don't have access to something > like 'vi', just use sed to comment out the offending line and reboot. > > Would go something like this: > mount -o remount,rw / > sed -i 's/.*LogVol08.*/#&/g' /etc/fstab > shutdown -r now > > That sed statement will comment out any line containing LogVol08 in > /etc/fstab. Correct your typo after the reboot. > > Hope this helps! > > On , Rogério Soares wrote: > >> do a CTRL+D, you will got aa single user mode,, just correct you >> > > /etc/fstab and reboot :) >> > > > > > > > > On Thu, Jun 2, 2011 at 12:55 PM, Bauer, Bobby (NIH/CIT) [E] >> baue...@mail.nih.gov> wrote: >> > > > > > I made a typo when I added a new logical volume to fstab, I misspelled >> the >> > > > logical volume mane. The reboot fails with: >> > > > >> > > > [/sbin/fsck.ext4 (1) -- /LAData] fsck.ext4 -a >> > > > /dev/mapper/vg_labarc-LogVol08 >> > > > fsck.ext4: No such file or directory while trying to open >> > > > /dev/mapper/vg_labarc-LogVol08 >> > > > /dev/mapper/vg_labarc-LogVol08: >> > > > >> > > > The superblock could not be read or does not describe a correct ext2 >> > > > filesystem. If the device is valid and it really contains an ext2 >> > > > filesystem (and not swap or ufs or something else), then the superblock >> > > > is corrupt, and you might try running e2fsck with an alternate >> superblock: >> > > > e2fsck -b 8193 >> > > > >> > > > [FAILED] >> > > > >> > > > *** An error occurred during the file system check. >> > > > *** Dropping you to a shell; the system will reboot >> > > > *** when you leave the shell. >> > > > *** Warning -- SELinux is active >> > > > *** Disabling security enforcement for system recovery. >> > > > *** Run 'setenforce 1' to reenable. >> > > > Give root password for maintenance >> > > > (or type Control-D to continue): >> > > > >> > > > >> > > > If I give it the root password, the filesystem is read only. Not sure >> what >> > > > the Control-D will do for me but I don't seem to be able to pass it to >> the >> > > > system anyway. Any suggestions how to fix fstab without rebuilding the >> > > > system? Or some other method? >> > > > >> > > > Thanks >> > > > Bobby Bauer >> > > > Center for Information Technology >> > > > National Institutes of Health >> > > > Bethesda, MD 20892-5628 >> > > > 301-594-7474 >> > > > >> > > > >> > > > >> > > > -- >> > > > 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/ >> > > -- 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: Oracle on RedHat 6 beta for z
RHEL 5.6 James Chaplin Systems Programmer, MVS, zVM & zLinux Base Technologies, Inc -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Hughes, Jim Sent: Thursday, June 02, 2011 1:04 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Oracle on RedHat 6 beta for z Wow. What release should I download? Jim Hughes Consulting Systems Programmer Mainframe Technical Support Group Department of Information Technology State of New Hampshire 27 Hazen Drive Concord, NH 03301 603-271-5586Fax 603.271.1516 Statement of Confidentiality: The contents of this message are confidential. Any unauthorized disclosure, reproduction, use or dissemination (either whole or in part) is prohibited. If you are not the intended recipient of this message, please notify the sender immediately and delete the message from your system. ==>-Original Message- ==>From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of ==>Graves, Aaron ==>Sent: Thursday, June 02, 2011 11:28 AM ==>To: LINUX-390@VM.MARIST.EDU ==>Subject: Re: Oracle on RedHat 6 beta for z ==> ==>I do not believe Oracle is supported yet on RHEL6 on any platform. ==> ==>Aaron ==> ==>-Original Message- ==>From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of ==>Hughes, Jim ==>Sent: Thursday, June 02, 2011 11:14 AM ==>To: LINUX-390@VM.MARIST.EDU ==>Subject: Oracle on RedHat 6 beta for z ==> ==>Our Oracle people are getting an error saying Oracle complains about ==>Redhat 6 Beta is not a supported operating system. ==> ==>We are downloading Redhat 6 for z now. ==> ==>Has anyone else discovered this restriction? ==> ==> ==>Jim Hughes ==>Consulting Systems Programmer ==>Mainframe Technical Support Group ==>Department of Information Technology ==>State of New Hampshire ==>27 Hazen Drive ==>Concord, NH 03301 ==>603-271-5586Fax 603.271.1516 ==> ==>Statement of Confidentiality: The contents of this message are ==>confidential. Any unauthorized disclosure, reproduction, use or ==>dissemination (either whole or in part) is prohibited. If you are not ==>the intended recipient of this message, please notify the sender ==>immediately and delete the message from your system. ==> ==>- - ==>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/ -- 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: Oracle on RedHat 6 beta for z
Wow. What release should I download? Jim Hughes Consulting Systems Programmer Mainframe Technical Support Group Department of Information Technology State of New Hampshire 27 Hazen Drive Concord, NH 03301 603-271-5586Fax 603.271.1516 Statement of Confidentiality: The contents of this message are confidential. Any unauthorized disclosure, reproduction, use or dissemination (either whole or in part) is prohibited. If you are not the intended recipient of this message, please notify the sender immediately and delete the message from your system. ==>-Original Message- ==>From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of ==>Graves, Aaron ==>Sent: Thursday, June 02, 2011 11:28 AM ==>To: LINUX-390@VM.MARIST.EDU ==>Subject: Re: Oracle on RedHat 6 beta for z ==> ==>I do not believe Oracle is supported yet on RHEL6 on any platform. ==> ==>Aaron ==> ==>-Original Message- ==>From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of ==>Hughes, Jim ==>Sent: Thursday, June 02, 2011 11:14 AM ==>To: LINUX-390@VM.MARIST.EDU ==>Subject: Oracle on RedHat 6 beta for z ==> ==>Our Oracle people are getting an error saying Oracle complains about ==>Redhat 6 Beta is not a supported operating system. ==> ==>We are downloading Redhat 6 for z now. ==> ==>Has anyone else discovered this restriction? ==> ==> ==>Jim Hughes ==>Consulting Systems Programmer ==>Mainframe Technical Support Group ==>Department of Information Technology ==>State of New Hampshire ==>27 Hazen Drive ==>Concord, NH 03301 ==>603-271-5586Fax 603.271.1516 ==> ==>Statement of Confidentiality: The contents of this message are ==>confidential. Any unauthorized disclosure, reproduction, use or ==>dissemination (either whole or in part) is prohibited. If you are not ==>the intended recipient of this message, please notify the sender ==>immediately and delete the message from your system. ==> ==>- - ==>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/ -- 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: bad entry in fstab
In case you're not using IUCV terminals and don't have access to something like 'vi', just use sed to comment out the offending line and reboot. Would go something like this: mount -o remount,rw / sed -i 's/.*LogVol08.*/#&/g' /etc/fstab shutdown -r now That sed statement will comment out any line containing LogVol08 in /etc/fstab. Correct your typo after the reboot. Hope this helps! On , Rogério Soares wrote: do a CTRL+D, you will got aa single user mode,, just correct you /etc/fstab and reboot :) On Thu, Jun 2, 2011 at 12:55 PM, Bauer, Bobby (NIH/CIT) [E] baue...@mail.nih.gov> wrote: > I made a typo when I added a new logical volume to fstab, I misspelled the > logical volume mane. The reboot fails with: > > [/sbin/fsck.ext4 (1) -- /LAData] fsck.ext4 -a > /dev/mapper/vg_labarc-LogVol08 > fsck.ext4: No such file or directory while trying to open > /dev/mapper/vg_labarc-LogVol08 > /dev/mapper/vg_labarc-LogVol08: > > The superblock could not be read or does not describe a correct ext2 > filesystem. If the device is valid and it really contains an ext2 > filesystem (and not swap or ufs or something else), then the superblock > is corrupt, and you might try running e2fsck with an alternate superblock: > e2fsck -b 8193 > > [FAILED] > > *** An error occurred during the file system check. > *** Dropping you to a shell; the system will reboot > *** when you leave the shell. > *** Warning -- SELinux is active > *** Disabling security enforcement for system recovery. > *** Run 'setenforce 1' to reenable. > Give root password for maintenance > (or type Control-D to continue): > > > If I give it the root password, the filesystem is read only. Not sure what > the Control-D will do for me but I don't seem to be able to pass it to the > system anyway. Any suggestions how to fix fstab without rebuilding the > system? Or some other method? > > Thanks > Bobby Bauer > Center for Information Technology > National Institutes of Health > Bethesda, MD 20892-5628 > 301-594-7474 > > > > -- > 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: bad entry in fstab
You can try remounting the filesystem from the shell; mount -o remount,rw,sync -t FS_TYPE DEVICE_NAME MOUNTING_POINT Att, Marcos Dib Filho From: "Bauer, Bobby (NIH/CIT) [E]" To: LINUX-390@vm.marist.edu Date: 06/02/2011 12:57 PM Subject: bad entry in fstab I made a typo when I added a new logical volume to fstab, I misspelled the logical volume mane. The reboot fails with: [/sbin/fsck.ext4 (1) -- /LAData] fsck.ext4 -a /dev/mapper/vg_labarc-LogVol08 fsck.ext4: No such file or directory while trying to open /dev/mapper/vg_labarc-LogVol08 /dev/mapper/vg_labarc-LogVol08: The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 [FAILED] *** An error occurred during the file system check. *** Dropping you to a shell; the system will reboot *** when you leave the shell. *** Warning -- SELinux is active *** Disabling security enforcement for system recovery. *** Run 'setenforce 1' to reenable. Give root password for maintenance (or type Control-D to continue): If I give it the root password, the filesystem is read only. Not sure what the Control-D will do for me but I don't seem to be able to pass it to the system anyway. Any suggestions how to fix fstab without rebuilding the system? Or some other method? Thanks Bobby Bauer Center for Information Technology National Institutes of Health Bethesda, MD 20892-5628 301-594-7474 -- 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: bad entry in fstab
Running RHEL V6 under z/VM 5.4 Bobby Bauer Center for Information Technology National Institutes of Health Bethesda, MD 20892-5628 301-594-7474 -Original Message- From: Bauer, Bobby (NIH/CIT) [E] Sent: Thursday, June 02, 2011 11:55 AM To: 'Linux on 390 Port' Subject: bad entry in fstab I made a typo when I added a new logical volume to fstab, I misspelled the logical volume mane. The reboot fails with: [/sbin/fsck.ext4 (1) -- /LAData] fsck.ext4 -a /dev/mapper/vg_labarc-LogVol08 fsck.ext4: No such file or directory while trying to open /dev/mapper/vg_labarc-LogVol08 /dev/mapper/vg_labarc-LogVol08: The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 [FAILED] *** An error occurred during the file system check. *** Dropping you to a shell; the system will reboot *** when you leave the shell. *** Warning -- SELinux is active *** Disabling security enforcement for system recovery. *** Run 'setenforce 1' to reenable. Give root password for maintenance (or type Control-D to continue): If I give it the root password, the filesystem is read only. Not sure what the Control-D will do for me but I don't seem to be able to pass it to the system anyway. Any suggestions how to fix fstab without rebuilding the system? Or some other method? Thanks Bobby Bauer Center for Information Technology National Institutes of Health Bethesda, MD 20892-5628 301-594-7474 -- 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: bad entry in fstab
do a CTRL+D, you will got a a single user mode,, just correct you /etc/fstab and reboot :) On Thu, Jun 2, 2011 at 12:55 PM, Bauer, Bobby (NIH/CIT) [E] < baue...@mail.nih.gov> wrote: > I made a typo when I added a new logical volume to fstab, I misspelled the > logical volume mane. The reboot fails with: > > [/sbin/fsck.ext4 (1) -- /LAData] fsck.ext4 -a > /dev/mapper/vg_labarc-LogVol08 > fsck.ext4: No such file or directory while trying to open > /dev/mapper/vg_labarc-LogVol08 > /dev/mapper/vg_labarc-LogVol08: > > The superblock could not be read or does not describe a correct ext2 > filesystem. If the device is valid and it really contains an ext2 > filesystem (and not swap or ufs or something else), then the superblock > is corrupt, and you might try running e2fsck with an alternate superblock: >e2fsck -b 8193 > > [FAILED] > > *** An error occurred during the file system check. > *** Dropping you to a shell; the system will reboot > *** when you leave the shell. > *** Warning -- SELinux is active > *** Disabling security enforcement for system recovery. > *** Run 'setenforce 1' to reenable. > Give root password for maintenance > (or type Control-D to continue): > > > If I give it the root password, the filesystem is read only. Not sure what > the Control-D will do for me but I don't seem to be able to pass it to the > system anyway. Any suggestions how to fix fstab without rebuilding the > system? Or some other method? > > Thanks > Bobby Bauer > Center for Information Technology > National Institutes of Health > Bethesda, MD 20892-5628 > 301-594-7474 > > > > -- > 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: bad entry in fstab
Just had this happen to me..enter maintenance mode run the following... mount -o remount,rw / edit the fstab and correct the mistake...ipl it and it should work Best Regards Richard Testa OIT-Operation Unix Systems Administrator NH Department of Information Technology 603-271-5460 (w) 603-235-2659 (c) www.nh.gov/doit -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Bauer, Bobby (NIH/CIT) [E] Sent: Thursday, June 02, 2011 11:55 AM To: LINUX-390@VM.MARIST.EDU Subject: bad entry in fstab I made a typo when I added a new logical volume to fstab, I misspelled the logical volume mane. The reboot fails with: [/sbin/fsck.ext4 (1) -- /LAData] fsck.ext4 -a /dev/mapper/vg_labarc-LogVol08 fsck.ext4: No such file or directory while trying to open /dev/mapper/vg_labarc-LogVol08 /dev/mapper/vg_labarc-LogVol08: The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 [FAILED] *** An error occurred during the file system check. *** Dropping you to a shell; the system will reboot *** when you leave the shell. *** Warning -- SELinux is active *** Disabling security enforcement for system recovery. *** Run 'setenforce 1' to reenable. Give root password for maintenance (or type Control-D to continue): If I give it the root password, the filesystem is read only. Not sure what the Control-D will do for me but I don't seem to be able to pass it to the system anyway. Any suggestions how to fix fstab without rebuilding the system? Or some other method? Thanks Bobby Bauer Center for Information Technology National Institutes of Health Bethesda, MD 20892-5628 301-594-7474 -- 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/
bad entry in fstab
I made a typo when I added a new logical volume to fstab, I misspelled the logical volume mane. The reboot fails with: [/sbin/fsck.ext4 (1) -- /LAData] fsck.ext4 -a /dev/mapper/vg_labarc-LogVol08 fsck.ext4: No such file or directory while trying to open /dev/mapper/vg_labarc-LogVol08 /dev/mapper/vg_labarc-LogVol08: The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 [FAILED] *** An error occurred during the file system check. *** Dropping you to a shell; the system will reboot *** when you leave the shell. *** Warning -- SELinux is active *** Disabling security enforcement for system recovery. *** Run 'setenforce 1' to reenable. Give root password for maintenance (or type Control-D to continue): If I give it the root password, the filesystem is read only. Not sure what the Control-D will do for me but I don't seem to be able to pass it to the system anyway. Any suggestions how to fix fstab without rebuilding the system? Or some other method? Thanks Bobby Bauer Center for Information Technology National Institutes of Health Bethesda, MD 20892-5628 301-594-7474 -- 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: Oracle on RedHat 6 beta for z
I do not believe Oracle is supported yet on RHEL6 on any platform. Aaron -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Hughes, Jim Sent: Thursday, June 02, 2011 11:14 AM To: LINUX-390@VM.MARIST.EDU Subject: Oracle on RedHat 6 beta for z Our Oracle people are getting an error saying Oracle complains about Redhat 6 Beta is not a supported operating system. We are downloading Redhat 6 for z now. Has anyone else discovered this restriction? Jim Hughes Consulting Systems Programmer Mainframe Technical Support Group Department of Information Technology State of New Hampshire 27 Hazen Drive Concord, NH 03301 603-271-5586Fax 603.271.1516 Statement of Confidentiality: The contents of this message are confidential. Any unauthorized disclosure, reproduction, use or dissemination (either whole or in part) is prohibited. If you are not the intended recipient of this message, please notify the sender immediately and delete the message from your system. -- 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/
Oracle on RedHat 6 beta for z
Our Oracle people are getting an error saying Oracle complains about Redhat 6 Beta is not a supported operating system. We are downloading Redhat 6 for z now. Has anyone else discovered this restriction? Jim Hughes Consulting Systems Programmer Mainframe Technical Support Group Department of Information Technology State of New Hampshire 27 Hazen Drive Concord, NH 03301 603-271-5586Fax 603.271.1516 Statement of Confidentiality: The contents of this message are confidential. Any unauthorized disclosure, reproduction, use or dissemination (either whole or in part) is prohibited. If you are not the intended recipient of this message, please notify the sender immediately and delete the message from your system. -- 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: SwapCache
On Thu, Jun 2, 2011 at 2:43 PM, Dave Czajkowski wrote: > Is there a way to disable or limit the amount of SwapCache? I understand > it's function, but the double allocation of these pages is causing my low > memory alerts to trip. Your anonymous page becomes swapcache when a copy is written to swap but not yet lost by giving it to someone else (and thus may still be used) or after swap-in when the process did not modify the contents yet. When you swap to VDISK you do have an additional copy in real memory, but with difference access patterns (and more likely to be paged out by z/VM). Don't see how you can avoid other than by not swapping... Rob -- 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/
[no subject]
On Thu, Jun 2, 2011 at 9:19 AM, Kobus Erwee wrote: > INFO 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 > -- > For more information on Linux on System z, visit > http://wiki.linuxvm.org/ > Hello! Please don't do this. Just because one individual did does not mean you should. The proper place for such requests is indicated in the header above, and below this message. - Gregg C Levine gregg.drw...@gmail.com "This signature fought the Time Wars, time and again." -- 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: SwapCache
We lower the default for the parmvm.swappiness The default is 60 and we mostly set this to 5 now. To see where it's set now; cat /proc/sys/vm/swappiness Change it; echo 5 > /proc/sys/vm/swappiness Update the /etc/sysctl.conf file to keep where you want it ... 20, 5, or even 0 ... Hope this is some help... Paul -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Dave Czajkowski Sent: Thursday, June 02, 2011 8:43 AM To: LINUX-390@VM.MARIST.EDU Subject: SwapCache Is there a way to disable or limit the amount of SwapCache? I understand it's function, but the double allocation of these pages is causing my low memory alerts to trip. I can remove the swap copy with a swapoff/swapon. Is there a more elegant way to remove? -- 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/
[no subject]
INFO 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 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
SwapCache
Is there a way to disable or limit the amount of SwapCache? I understand it's function, but the double allocation of these pages is causing my low memory alerts to trip. I can remove the swap copy with a swapoff/swapon. Is there a more elegant way to remove? -- 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/
