From owner-freebsd-fs@FreeBSD.ORG Tue Apr 1 05:09:29 2008 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 031301066FA8; Tue, 1 Apr 2008 05:09:29 +0000 (UTC) (envelope-from root@mmu.edu.my) Received: from staff.cyber.mmu.edu.my (staff.cyber.mmu.edu.my [203.106.62.12]) by mx1.freebsd.org (Postfix) with ESMTP id EC1B08FC1B; Tue, 1 Apr 2008 05:09:27 +0000 (UTC) (envelope-from root@mmu.edu.my) Received: by staff.cyber.mmu.edu.my (Postfix, from userid 0) id 0FAA44D58D7; Tue, 1 Apr 2008 12:11:03 +0800 (MYT) Received: from mx2.freebsd.org (mx2.freebsd.org [69.147.83.53]) by mmu.edu.my (Postfix) with ESMTP id E4B1755E491 for ; Wed, 26 Mar 2008 23:59:54 +0800 (MYT) Received: from hub.freebsd.org (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id ADC4C1A5B7C; Wed, 26 Mar 2008 15:59:17 +0000 (UTC) (envelope-from owner-freebsd-current@freebsd.org) Received: from hub.freebsd.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id C472E106573A; Wed, 26 Mar 2008 15:59:16 +0000 (UTC) (envelope-from owner-freebsd-current@freebsd.org) 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 A695F106566B; Wed, 26 Mar 2008 15:59:01 +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 7BA3F8FC12; Wed, 26 Mar 2008 15:59:01 +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 8F299125438; Thu, 27 Mar 2008 00:39:20 +0900 (JST) Message-ID: <47EA6E27.3060006@freebsd.org> Date: Thu, 27 Mar 2008 00:39:19 +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> In-Reply-To: <47E9448F.1010304@ipfw.ru> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Sender: owner-freebsd-current@freebsd.org Errors-To: owner-freebsd-current@freebsd.org Cc: freebsd-fs@freebsd.org, freebsd-current@FreeBSD.org, Kurt Jaeger , Robert Watson , dindin@yandex-team.ru Subject: Re: unionfs status X-BeenThere: freebsd-fs@freebsd.org List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Apr 2008 05:09:29 -0000 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 _______________________________________________ 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"