kern/155199: [ext2fs] ext3fs mounted as ext2fs gives I/O errors

Thu Mar 3 05:00:24 UTC 2011

The following reply was made to PR kern/155199; it has been noted by GNATS.

From: Roger Hammerstein <cheeky.m at live.com>
To: <giffunip at tutopia.com>, <bug-followup at freebsd.org>
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

 <html>
 <head>
 <style><!--
 .hmmessage P
 {
 margin:0px=3B
 padding:0px
 }
 body.hmmessage
 {
 font-size: 10pt=3B
 font-family:Tahoma
 }
 --></style>
 </head>
 <body class=3D'hmmessage'>
 Thank you for the followup.<br>&gt=3B Some notes.. from your original posti=
 ng it seemed like<br>&gt=3B the symlink issue was due to our lack of suppor=
 t for<br>&gt=3B fast symlinks. <br><br>At the time=2C I thought it the file=
 system was ext2 and was not expecting<br>those errors.<br>I was doing direc=
 tory listings across the filesystem=2C and the<br>log was showing the g_vfs=
 _done errors.<br>I tracked the log entries to traversals of the symlinks=2C=
  and then posted.<br><br>I hadn't done much individual file accesses at the=
  time.<br><br>&gt=3B The unreadable files are something new. Perhaps they<b=
 r>&gt=3B have extended attributes or ACLs? We don't support<br>&gt=3B those=
  and they would be difficult to support because<br>&gt=3B of implementation=
  differences with our native EAs.<br><br>Nothing special on the files (that=
  I know of).&nbsp=3B They don't have any acls or <br>extended attributes.&n=
 bsp=3B&nbsp=3B Errors occur on mnay different<br>types of files=2C READMEs=
 =2C jpgs=2C mp3s=2C txts=2C gifs.<br>Sometimes in a single directory=2C the=
  first couple of files<br>will read just fine=2C and the rest will give err=
 ors.<br><br> 		 	   		  </body>
 </html>=

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