Did it. Here the results:
lstat64("/home2/knodlseder/test2.png", {st_mode=S_IFREG|0644,
st_size=0, ...}) = 0
stat64("/home2/knodlseder/test2.png", {st_mode=S_IFREG|0644,
st_size=0, ...}) = 0
stat64("/home2/knodlseder/test.png", {st_mode=S_IFREG|0644,
st_size=17318, ...}) = 0
stat64("/home2/knodlseder/test2.png", {st_mode=S_IFREG|0644,
st_size=0, ...}) = 0
open("/home2/knodlseder/test.png", O_RDONLY|O_LARGEFILE) = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=17318, ...}) = 0
open("/home2/knodlseder/test2.png", O_WRONLY|O_TRUNC|O_LARGEFILE) = 4
fstat64(4, {st_mode=S_IFREG|0644, st_size=0, ...}) = 0
fstat64(3, {st_mode=S_IFREG|0644, st_size=17318, ...}) = 0
read(3, "\211PNG\r\n\32\n\0\0\0\rIHDR\0\0\3 \0\0\2X\10\6\0\0\0
\232"..., 32768) = 17318
write(4, "\211PNG\r\n\32\n\0\0\0\rIHDR\0\0\3 \0\0\2X\10\6\0\0\0
\232"..., 17318) = 17318
read(3, "", 32768) = 0
close(4) = -1 EINVAL (Invalid argument)
Any clues ?
Jürgen
Le 19 janv. 09 à 03:29, jumanjiman@xxxxxxxxx a écrit :
Try running 'strace -o /tmp/errs cp /path/to(test2.png /path/to/
destination/' and then inpect the temp file.
-paul
Sent via BlackBerry by AT&T
-----Original Message-----
From: "Jürgen Knödlseder" <jurgen.knodlseder@xxxxxxx>
Date: Sun, 18 Jan 2009 22:29:48
To: linux clustering<linux-cluster@xxxxxxxxxx>
Subject: gfs/nfs trouble
Hi all,
I have trouble exporting a GFS over NFS. Here the situation:
I have 2 PE1950 with a MD3000 SAN attached to build a failover
cluster. Both machines run
kernel 2.6.27.7 and cluster-2.03.10. I configured several GFS on the
storage device that I would
like to export via NFS to a rather old PE2800 which runs kernel
2.4.26 (I have to stick to this
kernel on this machine since it runs openmosix).
When I copy on the PE2800 a small file (1858 Bytes) everything works
fine. When I try to copy
a slightly larger file (e.g. 17318 Bytes) I get the error
cp: closing `test2.png': Invalid argument
and I have an empty file 'test2.png' on the disk ...
I've seen a similar bug on bugzilla (https://bugzilla.redhat.com/
show_bug.cgi?id=432544)
yet this should be fixed in my configuration ...
Can somebody help?
Jürgen
--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster
--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster
--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster
