Sachin Palav
2008-Mar-18 19:36 UTC
[zfs-discuss] Solaris 10 x86 + ZFS / NFS server "cp" problem with AIX
Friends, I have recently built a file server on x2200 with solaris x86 having zfs (version4) and running NFS version2 & samba. the AIX 5.2 & AIX 5.2 client give error while running command "cp -R <zfs_nfs_mount_source> <zfs_nfs_mount_desticantion> as below: cp: 0653-440 directory/1: name too long. cp: 0653-438 cannot read directory directory/1. and the cp core dumps in AIX. Can someone please help Thanks Sachin Palav This message posted from opensolaris.org
Michael Schuster
2008-Mar-18 19:47 UTC
[zfs-discuss] Solaris 10 x86 + ZFS / NFS server "cp" problem with AIX
Sachin Palav wrote:> Friends, > I have recently built a file server on x2200 with solaris x86 having zfs (version4) and running NFS version2 & samba. > > the AIX 5.2 & AIX 5.2 client give error while running command "cp -R <zfs_nfs_mount_source> <zfs_nfs_mount_desticantion> as below: > cp: 0653-440 directory/1: name too long. > cp: 0653-438 cannot read directory directory/1. > and the cp core dumps in AIX.I think someone from the AIX camp is probably better suited to answering this, as they hopefully understand under which circumstances AIX''s cp would spit out this kind of error message. HTH Michael -- Michael Schuster http://blogs.sun.com/recursion Recursion, n.: see ''Recursion''
Enda O''Connor
2008-Mar-18 19:57 UTC
[zfs-discuss] Solaris 10 x86 + ZFS / NFS server "cp" problem with AIX
Michael Schuster wrote:> Sachin Palav wrote: > >> Friends, >> I have recently built a file server on x2200 with solaris x86 having zfs (version4) and running NFS version2 & samba. >> >> the AIX 5.2 & AIX 5.2 client give error while running command "cp -R <zfs_nfs_mount_source> <zfs_nfs_mount_desticantion> as below: >> cp: 0653-440 directory/1: name too long. >> cp: 0653-438 cannot read directory directory/1. >> and the cp core dumps in AIX. >> > > I think someone from the AIX camp is probably better suited to answering > this, as they hopefully understand under which circumstances AIX''s cp > would spit out this kind of error message. > > HTH > Michael >Hi seems like CR 6538383 "cp -r" to AIX local dir from NFS-mounted ZFS dir complains "cp: 0653-440 <dir> : name too long." seesm adding -p will get past this one or using find as in: find . | cpio -pdmu else copied in from CR { "There is an old problem with scandir() in libc that was fixed by the following APARs: AIX 5.2: IY59427 AIX 5.3: IY60062 I can''t be certain this is the same problem, but it looks highly likely. There is no APAR for AIX 5.1 as it is out of support. If my fix levels are correct, if you have installed 5.2.0.50 (or later) or 5.3.0.10 (or later) or any level of 6.1 then you''ll have the fix." } Enda
Bryan Wagoner
2008-Mar-18 19:58 UTC
[zfs-discuss] Solaris 10 x86 + ZFS / NFS server "cp" problem
I know nothing of AIX, but as a guess out of air: Since it''s a recursive copy, is it possible one of the filenames in the the tree is just really long or the directory structures are so deep that it passes some AIX limit? This message posted from opensolaris.org
Tim Haley
2008-Mar-18 22:53 UTC
[zfs-discuss] Solaris 10 x86 + ZFS / NFS server "cp" problem with AIX
Sachin Palav wrote:> Friends, > I have recently built a file server on x2200 with solaris x86 having zfs (version4) and running NFS version2 & samba. > > the AIX 5.2 & AIX 5.2 client give error while running command "cp -R <zfs_nfs_mount_source> <zfs_nfs_mount_desticantion> as below: > cp: 0653-440 directory/1: name too long. > cp: 0653-438 cannot read directory directory/1. > and the cp core dumps in AIX. > > Can someone please help >This is almost certainly an instance of 6538383 in our bug database. scandir() is indeed broken on AIX, this is not a ZFS bug. If you have IBM support, you need to file something called a PMR with them to get the ball rolling on a fix. It''s possible someone at Sun opened one already, I''m not certain. The workaround is to use a program that doesn''t rely on scandir() to do the copying, tar or cpio as previously mentioned. Adding the -p option to cp appeared to be a workaround at one point, but that was a red herring, the failure with cp can be intermittent as it involves scandir() scribbling somewhat randomly over memory. -tim> Thanks > Sachin Palav > > > This message posted from opensolaris.org > _______________________________________________ > zfs-discuss mailing list > zfs-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss