The plot thickens. I replaced 'cp' with 'rsync' and it worked -- I ran it a few
times and it didn't hang so far.
So on the face of it, it appears that 'cp' is doing something that causes my
system to hang if the files are read from and written to the same pool, but
simply replacing 'cp' with 'rsync' works. Hmmm... anyone have a clue about what
I can do next to home in on the problem with 'cp' ?
Here is the output using 'rsync' :
bash-3.2$ truss -topen rsync -a z1 z2
open("/var/ld/ld.config", O_RDONLY) Err#2 ENOENT
open("/lib/libsocket.so.1", O_RDONLY) = 3
open("/lib/libnsl.so.1", O_RDONLY) = 3
open("/lib/libc.so.1", O_RDONLY) = 3
open("/usr/lib/locale/en_GB.UTF-8/en_GB.UTF-8.so.3", O_RDONLY) = 3
open("/usr/lib/locale/common/methods_unicode.so.3", O_RDONLY) = 3
open64("/etc/popt", O_RDONLY) Err#2 ENOENT
open64("/export/home/simon/.popt", O_RDONLY) Err#2 ENOENT
open("/usr/lib/iconv/UTF-8%UTF-8.so", O_RDONLY) = 3
open64("/var/run/name_service_door", O_RDONLY) = 3
open64("z1/testdir/f01", O_RDONLY) = 5
open64("z1/testdir/f02", O_RDONLY) = 5
open64("z1/testdir/f03", O_RDONLY) = 5
open64("z1/testdir/f04", O_RDONLY) = 5
open64("z1/testdir/f05", O_RDONLY) = 5
open64("z1/testdir/f06", O_RDONLY) = 5
open64("z1/testdir/f07", O_RDONLY) = 5
open64("z1/testdir/f08", O_RDONLY) = 5
open64("z1/testdir/f09", O_RDONLY) = 5
open64("z1/testdir/f10", O_RDONLY) = 5
open64("z1/testdir/f11", O_RDONLY) = 5
open64("z1/testdir/f12", O_RDONLY) = 5
open64("z1/testdir/f13", O_RDONLY) = 5
open64("z1/testdir/f14", O_RDONLY) = 5
open64("z1/testdir/f15", O_RDONLY) = 5
open64("z1/testdir/f16", O_RDONLY) = 5
Received signal #18, SIGCLD, in pollsys() [caught]
siginfo: SIGCLD CLD_EXITED pid=910 status=0x0000
bash-3.2$
This message posted from opensolaris.org
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
