From owner-freebsd-hackers Fri Oct 19 10:43:47 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id D920837B401 for ; Fri, 19 Oct 2001 10:43:44 -0700 (PDT) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id f9JHh8G47321; Fri, 19 Oct 2001 10:43:08 -0700 (PDT) (envelope-from dillon) Date: Fri, 19 Oct 2001 10:43:08 -0700 (PDT) From: Matthew Dillon Message-Id: <200110191743.f9JHh8G47321@apollo.backplane.com> To: Stephen McKay Cc: hackers@FreeBSD.ORG Subject: Re: vmiodirenable vs isofs, some proof References: <200110191315.f9JDFHS20600@dungeon.home> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG -Matt Matthew Dillon :About a month ago I suggested that vfs.vmiodirenable=1 and the cd9660 :file system interract badly. I have not got absolute proof, but I :think fairly good evidence of a causal link. :... :I set vfs.vmiodirenable=0 and copied again. Exactly the same incorrect :files. In other words, the corruption, whatever it is, was not magically :removed by disabling vmiodirenable while the cache remained. Turning off vmiodirenable does not effect things that are already VMIO backed, so this is expected. :I unmounted and remounted the CD. A copy operation was flawless at this :point (vmiodirenable still off). : :I enabled vmiodirenable and the next copy was corrupt in the same manner :(cross linked files), but the set of cross links was different than before. :(Dang, I can't remember if I did another unmount/remount cycle before :this copy. Oh well.) : :At this point, I noticed that the cross links were actual hard links :in my HD copies. (I should have noticed how fast they were copying, I :suppose). :.. :Is this enough for you to form a theory? Any more experiments you :think would be worthwhile? : :Stephen. It sure looks like you can reproduce the bug at will, which is great! Now I need to reproduce it over here. If you could email me an ls -liaR of the CD with vmiodirenable turned off, and another ls -liaR of the CD with vmiodirenable turned on and the corruption present, I should be able to use that to burn a junk CD of my own to try to reproduce the bug. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message