From owner-freebsd-questions Wed Apr 7 8:51:33 1999 Delivered-To: freebsd-questions@freebsd.org Received: from finch-post-10.mail.demon.net (finch-post-10.mail.demon.net [194.217.242.38]) by hub.freebsd.org (Postfix) with ESMTP id 2C75A14EFE for ; Wed, 7 Apr 1999 08:51:24 -0700 (PDT) (envelope-from marko@uk.radan.com) Received: from [158.152.75.22] (helo=uk.radan.com) by finch-post-10.mail.demon.net with smtp (Exim 2.12 #1) id 10UuZu-0005pl-0A for questions@freebsd.org; Wed, 7 Apr 1999 15:49:23 +0000 Organisation: Radan Computational Ltd., Bath, UK. Phone: +44-1225-320320 Fax: +44-1225-320311 Received: from marder-1. (rasnt-1 [193.114.228.211]) by uk.radan.com (8.6.10/8.6.10) with ESMTP id QAA02459 for ; Wed, 7 Apr 1999 16:49:17 +0100 Received: (from marko@localhost) by marder-1. (8.9.2/8.8.8) id QAA02075 for questions@freebsd.org; Wed, 7 Apr 1999 16:45:42 +0100 (BST) (envelope-from marko) Date: Wed, 7 Apr 1999 16:45:42 +0100 From: Mark Ovens To: questions@freebsd.org Subject: Bug in cp(1) or a filesystem problem? Message-ID: <19990407164542.A2018@marder-1.localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I was trying to copy a whole directory tree to a new disk using: ``cp -p -r marko /mnt/usr/'' There's about 29,000 files (~560MB). After about 80% has been copied cp just hangs. ps(1) shows it as idle. I tried again, same thing. I identified the sub-dirs that hadn't been copied and copied them (cp -p -r) one at a time. This worked for all but one directory. I tried several times, but this one dir (which contains sub-dirs) just hangs cp. I dropped to single-user, umnounted the filesystems and fsck'd both the source and target filesystems, no errors reported. I can tar this dir into a file and un-tar it in the new location and all the files are there and ``ls -R'' lists all the files in the source directory and below. It just seems to be cp that has a problem. I made a debug version of cp and ran it from gdb. When it hung I stopped it with Ctrl-Z and did a stack trace. This is the output: ^Z Program received signal SIGTSTP, Stopped (user). 0x804a94c in _open () (gdb) bt #0 0x804a94c in _open () #1 0x8048cb1 in copy_file (entp=0x8070600, dne=1) at utils.c:70 #2 0x8048bb9 in copy (argv=0xefbfdaa8, type=FILE_TO_DIR, fts_options=6) at cp.c:407 #3 0x8048665 in main (argc=1, argv=0xefbfdaa8) at cp.c:240 #4 0x80480e9 in _start () (gdb) Unfortunately this is about the limit of my gdb skills. Can anyone make any sense of this, and tell me why this dir won't copy? Is it a bug in cp or is there possibly a filesystem problem, despite fsck reporting everything is OK? -- FreeBSD - The Power To Serve http://www.freebsd.org My Webpage http://www.users.globalnet.co.uk/~markov _______________________________________________________________ Mark Ovens, CNC Apps Engineer, Radan Computational Ltd. Bath UK CAD/CAM solutions for Sheetmetal Working Industry mailto:marko@uk.radan.com http://www.radan.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message