From owner-freebsd-current@FreeBSD.ORG Sun Jun 6 13:48:22 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 40D7E16A4CE for ; Sun, 6 Jun 2004 13:48:22 -0700 (PDT) Received: from ganymede.hub.org (u46n208.hfx.eastlink.ca [24.222.46.208]) by mx1.FreeBSD.org (Postfix) with ESMTP id C93D843D45 for ; Sun, 6 Jun 2004 13:48:21 -0700 (PDT) (envelope-from scrappy@hub.org) Received: by ganymede.hub.org (Postfix, from userid 1000) id F33763BF49; Sun, 6 Jun 2004 17:48:14 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id EEEFF3B3D7; Sun, 6 Jun 2004 17:48:14 -0300 (ADT) Date: Sun, 6 Jun 2004 17:48:14 -0300 (ADT) From: "Marc G. Fournier" To: Eirik Oeverby In-Reply-To: <40BEC4D7.8070804@anduin.net> Message-ID: <20040606172659.T88480@ganymede.hub.org> References: <40BEC4D7.8070804@anduin.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed cc: current@freebsd.org Subject: Re: unionfs issues X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Sun, 06 Jun 2004 20:48:22 -0000 Eirik ... can you provide some details on exactly what you are trying to do? For instance, as Dave posts in a follow up, there are several known conditions that will cause a system to panic ... Now, in your case, you say it panic's ... do you have DEBUG enabled and core dumping? That would help to narrow down if its a "known condition" or something new ... On Thu, 3 Jun 2004, Eirik Oeverby wrote: > Hi, > > Recently (3 days ago) I upgraded my main server with 5.2.1, and then > cvsupped to latest current in order to solve some problems in 5.2.1. > Among those was the fact that unionfs was non-functional in the release. > After cvsupping it seemed to work, but when doing some heavy file > copying operations inside a mountpoint the box paniced. > > Problem is - the box is headless, 1000kms away, and with no serial > access. So I'll just ask if this is expected behaviour at the current > state of source, or if those in the know can say anything more about why > this happened and if it has already been fixed. > > I apologise for the vague description of this problem - I know I'm > probably reaching for straws here. > > Wbr., > /Eirik > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664