From owner-freebsd-current@FreeBSD.ORG Tue Apr 15 06:42:31 2008 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6DAF11065674; Tue, 15 Apr 2008 06:42:31 +0000 (UTC) (envelope-from daichi@freebsd.org) Received: from natial.ongs.co.jp (natial.ongs.co.jp [202.216.246.90]) by mx1.freebsd.org (Postfix) with ESMTP id 3B3198FC3A; Tue, 15 Apr 2008 06:42:31 +0000 (UTC) (envelope-from daichi@freebsd.org) Received: from parancell.ongs.co.jp (dullmdaler.ongs.co.jp [202.216.246.94]) by natial.ongs.co.jp (Postfix) with ESMTP id 1DC47125423; Tue, 15 Apr 2008 15:42:30 +0900 (JST) Message-ID: <48044E55.9060903@freebsd.org> Date: Tue, 15 Apr 2008 15:42:29 +0900 From: Daichi GOTO User-Agent: Thunderbird 2.0.0.12 (X11/20080325) MIME-Version: 1.0 To: "Alexander V. Chernikov" References: <47E9448F.1010304@ipfw.ru> <47EA6E27.3060006@freebsd.org> In-Reply-To: <47EA6E27.3060006@freebsd.org> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Cc: Masanori OZAWA , dindin@yandex-team.ru, freebsd-fs@freebsd.org, freebsd-current@FreeBSD.org, Robert Watson , Kurt Jaeger Subject: Re: unionfs status 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: Tue, 15 Apr 2008 06:42:31 -0000 If anyone has no problems with p20-1 to p20-4, I am going to commit it to HEAD. About p20-5, rwatson have pointed out that it maybe has the same socket problem, so we are going to research for more while ;) Daichi GOTO wrote: > I should say that so sorry of my slow response. so sorry. > > We are developing unionfs step by step and still have 5 next patches. > > http://people.freebsd.org/~daichi/unionfs/experiments/ > http://people.freebsd.org/~daichi/unionfs/experiments/unionfs-p20-1.diff > http://people.freebsd.org/~daichi/unionfs/experiments/unionfs-p20-2.diff > http://people.freebsd.org/~daichi/unionfs/experiments/unionfs-p20-3.diff > http://people.freebsd.org/~daichi/unionfs/experiments/unionfs-p20-4.diff > http://people.freebsd.org/~daichi/unionfs/experiments/unionfs-p20-5.diff > > p20-1: > leads panic when "no error happens, eofflag is 0, response data is empty > and DIAGNOSTIC is defined" while involving VOP_READDIR(9) from unionfs. > This change fixes system hang-up using with NFS. > > p20-2: > fixed fs access issue mounting on devfs. > > p20-3: > fixed kern/109377. > > p20-4: > fixed rename panic issue > > p20-5: > fixed unix socket connection issue > > On our long unionfs running test, It looks like works very well. Would you > try above patches? So sorry of my slow response. Please accept my deepest > apology. > > We are planing to commit above patches to 8-current. 7-release has been > done. It is good time to commit it to current ;) > > Alexander V. Chernikov wrote: >> Hello people! >> >> At this moment unionfs has got at least following problems: >> 1) File systems cannot mount onto upper/lower unionfs layer (partially >> described in kern/117829) >> 2) There are problems with multithreaded programs accessing(writing) >> files on unionfs (kern/109950) >> 3) As well there are problems with accessing unix sockets created on >> upper/lower unionfs layers (kern/118346) >> 4) Doing mv filename same-filename causes kernel to panic on 6.X (and >> printing warning about VOP_RENAME in 7+) >> 5) Making 'loops' when mounting unionfs causes kernel panic (kern/121385) >> >> I have made patches solving first 4 problems >> These patches are available at http://ipfw.ru/patches/ >> unionfs2.diff fixes fs mounting onto upper layer, unionfs_lmount.diff >> fixes lower >> unionfs_threads.diff and unionfs_unix.diff fixes cases 2) and 3) >> unionfs_rename.diff fixes case with renaming >> >> Can anybody comment/review ? > -- Daichi GOTO, http://people.freebsd.org/~daichi