From owner-freebsd-questions@FreeBSD.ORG Tue Jun 21 07:52:12 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5778F16A41C for ; Tue, 21 Jun 2005 07:52:12 +0000 (GMT) (envelope-from freminlins@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1171343D53 for ; Tue, 21 Jun 2005 07:52:11 +0000 (GMT) (envelope-from freminlins@gmail.com) Received: by wproxy.gmail.com with SMTP id 68so1239605wra for ; Tue, 21 Jun 2005 00:52:11 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=hrP/gyhmOZkrUQtQpAv2dTtKyzX8owylqrn3kpFxfrlDYOFd/yaArin6BlSYFhKQW9Z9luFqfNZrB+MGDcAwDGiZOteaE7LDZLckp8Ucx+Ei8zkjNRVGZnsEl6wBvdCLL9UrVxg5fYE1pVkbn9bFWa2O8XSnXoDMA0+GQYaIyLc= Received: by 10.54.91.12 with SMTP id o12mr3020101wrb; Tue, 21 Jun 2005 00:52:11 -0700 (PDT) Received: by 10.54.94.7 with HTTP; Tue, 21 Jun 2005 00:52:11 -0700 (PDT) Message-ID: Date: Tue, 21 Jun 2005 08:52:11 +0100 From: Freminlins To: freebsd-questions@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Subject: dump with -L flag - machine truely unresponsive X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Freminlins List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Jun 2005 07:52:12 -0000 I have a FreeBSD 5.4 machine with a SCSI hard drive. I dump all our machines onto a nfs-mounted filer. There are some files which it's important not to clobber during the dump, so I've been experimenting with dump using the -L flag like so: dump auLf /var /mnt/dump/var What I have noticed is that during the time that the machine is taking its snapshot, it becomes completely unreachable on the net. It is impossible to ssh or even ping it. Our monitoring reports that the machine has dropped off the net, but once the snapshot is finished it is available again. The machine itself does not drop, it just appears to drop. Has anyone seen this before? I certainly haven't. And if so, does anyone have a fix (apart from going back to dump without -L)? For info the partitions are suspended during the snapshot for these amounts of time: Jun 21 03:00:08 gia kernel: /: suspended 7.003 sec, redo 0 of 4 Jun 21 03:08:41 gia kernel: /var: suspended 57.036 sec, redo 25 of 2775 Jun 21 03:22:19 gia kernel: /home: suspended 1.037 sec, redo 0 of 4 Jun 21 03:23:56 gia kernel: /usr: suspended 40.246 sec, redo 0 of 14 Thanks, Frem.