From owner-freebsd-questions  Mon Jun 19 12:14:47 2000
Delivered-To: freebsd-questions@freebsd.org
Received: from gandalf.cc.purdue.edu (gandalf.cc.purdue.edu [128.210.135.25])
	by hub.freebsd.org (Postfix) with ESMTP id B7C5937BBCE
	for <freebsd-questions@freebsd.org>; Mon, 19 Jun 2000 12:14:39 -0700 (PDT)
	(envelope-from jrj@gandalf.cc.purdue.edu)
Received: from gandalf.cc.purdue.edu (jrj@localhost [127.0.0.1])
	by gandalf.cc.purdue.edu (8.9.1/8.9.1) with ESMTP id OAA14319;
	Mon, 19 Jun 2000 14:14:29 -0500 (EST)
Message-Id: <200006191914.OAA14319@gandalf.cc.purdue.edu>
To: Palle Girgensohn <girgen@partitur.se>
Cc: freebsd-questions@freebsd.org, amanda-users@amanda.org
Subject: Re: hanging dump process 
In-reply-to: Your message of "Mon, 19 Jun 2000 14:11:27 +0200."
             <394E0DEF.B11E9CE1@partitur.se> 
Reply-To: jrj@cc.purdue.edu
Date: Mon, 19 Jun 2000 14:14:29 -0500
From: "John R. Jackson" <jrj@gandalf.cc.purdue.edu>
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>?   DUMP: read error from /dev/vinum/slask: Input/output error: [block -1629160098]: count=3072
>...
>I was puzzled by the error ...

This is typical of a file changing out from under dump while it's running.
Normally it will recover and go on or else abandon that file system.

>... and tried umounting the disk and
>fsck'ing. fsck finished without errors, but remounting the disk
>rendered a device busy error. It turned out that amanda was
>hanging around still trying to dump the filesystem. I'm stuck,
>it seems, and cannot even kill -9 the dump processes, and
>cannot mount the fs until the processes are dead.

If you can't kill -9 them, then you're probably out of luck.  Note that
this is not an Amanda problem, but a dump (or OS) problem.

>Palle

John R. Jackson, Technical Software Specialist, jrj@purdue.edu


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message