Date: Mon, 16 Feb 2004 00:30:30 +0900 From: Murata Shuuichirou <mrt@notwork.org> To: Yar Tikhiy <yar@freebsd.org> Cc: fs@freebsd.org Subject: Re: updating HFS for 5.2R [patch] Message-ID: <87eksw1ht5.fsf@fons-adae.s.notwork.org> In-Reply-To: <20040211183645.GA18497@comp.chem.msu.su> (Yar Tikhiy's message of "Wed, 11 Feb 2004 21:36:45 %2B0300") References: <87ad41z6ru.fsf@fons-adae.s.notwork.org> <20040211183645.GA18497@comp.chem.msu.su>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?87eksw1ht5.fsf>