I installed b87 today and then I made a copy of a directory. To my surprise, a few seconds later the drive access light went out. Upon inspection, only a couple of the files had been copied, and the cp command appeared to have hung.
I did: cp -r dir1 dir2 ps -el showed that cp was still running but not taking much, if any, processor time. Nothing changed after a minute or so, so I tried to kill the cp process with -15, then a -9. Even that failed. Using the file manager (nautilus?), all I saw was a spinning logo and no files when I tried to access the directory where I copied data to. Thinking this was a bug in b87, I rolled back to b85. Back in b85, I tried the same thing, and again, it failed in exactly the same way. So it was nothing to do with b87, but in fact, something funny to do with my files. I did a scrub and saw no errors. What I now need to do is diagnose the problem. What do people here suggest I do next to find the root cause of this problem? I suspect there's something screwy with the files in the source directory -- some funny attribute somewhere (I remember some bug in b82 with file dates around 1970 or something). Luckily this directory didn't contain many files and I have a copy anyway, and the data is not critical. --------------------------------- Blog: http://breden.org.uk --------------------------------- This message posted from opensolaris.org _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
