Our linux is SUSE Enterprise Server 11 SP1 running on z/VM V5.4.
Our linux kernel is 2.6.32.12-0.7-default (geeko@buildhost) (gcc version
4.3.4 gcc-4 setup.1a06a7: Linux is running as a z/VM guest operating
system in 64-bit mode.
Our tape lib is TS3500, driver is 3592 E05.
Our SAN switch is
On 10/18/2011 09:14 AM, Lu GL Gao wrote:
Our linux is SUSE Enterprise Server 11 SP1 running on z/VM V5.4.
Our tape lib is TS3500, driver is 3592 E05.
(1) download tape driver from website of System Storage Interoperation
Center.
I downloaded 2 files. One is lin_tape-1.61.0-1.src.rpm,
On Tue, 18 Oct 2011 11:41:47 +0200 Steffen Maier wrote:
Since you (had to) build the lin_tape device driver kernel module
yourself it is formally flagged as not supported by SLES11 and
therefore modprobe denies loading the module.
I wonder how this sits philosophically with users.
At least
On 10/18/2011 at 05:41 AM, Steffen Maier ma...@linux.vnet.ibm.com wrote:
Since you (had to) build the lin_tape device driver kernel module
yourself it is formally flagged as not supported by SLES11 and
therefore modprobe denies loading the module. This is indicated by above
message for
We are running z/VM Version 5 Release 4.0, service level 1001 (64-bit). We
can ping all of our SLES10 guests through our real hypersockets from z/VM.
however we cannot ping our SLES11 guests from z/VM through our real
hypersockets. All our Linux guests (SLES10 and SLES11) can ping each other
fine
On 10/18/2011 at 06:42 PM, Peter E. Abresch Jr. - at Pepco
peabre...@pepco.com wrote:
We are running z/VM Version 5 Release 4.0, service level 1001 (64-bit). We
can ping all of our SLES10 guests through our real hypersockets from z/VM.
however we cannot ping our SLES11 guests from z/VM
Yes, PTF shows applied UK46027:
VMFSRV1226I TCPIP (5VMTCP40%TCPIP) APAR PK80882 (PTF UK46027) status:
VMFSRV1226IRECEIVED 06/17/10 07:50:18
VMFSRV1226IAPPLIED 10/06/09 20:16:49
VMFSRV1226IBUILT 06/17/10 07:51:47
VMFSRV1226IPUT2PROD 06/17/10 09:18:43
VMFSRV2760I SERVICE
Peter,
Are you by any chance hitting:
Applying SLES 11 SP 1 Causing Communication Issues
http://www.novell.com/support/search.do?cmd=displayKCdocType=kcexternalId=7007649sliceId=1docTypeID=DT_TID_1_1
Mike O'Reilly
IBM Linux Change Team
Peter E. Abresch
Maybe, net.ipv4.conf.all.rp_filter was set to 1. I took one of my
SLES11-SP1 guest and set it to 2. It now pings from z/VM. When I set it
back to 1, it still pings. When I set it to 0, it still pings. I went to a
different SLES11 guest. It did not ping, but once I set
net.ipv4.conf.all.rp_filter
On Tue, 18 Oct 2011 13:51:37 -0600 Mark Post wrote:
If the OP _has_ to use lin_tape for whatever reason, he needs to
understand that running with a tainted kernel _might_ put some
additional burden on him in the future.
Is this not GPL licensed code ?.
If so, just how does running it result
On 10/19/2011 at 12:36 AM, Shane ibm-m...@tpg.com.au wrote:
Is this not GPL licensed code ?.
I have no idea if it is or not.
If so, just how does running it result in a tainted kernel ?.
We didn't build it, so we don't support it. Tainting is not a one bit flag, it
is multiple bits,
Let me explain the reason of installing tape driver is we are going to
install Tivoli Storage Manager which will be the only tool to backup our
systems.
Our linux is newly installed which was provided by IBM. Nobody modified it,
and even nobody begin to use it.
I also downloaded tape driver from
We ran it for a while on SLES 10. There was a tainted message there too at
boot time, but no special action like SLES 11 seems to require.
We needed it to drive an IBM ATL. There is no native Linux support for that.
Just know that if you do have a problem and Novell is providing your support,
13 matches
Mail list logo
