Date: Sun, 07 Dec 2008 06:18:30 +0000 From: "Bruce M. Simpson" <bms@incunabulum.net> To: josh.carroll@gmail.com Cc: freebsd-fs@freebsd.org, freebsd-stable@freebsd.org, Gonzalo Nemmi <gnemmi@gmail.com> Subject: Re: ext2 inode size patch - RE: PR kern/124621 Message-ID: <493B6AB6.2040704@incunabulum.net> In-Reply-To: <8cb6106e0812040902g69ec2f84t814c2f2b5cdb33f6@mail.gmail.com> References: <8cb6106e0811241129o642dcf28re4ae177c8ccbaa25@mail.gmail.com> <20081125150342.GL2042@deviant.kiev.zoral.com.ua> <8cb6106e0812031453j6dc2f2f4i374145823c084eaa@mail.gmail.com> <200812041747.09040.gnemmi@gmail.com> <8cb6106e0812040902g69ec2f84t814c2f2b5cdb33f6@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
FYI: The ext2 IFS driver for Windows v1.11a also appears to have the
inode size issue:
http://www.fs-driver.org/
I was not able to mount an ext2 filesystem with 256 byte inode size
using this driver. Its installer will see that the filesystem exists,
that it's ext2, but whenever you try to mount, you get nothing -- a very
similar failure mode to the FreeBSD ext2fs driver.
Again, it sounds like the author is actively maintaining it, so it might
be worth contacting him to pool resources.
cheers,
BMS
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?493B6AB6.2040704>