From owner-freebsd-current@FreeBSD.ORG Wed Jun 2 23:40:48 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 D7A3A16A4CE for ; Wed, 2 Jun 2004 23:40:48 -0700 (PDT) Received: from VARK.homeunix.com (ar59.lsanca2-4.27.98.47.lsanca2.dsl-verizon.net [4.27.98.47]) by mx1.FreeBSD.org (Postfix) with ESMTP id 79F5043D2D for ; Wed, 2 Jun 2004 23:40:46 -0700 (PDT) (envelope-from das@FreeBSD.ORG) Received: from VARK.homeunix.com (localhost [127.0.0.1]) by VARK.homeunix.com (8.12.11/8.12.10) with ESMTP id i536eiPi004642; Wed, 2 Jun 2004 23:40:44 -0700 (PDT) (envelope-from das@FreeBSD.ORG) Received: (from das@localhost) by VARK.homeunix.com (8.12.11/8.12.10/Submit) id i536eie8004641; Wed, 2 Jun 2004 23:40:44 -0700 (PDT) (envelope-from das@FreeBSD.ORG) Date: Wed, 2 Jun 2004 23:40:44 -0700 From: David Schultz To: Eirik Oeverby Message-ID: <20040603064044.GA4505@VARK.homeunix.com> Mail-Followup-To: Eirik Oeverby , current@FreeBSD.ORG References: <40BEC4D7.8070804@anduin.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <40BEC4D7.8070804@anduin.net> 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: Thu, 03 Jun 2004 06:40:49 -0000 On Thu, Jun 03, 2004, Eirik Oeverby wrote: > 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. There are some things that are known to panic unionfs. For instance, certain types of unionfs-on-unionfs layering, FIFOs, and other special files cause panics. Beyond that, all I can say is that unionfs is in need of a maintainer and has a very small userbase, so the problem you face could also be due to bitrot. You're welcome to report any problems you come across, but it would be *much* *much* better if they included patches. In any case, here are some existing PRs you might want to look at first: 50833 51001 51742 51743 52745 54534 55993 56381 66066 66152