Re: ext2fs panic with Dfly 1.5.2

[Matthew Dillon <dillon@xxxxxxxxxxxxxxxxxxxx>]

:
:But take a look at the effect of the
:
:  "Major BUF/BIO work commit.  Make I/O BIO-centric and specify the disk or
:  file location with a 64 bit offset instead of a 32 bit block number."
:
:patch on sys/vfs/ufs/ufs_bmap.c :
:
:  http://www.dragonflybsd.org/cvsweb/src/sys/vfs/ufs/ufs_bmap.c.diff?r1=1.9&r2=1.10&f=h 
:
:Unlike the old ones, the new ufs_bmap() and ufs_bmaparray() utilizes an "fs"
:thingy, which is initialized like this:
:
:sys/vfs/ufs/ufs_bmap.c :
:----------------------------
:fs = VTOI(ap->a_vp)->i_fs;
:----------------------------
:
:Here the VTOI macro gives back the private field of the vnode as a struct
:inode, which is fine for both of ufs and ext2fs. But fetching "i_fs" is bogus
:...

    Yah, I think you are right.  EXT2FS can't share UFS's routines any 
    more.

    I'll have a go at making ext2-private versions of all the UFS routines.
    I don't yet know how hard (or easy) it will turn out to be.

						-Matt