From owner-freebsd-questions@FreeBSD.ORG Mon Oct 1 18:03:16 2012 Return-Path: Delivered-To: questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 40A8A106566B for ; Mon, 1 Oct 2012 18:03:16 +0000 (UTC) (envelope-from jguojun@sbcglobal.net) Received: from nm11-vm0.bullet.mail.bf1.yahoo.com (nm11-vm0.bullet.mail.bf1.yahoo.com [98.139.213.136]) by mx1.freebsd.org (Postfix) with SMTP id D7EC88FC08 for ; Mon, 1 Oct 2012 18:03:15 +0000 (UTC) Received: from [98.139.212.146] by nm11.bullet.mail.bf1.yahoo.com with NNFMP; 01 Oct 2012 18:00:58 -0000 Received: from [66.94.237.110] by tm3.bullet.mail.bf1.yahoo.com with NNFMP; 01 Oct 2012 18:00:57 -0000 Received: from [127.0.0.1] by omp1015.access.mail.mud.yahoo.com with NNFMP; 01 Oct 2012 18:00:57 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 881568.73857.bm@omp1015.access.mail.mud.yahoo.com Received: (qmail 77574 invoked by uid 60001); 1 Oct 2012 18:00:57 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sbcglobal.net; s=s1024; t=1349114457; bh=BEm3yVxG4oKoIhpJkzFBtZf1kPmnqD01gaDswHKtmPc=; h=X-YMail-OSG:Received:X-Mailer:References:Message-ID:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=KwSqbjK/Eu0RZIFIObXtWf0TyU6W6uElFczN20zPdLz2xvy9oWFGpX9cqb+lPkZ4Y3YG1uNzWaOY1jv3J0ZkDRhES+X3S0xYcSyoF3XZkr2IK/Q60M75THSe8uLQ5pyrr7ipe8ZscI8Z7G+8XYqCxgZqSguAb0KQwavRQYN9kuA= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=sbcglobal.net; h=X-YMail-OSG:Received:X-Mailer:References:Message-ID:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=I4lbmWdkrtAazU6jxa0iJ6RNK3mlILaXrKOfrzW9Bm+pzbPa4olIgJtAslX99k6zD2VbJPANjqQXqEIw0hULMjakL3DLILB4m7pIGKoYaCK9DropFWNwbE7P093TuWOtqohLoV54ZWmLyOjKI8j+Zft0tCQ6sV0+qVfEcFYHQck=; X-YMail-OSG: aiyQ6R8VM1kUP.v.sntgPO1aFXgEwPVau9BHz3kowb.pGlR Ziq3gPMA6w1C3hAS3HA073J4Ljc1MpNkNvAGt_OxCs88qIt6maw7ibfrdlSG ZdrDwxcazvLyMiQV5k6gx.IxTHPcPN8oTjOapo6YwYdygbheNPRGrF4UjuXc toMqdk.Ys5W3mdmrQsTsCL1HWjZEVy2Q8pDwGoecj2i6caVy_G3cT4zAnv6c HIa1L_AJL03JUmL5d4l1kKv7wTshgB_v0MIqJcoUqlNTSNwnTIB8ziGUrAQ6 Y8lWVOy8ryhSszHTm9H2lLpIU2TixuWxJvE8Za12tdztL_qHTX7C3zSef0R4 2nqGqM8IhsyQZQZTDzOwJ8pcuN1kBnJn9fIaBFmIZ8SedeXgK8yvIWvqisLu cdstY9EUwAxCRngwcEeb9PJtoPQ.g6SFRUSpsrYnCrxD805kAiFuU0x4asDS 9NZ556xgTkEl4BoDRDZI4SBR2SXKi8kG3pcgWOk3HYwXmy9NGqmxnRyjUmL9 sWky. Received: from [75.37.1.111] by web180904.mail.ne1.yahoo.com via HTTP; Mon, 01 Oct 2012 11:00:57 PDT X-Mailer: YahooMailRC/708 YahooMailWebService/0.8.122.442 References: <1348984196.37002.YahooMailRC@web180906.mail.ne1.yahoo.com> <5068A688.4070100@delphij.net> Message-ID: <1349114457.65907.YahooMailRC@web180904.mail.ne1.yahoo.com> Date: Mon, 1 Oct 2012 11:00:57 -0700 (PDT) From: Jin Guojun To: d@delphij.net In-Reply-To: <5068A688.4070100@delphij.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: hackers@freebsd.org, questions@freebsd.org Subject: Re: system hangs during dump + compress > usb2-drive X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Oct 2012 18:03:16 -0000 ________________________________ From: Xin Li To: Jin Guojun Cc: questions@freebsd.org; hackers@freebsd.org Sent: Sun, September 30, 2012 1:07:40 PM Subject: Re: system hangs during dump + compress > usb2-drive On 9/29/12 10:49 PM, Jin Guojun wrote: > In FreeBSD 8.3 release (possibly in earlier release), dump a file > system has 2-3GB or more content can cause system hang in a > specific case (pipe to compression): > > dump FS-on-SATA-drive > usb-drive OK dump FS-on-SATA-drive > | anyCompress > sata-drive OK mv a-large-dump-file from > STAT drive to a USB drive OK dump small-FS-on-SATA-drive | > anyCompress > usb-drive OK small -- 1.8GB or less dump > large-FS-on-SATA-drive | anyCompress > usb-drive hang > content is 3GB or larger (did not try around 2GB yet) > > When system hangs, no sub system, such video, network, etc, will > function. Typically, the unfinished compressed dump file is around > 1.5-2.7GB, so guessing dumped file content is close to or over 2GB > when failure occurred. > > Has anyone encountered the same problem? > > Because this usually takes a few hours to occur, this is hard to > watch how/when it happens. Is any way to debug or determine what > status the system is? For starters I'd use a different console for doing procstat -kk -a and see what the system is doing. (Perhaps also top) I *think* that if it's just hanging for some time, it's probably because the system is trying to take a snapshot? It takes time on UFS when creating and removing the snapshot. Just a guess... Cheers, --------------- Not sure how to use a different console. No tty is functioning (neither ttyv? nor over network). You are right on a different case -- mount /dev/da0s4d /mnt # mount a usb drive cd /mnt ssh remote-liux-host "tar -cf - 8GB_FS" | tar -xf - In this case, doing ls -l /mnt or df will hangs, but system is still alive. The network is 45Mbps. I have no idea how long it took the tar to finish since machine is 60 km away. When I left there last Friday, only 400MB was done in one hour. I will get the processing time tomorrow. The problem we can see now is that tar (probably the pipe) process only finish with 4GB. # df Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/ad4s3a 1012974 355348 576590 38% / devfs 1 1 0 100% /dev ... /dev/da0s4d 1027486774 4198246 941089588 0% /mnt So, I suspect this is a pipe problem, not a compress issue.