not my employer's.
"Daniel Tate"
Sent by: "The IBM z/VM Operating System"
08/30/2010 12:19 PM
Please respond to
"The IBM z/VM Operating System"
To
IBMVM@LISTSERV.UARK.EDU
cc
Subject
Re: messed up DASD Mappings..
Thanks! This was exactly wha
Thanks! This was exactly what i needed to get started. Once this was
done i was able to link it (mw) and, because the machine with
permissions to link to another disk was non-network-accessible, take a
crash course on using ed to modify files :/ but the troubled system
is back up.
Thanks for y
If it looks like the others when you do a 'q v dasd' then it is a minidisk.
Most likely, it is a "near full pack" minidisk, which means it starts
at cylinder 1 (and z/VM owns cylinder 0). Attaching it directly means
that the guest sees the whole disk, including cyl 0. Linux will not
know what
Right on both accounts. I am unsure if it is a minidisk - it
normally shows when i do a q v dasd just like all the others (minus
VDSK) in the original post (CYL addressing), if that tells you
anything
On Mon, Aug 30, 2010 at 9:43 AM, Richard Troth wrote:
> You attached the disk (the whole volu
You attached the disk (the whole volume) to that other guest. But ...
the guest which owns it ... is it a minidisk? If so, then you want to
'link' it instead of 'attach' it.
That's just for starters. Forgive me if you already know this, but it
sounds like #1 you are in a minor crisis and #2
I have a user with a corrupt filesystem. in attempting to move the
DASD Containing the root disks, i detached the old disk:
00: DASD 9F80 VM6LX9
I need to reattach it to the original machine, but i also need to
attach it to another guest, mount it and fix the corrupted files where
it can boot.
