From owner-freebsd-fs@FreeBSD.ORG Sun Feb 15 07:30:47 2004 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9E2BD16A504; Sun, 15 Feb 2004 07:30:47 -0800 (PST) Received: from fons-adae.s.notwork.org (fons-adae.s.notwork.org [218.224.220.115]) by mx1.FreeBSD.org (Postfix) with ESMTP id 372BE43D5F; Sun, 15 Feb 2004 07:30:47 -0800 (PST) (envelope-from mrt@notwork.org) Received: from fons-adae.s.notwork.org (fons-adae.s.notwork.org [IPv6:2001:218:420::3]) by fons-adae.s.notwork.org (Postfix) with ESMTP id 313313493; Mon, 16 Feb 2004 00:30:31 +0900 (JST) To: Yar Tikhiy X-cite: xcite 1.49 From: Murata Shuuichirou In-Reply-To: <20040211183645.GA18497@comp.chem.msu.su> (Yar Tikhiy's message of "Wed, 11 Feb 2004 21:36:45 +0300") References: <87ad41z6ru.fsf@fons-adae.s.notwork.org> <20040211183645.GA18497@comp.chem.msu.su> Date: Mon, 16 Feb 2004 00:30:30 +0900 Message-ID: <87eksw1ht5.fsf@fons-adae.s.notwork.org> User-Agent: Gnus/5.110002 (No Gnus v0.2) Emacs/22.0.0 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii cc: Zack Hobson cc: fs@freebsd.org Subject: Re: updating HFS for 5.2R [patch] X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Feb 2004 15:30:47 -0000 In message <20040211183645.GA18497@comp.chem.msu.su>, `yar@freebsd.org' wrote: > > But, I have not tested this fully and found some problems such as: > > > > 1. Sometime, hfs partitions become unmountable by FreeBSD > > (mount_hfs returns "Invalid argument"), although the > > partition can still be mounted by MacOSX. > > Did you try to fsck_hfs such a broken volume? Ugh, I completely forgot to do fsck. OK, fsck_hfs makes that partition mountable again. (I don't know why MacOSX was able to mount that without fsck) > > 2. After editing files on hfs filesystem with vi(1), umounting > > the filesystem causes these errors: > > > > Feb 2 21:13:11 roma kernel: hfs_fsync: dirty: 0xc2d74000: tag hfs, type VREG, usecount 2, writecount 0, refcount 2, flags (VV_SYSTEM), lock type cnode: EXCL (count 1) by thread 0xc2b42a80 (pid 1068) > > Feb 2 21:13:11 roma kernel: tag VT_HFS, cnid 4, on dev 4, 24 lock type cnode: EXCL (count 1) by thread 0xc2b42a80 (pid 1068) > > (lots of same errors continue) > > > > Then system crashed. > > It's me who introduced this bug. I forgot to unlock > a buffer at one place. Please try the patch attached. Your patch fixes the vi problem here. So HFS+ is now almost usable. -- MURATA Shuuichirou