From owner-freebsd-questions@FreeBSD.ORG Mon Apr 13 14:13:07 2015 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 37A67409 for ; Mon, 13 Apr 2015 14:13:07 +0000 (UTC) Received: from mail-ig0-x235.google.com (mail-ig0-x235.google.com [IPv6:2607:f8b0:4001:c05::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EFE13FE1 for ; Mon, 13 Apr 2015 14:13:06 +0000 (UTC) Received: by igbqf9 with SMTP id qf9so44761333igb.1 for ; Mon, 13 Apr 2015 07:13:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:date:subject:message-id:priority:in-reply-to:references; bh=V24RhaAgnFd+YBuVB1T0L8EeZGDXj9+T2IIP6zbNNZM=; b=KXrBGh11mB/0fkj7MPx2SUloB3W+zDo+aqDF06iISTXu7bF6AmYXplgcOcWRMx3kAR Hagvf08p5oDtO1N8Dv87ZhItBvWCPO2LbMxWrYUmdauWvGVP6isKAT9cnQxvHzjBvVmM ewz9kTZ0+rhhXZuPIMJqh/5g0tw5iibN00MA4139ZLc2lIAOmwzeEIsPXBue4CFvIaDk ZjEMOAXNJZzj29OOwwEmQ1lvpYBCHheEnHOrSqD+EQPwQhQWpyyN1NCMz2lVDFEK+oSW fxv+mrNZNQQLVwcYq11mOYCJzpmgLjQyUu/qy0v+HiGLhefoXU5/a0HSTWYj24oUpwO9 ISdQ== X-Received: by 10.42.176.70 with SMTP id bd6mr19064037icb.52.1428934386345; Mon, 13 Apr 2015 07:13:06 -0700 (PDT) Received: from [192.168.23.13] (198-84-175-115.cpe.teksavvy.com. [198.84.175.115]) by mx.google.com with ESMTPSA id m191sm5000565ioe.23.2015.04.13.07.13.04 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 13 Apr 2015 07:13:05 -0700 (PDT) From: matheyden@gmail.com To: freebsd-questions@freebsd.org Date: Mon, 13 Apr 2015 10:13:03 -0400 Subject: Re: System hangs on rm after upgrade to 10.1 with UFS Message-ID: <552BCEEF.4096.A69CE8C@matheyden.gmail.com> Priority: normal In-reply-to: <5522A200.9050206@gmx.de> References: <551BFF9C.22917.CCA7BA9B@matheyden.gmail.com>, <5522A200.9050206@gmx.de> X-mailer: Pegasus Mail for Windows (4.70) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Apr 2015 14:13:07 -0000 > On 04/01/15 16:24, matheyden@gmail.com wrote: > > Anyone have any idea what may be causing the problem? Is this a bug in > > FreeBSD 10.1? > > > > Thanks. > > > > _______________________________________________ > > freebsd-questions@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > To unsubscribe, send any mail to > "freebsd-questions-unsubscribe@freebsd.org" > > > Can you give an answer about which file make this problem (dmesg or > other logfile)? > Is this a windows system? They have a little problem with a path over > 255 signs (but this error begins with 240 signs or early). > > Or make you just a little first april joke? > Greeting I'm not sure which file the process gets stuck on, is there an easy way to find out? Nothing appears to be written to the log files when executing the command, outside of the rsnapshot log: http://pastebin.com/uVPfWYtT dmesg: http://pastebin.com/t3HBYH73 My test host is running in VirtualBox on Windows 7, but the issue was first found on a physical system running FreeBSD 10.1 backing up a host running FreeBSD 10.0, so no windows involvement there. Thanks.