From owner-freebsd-fs@FreeBSD.ORG Thu Mar 3 05:00:23 2011 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E2F00106564A for ; Thu, 3 Mar 2011 05:00:23 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id CF79F8FC16 for ; Thu, 3 Mar 2011 05:00:23 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p2350Nvj070400 for ; Thu, 3 Mar 2011 05:00:23 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p2350NS7070391; Thu, 3 Mar 2011 05:00:23 GMT (envelope-from gnats) Date: Thu, 3 Mar 2011 05:00:23 GMT Message-Id: <201103030500.p2350NS7070391@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: Roger Hammerstein Cc: Subject: RE: kern/155199: [ext2fs] ext3fs mounted as ext2fs gives I/O errors X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Roger Hammerstein List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Mar 2011 05:00:24 -0000 The following reply was made to PR kern/155199; it has been noted by GNATS. From: Roger Hammerstein To: , Cc: Subject: RE: kern/155199: [ext2fs] ext3fs mounted as ext2fs gives I/O errors Date: Wed, 2 Mar 2011 23:43:18 -0500 --_6f81a817-3b1a-463b-b71c-49f0f91b67a5_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Thank you for the followup. > Some notes.. from your original posting it seemed like > the symlink issue was due to our lack of support for > fast symlinks.=20 At the time=2C I thought it the filesystem was ext2 and was not expecting those errors. I was doing directory listings across the filesystem=2C and the log was showing the g_vfs_done errors. I tracked the log entries to traversals of the symlinks=2C and then posted. I hadn't done much individual file accesses at the time. > The unreadable files are something new. Perhaps they > have extended attributes or ACLs? We don't support > those and they would be difficult to support because > of implementation differences with our native EAs. Nothing special on the files (that I know of). They don't have any acls or= =20 extended attributes. Errors occur on mnay different types of files=2C READMEs=2C jpgs=2C mp3s=2C txts=2C gifs. Sometimes in a single directory=2C the first couple of files will read just fine=2C and the rest will give errors. = --_6f81a817-3b1a-463b-b71c-49f0f91b67a5_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Thank you for the followup.
>=3B Some notes.. from your original posti= ng it seemed like
>=3B the symlink issue was due to our lack of suppor= t for
>=3B fast symlinks.

At the time=2C I thought it the file= system was ext2 and was not expecting
those errors.
I was doing direc= tory listings across the filesystem=2C and the
log was showing the g_vfs= _done errors.
I tracked the log entries to traversals of the symlinks=2C= and then posted.

I hadn't done much individual file accesses at the= time.

>=3B The unreadable files are something new. Perhaps they>=3B have extended attributes or ACLs? We don't support
>=3B those= and they would be difficult to support because
>=3B of implementation= differences with our native EAs.

Nothing special on the files (that= I know of). =3B They don't have any acls or
extended attributes.&n= bsp=3B =3B Errors occur on mnay different
types of files=2C READMEs= =2C jpgs=2C mp3s=2C txts=2C gifs.
Sometimes in a single directory=2C the= first couple of files
will read just fine=2C and the rest will give err= ors.

= --_6f81a817-3b1a-463b-b71c-49f0f91b67a5_--