I find that fdasd /dev/dasd_ shows Linux Native for a dasdfmt disks
and it shows Linux LVM LVM after you do a pvcreate command to the disk.
Using p to look at the partitions and q to not change them ...
Command action
m print this menu
p print the partition table
n add a new
I haven't read all the answers, but usually it works fine (when it is a mount
for userdata that fails)
to just mount everything manually:
mount /usr
mount /var
mount /opt
and so on.
and after enough mounts just: /etc/init.d/sshd start
and you can login as usual and fix the problem
Anyone having tried the mvsdad driver for read z/OS dasd directly ?
I have tried download the SLES11 version from
http://www.mvsdasd.org/download.html
it does not work, some corrupt file here it seams.
So I downloaded the source, but gets errors ( of course, why should it be
simple ;)
In file
There have been a couple of other methods that work but this is by far the
simplest and it was user data that I had the problem with. I'll give this a
try, thanks.
Bobby Bauer
Center for Information Technology
National Institutes of Health
Bethesda, MD 20892-5628
301-594-7474
-Original
I recently had a typo in fstab for a new file system I tried to add and my
system would not come back up. Thanks to everybody for helping me out and
getting my system back without a major recovery effort.
Any reason why zLinux dies when it finds a bad entry in fstab even though the
filesystem
If /etc/fstab has markers which say this is important, then it dies.
That is common for Unix/Linux/POSIX.
Specifically, if you have the troubled FS set to be checked (last
column something other than 0), and the check fails, the system will
fall back to maint mode. Filesystems which fail to
On 6/9/2011 at 11:23 AM, Agblad Tore tore.agb...@volvo.com wrote:
Anyone having tried the mvsdad driver for read z/OS dasd directly ?
For anyone that has, I hope their auditors never find out.
Mark Post
--
For LINUX-390
This might be influenced by those numbers at the end of the fstab entry..
The last one indicates whether fsck should be run against it. If yours is
0, then that should prevent Linux from requiring it there.
I'm not sure how badly you mucked up the syntax though...As others have
said - use
Thank you everyone for your confirmation and instructions. It threw off our
Linux Support person when YaSt wouldn't keep the LVM option on the disk as
he was doing the install. Following the suggestions we were able to
configure it and it is working now.
Craig Collins
State of WI, DOA, DET
On
On 6/9/2011 at 11:29 AM, Agblad Tore tore.agb...@volvo.com wrote:
I haven't read all the answers, but usually it works fine (when it is a mount
for userdata that fails)
to just mount everything manually:
mount /usr
mount /var
mount /opt
and so on.
mount -a might be easier.
Mark
I would bet it just has to time out. I know NFS and SMBFS can hold on for
quite a while before giving up the ghost.
-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Bauer,
Bobby (NIH/CIT) [E]
Sent: Thursday, June 09, 2011 12:21 PM
To:
For mounting network filesystems this can be true... but for a local disk
(which I'm pretty sure is the case here) - you are either put into a
recovery shell or it won't come up at all and you have to recover by other
means. Depends on what the error in your fstab is and what fsck option you
have
On Thursday, 06/09/2011 at 01:10 EDT, Mark Post mp...@novell.com wrote:
On 6/9/2011 at 11:23 AM, Agblad Tore tore.agb...@volvo.com wrote:
Anyone having tried the mvsdad driver for read z/OS dasd directly ?
For anyone that has, I hope their auditors never find out.
(shudder) Indeed.
Implementing the driver isn't an auditable offense.. gaining access to the
volume through a DEDICATE or LINK, etc is another story - but that shouldn't
discourage use of the driver. I see little difference between this and the
cmsfs driver... access to a z/OS or CMS disk is auditable (or
14 matches
Mail list logo
