From owner-freebsd-current@FreeBSD.ORG Mon May 7 07:01:11 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D41FF16A407; Mon, 7 May 2007 07:01:11 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from cs1.cs.huji.ac.il (cs1.cs.huji.ac.il [132.65.16.10]) by mx1.freebsd.org (Postfix) with ESMTP id 8A63513C484; Mon, 7 May 2007 07:01:11 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by cs1.cs.huji.ac.il with esmtp id 1HkxDa-00082U-3D; Mon, 07 May 2007 10:01:10 +0300 X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.2 To: Kostik Belousov In-reply-to: <20070506160056.GE83173@deviant.kiev.zoral.com.ua> References: <20070506093034.GA42976@freebsd.org> <20070506160056.GE83173@deviant.kiev.zoral.com.ua> Comments: In-reply-to Kostik Belousov message dated "Sun, 06 May 2007 19:00:56 +0300." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 07 May 2007 10:01:10 +0300 From: Danny Braniss Message-ID: Cc: Roman Divacky , FreeBSD Current Subject: Re: [ANN] unionfs patchset-19-20070504 release, it is now MPSAFE and transparent mode as default 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: Mon, 07 May 2007 07:01:11 -0000 > On Sun, May 06, 2007 at 11:30:34AM +0200, Roman Divacky wrote: > > > Hi, > > > So far I've tested it under -current, in my diskless env. where > > > /etc & /compat/linux are unionfs'ed with a mfs, and so all seems OK. > >=20 > > there's an XXX in the linuxulator code saying: > >=20 > > XXX Untested vs. mount -o union; probably does the wrong thing. > >=20 > > can you confirm that it works ok with unionfs from daichi? > > There are to quite different union-kind things in kernel. One is the -o uni= > on > option for the mount, see mount(2). Second is unionfs proper. > > The first thing (-o union) requires support in namei and related syscalls, > like getdirentries. It is implemented for native freebsd getdirentries (both > current and 4-compat variants), but, AFAIR, is _not_ implemented in > compat syscalls implementations for sysv, linux, xenix etc. And, in fact, > making that compat syscalls behave is somewhat tricky due to cookies and > differences between supposed output formats for ABIs. > > Unionfs shall have no real difference in behaviour what used from processes > using compat ABIs. > well, it seems that there is a problem: I have /compat/linux union mounted with a memory fs - because / is diskless, and linux likes to write to etc, var), so far, so good, but mount -t linprocfs linproc /compat/linux/proc failes: mountd[874]: can't delete exports for /home/dist/local/amd64=FreeBSD_7.0/compat /linux/proc: Invalid argument unionfs does not support mount update though I don't think the problem is in the unionfs code ... danny