On Tue, 16 Sep 2003, James Melin wrote:
> Using this strategy from the link on Linux VM
>
> mount /dev/dasdh1 /mnt
> cd /var
> tar -clpSf - . | (cd /mnt; tar -xpSf - )
>
> produced 3 errors
>
> tar: ./lib/mysql/mysql.sock: socket ignored
> tar: ./run/printer: socket ignored
> tar: ./run/.nscd_sock
On Tue, 16 Sep 2003, James Melin wrote:
> Once upon a time, our former storage administrator carved up a new shark
> box and gave me 8 3390-mod 9's and 8 3390-mod 3's, for 2 Linux Lpars.
> Things went merrily along until we attempted to do a disaster recovery test
> of Linux, where I discovered th
> tar: ./lib/mysql/mysql.sock: socket ignored
> tar: ./run/printer: socket ignored
> tar: ./run/.nscd_socket: socket ignored
> Those three errors translated into missing items in the copy
Not really. They're not really files (they're actually open sockets), so
it's OK that they didn't copy.
-- db
James Melin writes:
> Using this strategy from the link on Linux VM
>
> mount /dev/dasdh1 /mnt
> cd /var
> tar -clpSf - . | (cd /mnt; tar -xpSf - )
>
> produced 3 errors
>
> tar: ./lib/mysql/mysql.sock: socket ignored
> tar: ./run/printer: socket ignored
> tar: ./run/.nscd_socket: socket ignored
>
I know that the mysql.sock will be created when MySQL starts up on the new
system. I have this every time I clone a system and MySQL always starts up
fine. I suspect that the nscd.socket is the same sort of an ipl to ipl
entity.
/Thomas Kern
/301-903-2211
> -Original Message-
> From: Jame
Using this strategy from the link on Linux VM
mount /dev/dasdh1 /mnt
cd /var
tar -clpSf - . | (cd /mnt; tar -xpSf - )
produced 3 errors
tar: ./lib/mysql/mysql.sock: socket ignored
tar: ./run/printer: socket ignored
tar: ./run/.nscd_socket: socket ignored
Those three errors translated into missi
I want to connect to the MQ Server on Z/OS from Linux/390.
I want to make the connections available in a pool for a
servlet application to be run under Tomcat.
Any suggestions, Please.
Thanks,
Samy Rengasamy.
Just had the in-house hardware guy in here, and it looks like the "gateway" device got
dropped from our IOCP. I'll let you know when we get farther along.
> -Original Message-
> From: Ann Smith [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, September 16, 2003 3:25 PM
> To: [EMAIL PROTECTED]
Do post back if it works. We're doing the same thing.
"Hall, Ken (IDS ECCS)" wrote:
> That's exactly what I'm trying to get clarified now. They've given me LUNs of
> 561-563, but I think that means "0x0561".
>
> If I get it working, I'll post more details.
>
> > -Original Messag
That's exactly what I'm trying to get clarified now. They've given me LUNs of
561-563, but I think that means "0x0561".
If I get it working, I'll post more details.
> -Original Message-
> From: Ferguson, Neale [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, September 16, 2003 2:0
Posted on behalf of SHARE...
Is your organization considering, or about to deploy, Linux or Linux/390?
Then, don't miss your chance to learn from a leading Linux expert, Mark Post
of EDS, this October in San Francisco and Anaheim as he presents two-day
interactive seminars that deliver the most in
Hi Matt,
When connectivity is lost through the PIX, can your guests still
communicate with each other ? (at least the two on the same VLAN)
I'll assume that you mean they cannot communicate through the PIX.
Your other (HiperSockets) connection should not affect this interface
directly. Any addit
The LUN is a 16 byte no. but usually you're only interested in the first
four. So when we were told the LUN was 01 I initially did 0x001
but it needed to be 0x0001.
On Tuesday, 09/16/2003 at 09:49 CST, Matt Lashley/SCO
<[EMAIL PROTECTED]> wrote:
> I have three Linux images coupled to a VSWITCH. The VSWITCH is
connected
> to an OSA Express. The OSA Express is plugged into a VLAN on a Cisco
6509
> which is plugged into a PIX with an IP address if 172.16.64.1
>
I'd check the switch configuration and ensure WWPN/LUN are correct and that
the switch allows the LUN to talk to the given WWPN (of the 390).
-Original Message-
We did rebuild the kernel and double checked options on our side.
We also booted from disk rather than using the shared NSS but s
Based on what we saw, the problem was exactly that: We weren't given the right port
and LUN names. The closest I was able to get was to see the "VMC Database" on LUN 0.
They've since replaced the original box with a "DMX" box, but haven't been able to
figure out the port and LUN names for THAT
We did rebuild the kernel and double checked options on our side.
We also booted from disk rather than using the shared NSS but same results.
We want to talk to the EMC SAN folks here. There are messages regarding
write protection in /var/log/messages:
ep 16 13:39:47 linuxl1 kernel: zfcp: FSF:
zfc
We've used the EMC devices without any problem except for me typing in
incorrect LUN values. Once my dyslexia was cured, the devices worked as they
were supposed to. So if anything, verify your LUN setting is correct.
(Although the symptoms I got for this were different to what you are
showing.)
-
I didn't gather from the previous notes whether you specified the maps for the devices
when loading zfcp. Did you follow the documentation, such as it is? The driver won't
auto-discover devices.
I've been trying to do this for some time, but it seems that the problems have been on
the EMC sid
I'm at a loss then. All I can suggest is apply SP2 and try building the
kernel again.
lsmod:
(/root) Ready(0)# lsmod
Module Size Used byTainted: P
nfsd 76000 4 (autoclean)
st 28152 0 (unused)
sd_mod 14260 0 (unused)
zfcp 253732 0 (unused)
scsi_mod 88876 3 [st sd_
What does lsmod report?
-Original Message-
Yes. We did.
Jim,
There are 12 4096 blocks per track or 601,020 blocks
on a 3390-3 and 1803060 blocks on a 3390-0. The VTOC
for cdl is the small for all volume sizes as its just
a small "dummy" vtoc.
To copy just the allocated stuff on a dasd partition,
Richard Higson's tar2tar (below) is a convenient tool.
A
Yes. We did.
"Ferguson, Neale" wrote:
> Did you specify CONFIG_MSDOS_PARTITION=y in the kernel configuration? (File
> Systems->Partition Types->MSDOS)
>
> -Original Message-
> We built our own. We actually have been using the doc you kindly provided
> I think it's dated Aug. 2002.
> We ru
Did you specify CONFIG_MSDOS_PARTITION=y in the kernel configuration? (File
Systems->Partition Types->MSDOS)
-Original Message-
We built our own. We actually have been using the doc you kindly provided
I think it's dated Aug. 2002.
We run a shared kernel in an NSS also.
We had to build our
I have three Linux images coupled to a VSWITCH. The VSWITCH is connected
to an OSA Express. The OSA Express is plugged into a VLAN on a Cisco 6509
which is plugged into a PIX with an IP address if 172.16.64.1
The Linux images have IP addresses in the 192.168.2.0/24 subnet. The PIX
does NAT for
We built our own. We actually have been using the doc you kindly provided
I think it's dated Aug. 2002.
We run a shared kernel in an NSS also.
We had to build our own kernel for that as well as adding options needed for
fcp.
We are a little shy of service pack 2. We are are using kernel level
2.4.1
What service pack do you have applied? Is this the default kernel or have
you built your own?
Let's try this again. We rebooted and here's what happens with fdisk:
/etc/init.d) Ready(0)# fdisk /dev/sda
Device contains neither a valid DOS partition table, nor Sun, SGI or OSF
disklabel
Building a new DOS disklabel. Changes will remain in memory only,
until you decide to write them. After tha
Yes, we are using SLES8.
I just had Ed re-issue the fdisk /dev/sda and he was answering the prompts
as he had before. I was going to send you the messages fronm the console
but this time the linux guest appears to maybe have gone into a loop. But
we don't see any I/O being done. This is new. Befor
http://linuxvm.org/info/HOWTOs/movefs.html
Mark Post
-Original Message-
From: James Melin [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 16, 2003 10:53 AM
To: [EMAIL PROTECTED]
Subject: Fat 3390-mod 9's.
Once upon a time, our former storage administrator carved up a new shark
box a
Once upon a time, our former storage administrator carved up a new shark
box and gave me 8 3390-mod 9's and 8 3390-mod 3's, for 2 Linux Lpars.
Things went merrily along until we attempted to do a disaster recovery test
of Linux, where I discovered that the 3390-9's were exactly 100 cylinders
too la
Are you using SLES8? Can you fdisk /dev/sda?
-Original Message-
We are attempting have LINUX/390 use an EMC SAN.
scsiload puts out a message about an 'unknown partition table'
Are other folks using EMC SYMMETRIC successfully? Is there doc anywhere
on
how to configure the EMC SAN for LINUX/
We are attempting have LINUX/390 use an EMC SAN.
scsiload puts out a message about an 'unknown partition table'
Are other folks using EMC SYMMETRIC successfully? Is there doc anywhere
on
how to configure the EMC SAN for LINUX/390?
Sep 16 09:05:24 linuxl1 kernel: scsi : 0 hosts left.
Sep 16 09:05:2
34 matches
Mail list logo
