From owner-freebsd-current@FreeBSD.ORG Tue Jan 8 20:31:45 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A9B4316A419 for ; Tue, 8 Jan 2008 20:31:45 +0000 (UTC) (envelope-from ATRENS@nortel.com) Received: from zrtps0kn.nortel.com (zrtps0kn.nortel.com [47.140.192.55]) by mx1.freebsd.org (Postfix) with ESMTP id 4BE5513C4D9 for ; Tue, 8 Jan 2008 20:31:45 +0000 (UTC) (envelope-from ATRENS@nortel.com) Received: from zcarhxm2.corp.nortel.com (zcarhxm2.corp.nortel.com [47.129.230.99]) by zrtps0kn.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id m08KVXI14863; Tue, 8 Jan 2008 20:31:33 GMT Received: from ab-thinky.atrens.ca ([47.128.181.148] RDNS failed) by zcarhxm2.corp.nortel.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 8 Jan 2008 15:31:17 -0500 Message-ID: <4783DD5C.5020002@nortel.com> Date: Tue, 08 Jan 2008 15:30:20 -0500 From: "Andrew Atrens" User-Agent: Thunderbird 2.0.0.6 (X11/20071028) MIME-Version: 1.0 To: Ollivier Robert References: <200712301219.29839@aldan> <20080102141415.GA15414@keltia.freenix.fr> In-Reply-To: <20080102141415.GA15414@keltia.freenix.fr> X-Enigmail-Version: 0.95.4 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 08 Jan 2008 20:31:17.0935 (UTC) FILETIME=[6C0943F0:01C85235] Cc: freebsd-current@freebsd.org Subject: Re: a new way to hang 7.0 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Jan 2008 20:31:45 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Ollivier Robert wrote: > According to Elliot Finley: >> -L has been hanging systems ever since it existed. Don't use it. > > No, it has been hanging systems _temporarely_ during the creation of the > snapshot, afterwards, it works. If indeed, snapshot creation blocks, there > is a problem, maybe there is not enough space? I've only tried using -L once and this is exactly what happened to me. In a perfect world dump would be able to figure out if there's enough space to make the snapshot before attempting it. At the time I was just using it to migrate to a new larger hd on my new laptop and was single user, though I had all filesystems mounted rw. That last bit was probably just laziness on my part. Anyways I read the manpage, tried -L, and it ran out of space and hung my system. Seemed very ugly at the time. Seems to me in many situations when one is using dump/restore one expects (or hopes) that they'll be as robust as possible. I hope that's enough of a report for dump's maintainer to take a quick try at reproducing the problem. I don't have any free cycles and won't have until the Fall :( - --Andrew -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHg91c8It2CaCdeMwRAkKrAKCBWl6z3SfWPPlqUuvCk2skrLvfVwCfSUtp K3bFIvLc0q0A3ziJLJ0ycFQ= =vG6U -----END PGP SIGNATURE-----