From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 11 08:29:12 2012 Return-Path: Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5013C106564A for ; Wed, 11 Apr 2012 08:29:12 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from shell0.rawbw.com (shell0.rawbw.com [198.144.192.45]) by mx1.freebsd.org (Postfix) with ESMTP id 372038FC0A for ; Wed, 11 Apr 2012 08:29:12 +0000 (UTC) Received: from eagle.yuri.org (stunnel@localhost [127.0.0.1]) (authenticated bits=0) by shell0.rawbw.com (8.14.4/8.14.4) with ESMTP id q3B8T53W094300 for ; Wed, 11 Apr 2012 01:29:06 -0700 (PDT) (envelope-from yuri@rawbw.com) Message-ID: <4F8540D1.5070100@rawbw.com> Date: Wed, 11 Apr 2012 01:29:05 -0700 From: Yuri User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:10.0.3) Gecko/20120316 Thunderbird/10.0.3 MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: cp -R from the mounted ufs disk image hangs in DL+ vnread X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Apr 2012 08:29:12 -0000 I have an 82GB UFS image file (ufs-snapshot) mounted on some directory ufs-snapshot.mount. (mount /dev/`mdconfig -a -t vnode -f ufs-snapshot` ufs-snapshot.mount) Command 'cp -R ufs-snapshot.mount/usr other-dir/' hanged in the middle with DL+ status: $ ps ax | grep cp 73635 10 DL+ 0:12.19 cp -R ufs-snapshot.mount/usr other-dir/ 'top' shows it in vnread state: 73635 root 1 20 0 10084K 2672K vnread 1 0:12 0.00% cp When I ran 'ls' in the same mounted directory it hanged too with D+ status: $ ps ax | grep ls 75882 2 D+ 0:00.00 ls ufs-snapshot.mount/ What is happening? Why cp and ls hanged? I think, cp -R hanged first and later ls is waiting on some op initiated by cp -R. Somehow, cp -R managed to hang itself. How can I find out what cp is waiting on? 9.0-STABLE amd64 Yuri