Actually, different LPAR but the same CPU, same DASD box, same DASD
devices, same minidiskextents, same minidisks. So other than the LPAR-ID
for this VM it should be identical. I don't know for sure is the by-uuid
and/or by-id would be the same between the two LPARs. Indeed, the
by-path is the same. I would also expect the dasdxx to be the same.
Meaning, dev 200 is dasda, 201 is dasdb and so on.

When I look in the /dev/disk/by-path it links to the /dev/dasdxx
devices. So in that case once again, if /dev/dasde1 is not available,
how can /dev/disk/by-path find it's volumes? In fact, listing the
directory (yes we DDR'ed the / disk before fixing the errors) I can't
find neither /dev/dasde1 nor /dev/disk/by-path/ccw-0.0.0204*. And
/dev/dasdkk1 doesn't exist, so ..by-path/ccw-0.0.0328p1 shows a broken
link.

Berry.


-----Original Message-----
From: Linux on 390 Port [mailto:[email protected]] On Behalf Of
David Boyes
Sent: dinsdag 23 februari 2010 14:22
To: [email protected]
Subject: Re: Devices disappeared from /dev

This is why I always recommend using by-path references in /etc/fstab
rather than the dasdxx entries.

What happened is that something disturbed the order of DASD detection --
moving the guest to different disks on a different system, in your case
-- and the system detected the disks and assigned them to some other
dasdxx entry. Udev is supposed to handle this better, but it doesn't
always work, where the by-path entries DO always work (at least as long
as you don't change the virtual address at which the disk is presented
to the virtual machine, at which point: your gun, your foot).

Avoid relying on dasdxx entries. As you discovered, they'll bite you.

--d b

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions, send
email to [email protected] 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 [email protected] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze worden u op aanvraag direct 
kosteloos toegezonden.

 

This e-mail and the documents attached 
are confidential and intended solely

for the addressee; it may also be 
privileged. If you receive this e-mail

in error, please notify the sender 
immediately and destroy it.

As its integrity cannot be secured on 
the Internet, the Atos Origin group

liability cannot be triggered for the 
message content. Although the

sender endeavours to maintain a 
computer virus-free network, the sender

does not warrant that this transmission 
is virus-free and will not be

liable for any damages resulting from 
any virus transmitted.

 

On all offers and agreements under 
which Atos Origin supplies goods and/or

services of whatever nature, the Terms 
of Delivery from Atos Origin

exclusively apply. 

The Terms of Delivery shall be promptly 
submitted to you on your request.

 

Atos Origin Nederland B.V. / Utrecht

KvK Utrecht 30132762

Reply via email to