On Wed, Feb 18, 2009 at 7:41 AM, Mark Perry rita.co@googlemail.com wrote:
Why would idle virtual processors be in the dispatch list?
Spin locks ;-)
I can see your smiley, so I take it you don't really think that an
idle processor would cause lock contention looking for work (though
this
Well I am not sure where I can do that. Normally I am told that this outside
of the support Novell gives for installation.
Best regards,
Florian
On Wed, Feb 18, 2009 at 1:52 AM, Mark Post mp...@novell.com wrote:
On 2/17/2009 at 2:34 PM, Florian Bilek florian.bi...@gmail.com
wrote:
Thank
We are also using FDR products in the similar fashion to Aaron's group.
Some variations:
For Postgres on zLinux we use pgdump and FDR/Upstream to backup the
result.
For DB2 on zLinux we use native tools and use FDR/Upstream to backup the
result.
For Oracle on zLinux we use a combination of RMAN
Hey, this is getting to be fun. I've gotten into rescue mode as described in
the manual Brad referenced below and was able to follow the script but it
doesn't tell me how to finish.
An 'lvm vgscan' found VolGroup00
The 'lvm vgchange -a y' found the 11 volumes and activated VolGroup00
I was able
Thanks, Tobias. I've tried placing this in various places in my
autoyast.xml file and still does not appear after autoyast completes.
So after the IPL from the boot disk failed, I IPLed the starter system and
manually add the file etc/sysconfig/
hardware/hwcfg-qeth-bus-ccw-0.0.1d00
Now when
On 2/17/09 6:39 PM, Scott Rohling scott.rohl...@gmail.com wrote:
Is that the Novell stance? No / under LVM??
No, I'd say that reflects real experience with having it break. Both
distributions support doing it technically. It'll work -- but you'll regret
it. If not now, soon.
Hi,
We're new to the Linux world. Currently we have 3390 Mod-3 (2.8G) and Mod-9s
(8.4 G) defined to our Linux guests under Z/VM.
I'm starting to get complaints that these 'partitions' are too small and do
not compare favorably with the dasd sizes available on PC desktops. (Apples and
We're new to the Linux world. Currently we have 3390 Mod-3 (2.8G) and Mod-9s
(8.4 G) defined to our Linux guests under Z/VM.
On ECKD, same as you mod-3 and mod-9. On FCP terabyte sized luns.
What I'd like to know from the group is - What are your DASD sizes?
Are the complaints about
On Feb 18, 2009, at 9:34 AM, O'Brien, David W. (NIH/CIT) [C] wrote:
Hi,
We're new to the Linux world. Currently we have 3390 Mod-3 (2.8G)
and Mod-9s (8.4 G) defined to our Linux guests under Z/VM.
I'm starting to get complaints that these 'partitions' are too
small and do not compare
I've heard several people mention using EDEV with FCP. We tested FCP and EDEV
was simple to set up and get working. Giving it to Linux seemed like it took a
bit more work. We had an IBM consultant come in and told us to never use EDEV
for Linux guests. Is anyone using EDEV FBA in production
Seriously start looking at FCP storage, at least for data partitions. While I
really like the ability to manage minidisks, you need to be able to hand out
bigger chunks, and LVM is just too much of a PITA long term to use to assemble
really large chunks of disk ( a few hundred G).
In the
On Feb 18, 2009, at 10:02 AM, Stewart Thomas J wrote:
We had an IBM consultant come in and told us to never use EDEV for
Linux guests.
That's fascinating.
What were the reasons given?
Adam
--
For LINUX-390 subscribe /
It would have been the overhead: primarily the FBA channel program has to be
converted to SCSI command sequences.
On 2/18/09 11:11 AM, Adam Thornton athorn...@sinenomine.net wrote:
On Feb 18, 2009, at 10:02 AM, Stewart Thomas J wrote:
We had an IBM consultant come in and told us to never use
Yep,
They are puny little disks to the distributed folks (and consider your
mod 3 is 2.3G and mod 9 6.8G after formatting and putting a file system
on it).
We are mostly mod 27 and mod 54. Mod 3's are only for paging here.
We do use LVM extensively. One server has 5TB (110 mod 54's).
LVM
Hi,
We run Red Hat 5.3. Our production LPARs use FCP attached SCSI for local
file systems, SCSI managed via EDEVs for the OS install (/ and /boot)
and 3390's for VM. It takes a lot of planning up front for the SCSI box
configuration. 50G and 100G are good LUN sizes. Good I/O performance
requires
On 2/18/09 11:02 AM, Stewart Thomas J stewartthom...@johndeere.com
wrote:
I've heard several people mention using EDEV with FCP. We tested FCP and EDEV
was simple to set up and get working. Giving it to Linux seemed like it took a
bit more work.
It's allocated just like any other minidisk.
Thanks Marcy,
Yes, we do backup all of our Linux DASD from Z\os using FDR.
Guess that will have to change.
Dave O'Brien
NIH Contractor
From: Linux on 390 Port [linux-...@vm.marist.edu] On Behalf Of Marcy Cortes
[marcy.d.cor...@wellsfargo.com]
Sent:
On 2/18/2009 at 6:35 AM, Florian Bilek florian.bi...@gmail.com wrote:
Well I am not sure where I can do that. Normally I am told that this outside
of the support Novell gives for installation.
That's true. It wasn't clear from your email that you were just doing an
evaluation. Sorry.
Just curious - how long does it take to do an fschk on your 5TB lvm ?
Alan Levy
VM/Linux Administrator
NYC DoITT
-Original Message-
From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Marcy
Cortes
Sent: Wednesday, February 18, 2009 11:20 AM
To:
Bauer, Bobby (NIH/CIT) [E] wrote:
Hey, this is getting to be fun. I've gotten into rescue mode as described in
the manual Brad referenced below and was able to follow the script but it
doesn't tell me how to finish.
An 'lvm vgscan' found VolGroup00
The 'lvm vgchange -a y' found the 11 volumes
On 2/18/2009 at 11:52 AM, Brad Hinson bhin...@redhat.com wrote:
-snip-
- there could be an initrd problem (perhaps the lvm module isn't being
loaded?) You can regenerate the initrd with chroot /mnt/sysimage;
mkinitrd -v /boot/initrd...img kernel_version
I'm betting on this one. Since
OK, I'm getting the hang of this, a little.
Nuts, modprobe.conf only has 5 of the 6 volumes!!!
However when I try to run mkinitrd from /boot it tells me
sh-3.1# mkinitrd -v initrd-2.6.18-53.el5.img 2.6.18-53.el5
/mnt/sysimage/sbin/mkinitrd: line 32: /etc/rc.d/init.d/functions: No such
On 2/18/2009 at 12:58 PM, Bauer, Bobby (NIH/CIT) [E]
baue...@mail.nih.gov
wrote:
-snip-
However when I try to run mkinitrd from /boot it tells me
sh-3.1# mkinitrd -v initrd-2.6.18-53.el5.img 2.6.18-53.el5
/mnt/sysimage/sbin/mkinitrd: line 32: /etc/rc.d/init.d/functions: No such
file
On 2/18/2009 at 11:51 AM, Levy, Alan al...@doitt.nyc.gov wrote:
Just curious - how long does it take to do an fschk on your 5TB lvm ?
If they're using a journaling file system, it shouldn't take any time at all.
Mark Post
From my notes, feel free to correct any errors.
EDEVICE can be used to emulate ECKD on FBA. We did some testing with this and
were able to format the disk for use as z/VM minidisks. The setup was pretty
easy and once defined were controlled mostly the same as regular ECKD disk. Per
one of our
On Feb 18, 2009, at 12:52 PM, Stewart Thomas J wrote:
I also had a link to the following IBM report:
http://www.vm.ibm.com/perf/reports/zvm/html/520lxd.html
Absent from this study is an evaluation of Diagnose X'250' with
emulated FBA DASD. - that was another question IBM could never
answer at
Mark Post wrote:
You need to chroot to /mnt/sysimage before running the mkinitrd.
Sorry to hop on route.. but..
I was wondering...
Why on earth does one need to mkinitrd/zipl after adding a DASD volume
to z/Linux ?
Most (if not all) 'distributed' platforms are perfectly happy to add a
On 2/18/09 1:52 PM, Stewart Thomas J stewartthom...@johndeere.com wrote:
From my notes, feel free to correct any errors.
EDEVICE can be used to emulate ECKD on FBA. We did some testing with this and
were able to format the disk for use as z/VM minidisks. The setup was pretty
easy and once
On 2/18/2009 at 1:58 PM, Ivan Warren i...@vmfacility.fr wrote:
-snip-
I was wondering...
Why on earth does one need to mkinitrd/zipl after adding a DASD volume
to z/Linux ?
Basically, some historical, performance, and data integrity reasons.
When the DASD driver initializes, particularly
I find that with SLES10, you do NOT have to mkinitrd and zipl. It
will happily find the additional DASD and bring them online without
needing special intelligence in the INITRD.
The whole INITRD thing ... I will hold my peace for the moment.
Now if you added a different KIND of DASD (if you
Mark Post wrote:
Basically, some historical, performance, and data integrity reasons.
Ok,
I'm starting to get a better picture now (as to the how why). As I
understand it, the bases are :
- An LPAR may have thousands of volumes allocated to it, not all of them
being for Linux use.
-
Richard Troth wrote:
The whole INITRD thing ... I will hold my peace for the moment.
I'm with you here..
I mean..
On 'distributed' platforms you may have.. what.. 200.. 300 different
drivers..
On z.. you have what ... 15 ?
A monolithic kernel would make all the sense in the world..
I don't believe that there is a performance problem with thousands of
volumes that are there. The performance problem is with the thousands
of volumes that are not there.
In my case, when we brought in an IBM DS6800, I defined to the IOCP,
that there were 150 volumes on each of the 8
On 2/18/09 2:23 PM, Mark Post mp...@novell.com wrote:
When the DASD driver initializes, particularly in an LPAR, which devices do
you want it to pay attention to? Unlike most distributed systems, an LPAR can
be set up to see all the devices that are attached to the box. Those
devices can
On 2/18/2009 at 2:15 PM, Richard Troth vmcow...@gmail.com wrote:
I find that with SLES10, you do NOT have to mkinitrd and zipl. It
will happily find the additional DASD and bring them online without
needing special intelligence in the INITRD.
That's going to depend on just how the DASD
Mark Post wrote:
That's going to depend on just how the DASD devices were added, and whether the
appropriate configuration files got created. If those files are there, then
you're right as long as those DASD volumes are not needed to get your root file
system mounted. Such as is the case
On 2/18/2009 at 3:03 PM, Ivan Warren i...@vmfacility.fr wrote:
Why doesn't mkinitrd *ONLY* take care of the IPL
volume (or volumes in you're LVM).. - as the initrd was designed - then
- depending on what config is on the root fs, enable this or that volume
- once control has been passed
Mark Post wrote:
That's is all that's necessary. And, again, if you make sure that when DASD
volumes are added, that the proper configuration files are there, it should
work just fine. However, consider the case where / is on an LV, and you just
added another volume to the VG. That's big
On 2/18/2009 at 3:12 PM, Ivan Warren i...@vmfacility.fr wrote:
A monolithic kernel would make all the sense in the world.. and IPL
directly with your root !
And would be different from how everything else is done, driving up costs,
generating complaints (Why is this different from my other
Reading a piece on adding Qeth to sles10 it talks about 2 pieces
one in /etc/sysconfig/network/
and one in /etc/sysconfig/hardware/
So after the initial install I find
/etc/sysconfig/hardware/hwcfg-bus-ccw-0.0.1d00
and
/etc/sysconfig/network/ifcfg-eth-id-02:00:85:00:00:09
Is it odd these are not
Mark Post wrote:
And would be different from how everything else is done, driving up costs, generating
complaints (Why is this different from my other systems? That's stupid.)
I don't particularly care for using an initrd myself, but I'm not going to try
to argue with the folks that put
On Feb 18, 2009, at 4:30 PM, Ivan Warren wrote:
Basically, the requirement for an initrd was generated by
'distributed'
systems.. Where you can stick in brand XXX variant ZZZ HBA.. but on
IBM
System z.. you can't do that ! And even more... Even if you were
allowed
to, it would have to follow
On 2/18/2009 at 4:27 PM, Mark Pace mpac...@gmail.com wrote:
-snip-
So after the initial install I find
/etc/sysconfig/hardware/hwcfg-bus-ccw-0.0.1d00
and
/etc/sysconfig/network/ifcfg-eth-id-02:00:85:00:00:09
Is it odd these are not named the same?
Not particularly. If I were doing it,
Adam Thornton wrote:
Or diag250.
Sure, doesn't work on the metal. Nevertheless.
Well.. Diag 250 is just a way to talk to a DASD.
Whatever you do with Diag 250, you can also do with SSCH, an ORB and
some CCWs... So even if Diag 250 isn't embedded in the kernel, you
should still be able to
On Feb 18, 2009, at 9:36 PM, Ivan Warren wrote:
Now about Diag 250.. What's the gain ?
a) tons easier for the device driver writers. Take a look at the disk
driver in OpenSolaris/z to see why I care.
Now.. Simplicity ? Device independence ? well, to support LPAR, you're
going to have to
45 matches
Mail list logo
