Linux - Virtualization and CloudThis forum is for the discussion of all topics relating to Linux Virtualization and Linux Cloud platforms. Xen, KVM, OpenVZ, VirtualBox, VMware, Linux-VServer and all other Linux Virtualization platforms are welcome. OpenStack, CloudStack, ownCloud, Cloud Foundry, Eucalyptus, Nimbus, OpenNebula and all other Linux Cloud platforms are welcome. Note that questions relating solely to non-Linux OS's should be asked in the General forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I did diskmap to make sure there is no overlap. After that, "DIRECTXA USER" is issued.
After linux01 is boot up, I issued "chccwdev -e 109" to online the disk. I can see it using lsdasd:
hxlnx01:~ # lsdasd
0.0.0100(ECKD) at ( 94: 0) is dasda : active at blocksize 4096, 600840 blocks, 2347 MB
0.0.0101(ECKD) at ( 94: 4) is dasdb : active at blocksize 4096, 600840 blocks, 2347 MB
0.0.0300(FBA ) at ( 94: 8) is dasdc : active at blocksize 512, 524288 blocks, 256 MB
0.0.0301(FBA ) at ( 94: 12) is dasdd : active at blocksize 512, 1048576 blocks, 512 MB
0.0.0102(ECKD) at ( 94: 16) is dasde : active at blocksize 4096, 600840 blocks, 2347 MB
0.0.0103(ECKD) at ( 94: 20) is dasdf : active at blocksize 4096, 600840 blocks, 2347 MB
0.0.0104(ECKD) at ( 94: 24) is dasdg : active at blocksize 4096, 600840 blocks, 2347 MB
0.0.0105(ECKD) at ( 94: 28) is dasdh : active at blocksize 4096, 600840 blocks, 2347 MB
0.0.0106(ECKD) at ( 94: 32) is dasdi : active at blocksize 4096, 600840 blocks, 2347 MB
0.0.0107(ECKD) at ( 94: 36) is dasdj : active at blocksize 4096, 600840 blocks, 2347 MB
0.0.0109(ECKD) at ( 94: 40) is dasdk : active at blocksize 4096, 600840 blocks, 2347 MB
Everything appeared fine until I tried to format it in linux.
hxlnx01:~ # dasdfmt -b 4096 -y -f /dev/dasdk
Disk in use!
I could use FORCE to enforce format, but later when i tried to partition it using fdasd I encountered same "disk in use" problem again..
Can anybody shed some light on this issue? I have tried using a different minidisk number but it doesn't solve the problem..
I won't be able to attach it to SYSTEM unless I detach it from MAINT.
I have tried to FORCE LINUX01 from VM side to ensure the guest is brought down completely, and then XAUTOLOG LINUX01. However the result is still not good.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.