updating HFS for 5.2R [patch]
mrt at notwork.org
Sun Feb 15 07:30:47 PST 2004
In message <20040211183645.GA18497 at comp.chem.msu.su>,
`yar at 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.
More information about the freebsd-fs