Bill,
Has the dust settled now on the z/VM Spectre fixes? We put on VM65396
as well on a couple of systems then halted that until further fixes arrive.
On 4/12/2018 7:26 AM, Bill Bitner wrote:
Rick, if you have VM65396 on, but not VM65414, that would be my guess.
VM65414 corrected a problem
We used EDEVICE's for 15 years, tired of that. :-) Seriously the large
EDEVICEs with many zLinux OS disks per device was a bottleneck. We
never moved '/var' off so log backups (often for a bunch of systems at
once) and Linux backups were both having really high wait times on
EDEVs, with 1 I/O
Thanks Robert and others,
We figured there would be a learning curve, I think we'll get it figured
out, we just need to figure out everything, then how you do those things
on SLES12.
On 9/8/2017 3:28 PM, Robert J Brenneman wrote:
Ancient history:
You'd still need to customize disk clones to make them
work but it should at least break early during boot and not accecss the
golden image (especially not writable and thus potentially destroying its
golden property).
On 09/07/2017 09:19 PM, Greg Preddy wrote:
I think that is it, we have no clue where SLES
scsi_id (wwid) of Lun with friendly name (mpathX for
example).
That multipath configuration is also saved in initrd. So if you boot from
clone, it will end up mounting wrong volume.
Are you using LVM?
2017-09-07 9:08 GMT-04:00 Greg Preddy <gpre...@cox.net>:
All,
We're doing SLES 12
/multipath.conf) configuration. In there you
usually you bond scsi_id (wwid) of Lun with friendly name (mpathX for
example).
That multipath configuration is also saved in initrd. So if you boot from
clone, it will end up mounting wrong volume.
Are you using LVM?
2017-09-07 9:08 GMT-04:00 Greg Preddy
All,
We're doing SLES 12 on 100% LUN, with gold copy on a single 60GB LUN.
This is a new cloning approach for us so we're not sure how to make this
work. Our Linux SA got the storage admin to replicate the LUN, but when
we change the server to boot the copy, it still mounts the gold LUN.
99%
