From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jiro SEKIBA Subject: Re: How does NILFS2 handle directory management Date: Mon, 28 Sep 2009 08:03:17 +0900 Message-ID: <87my4gq9ca.wl%jir@sekiba.com> References: <20090925122109.GD6624@aardappel.13thmonkey.org> <20090926.004730.113223425.ryusuke@osrg.net> <20090925162334.GA14945@aardappel.13thmonkey.org> <20090926.101634.31873031.ryusuke@osrg.net> <20090927221049.GA14618@aardappel.13thmonkey.org> Reply-To: NILFS Users mailing list Mime-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20090927221049.GA14618-5cYspOl2ggRz6xQTk39kMVfVdRo2wo/d@public.gmane.org> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: users-bounces-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org Errors-To: users-bounces-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org To: NILFS Users mailing list Cc: Reinoud Zandijk Hi, At Mon, 28 Sep 2009 00:10:49 +0200, Reinoud Zandijk wrote: > > Hi Ryusuke, > > On Sat, Sep 26, 2009 at 10:16:34AM +0900, Ryusuke Konishi wrote: > > > The Ext3 approach also is hacky and shoe-horned. How can it even see if the > > > hash table is still OK? an Ext2 system could have radically reformed and > > > reformatted the dirents. > > > > One of the reason I see it as a candidate is that it keeps both > > backward and forward compatibility. And, we can see the applicable > > code in front of our eyes. > > Ext3 hash correctness detection thus works ONLY if the first entry is indeed > recycled on a directory entry creation. If not, its pointing to garbage..... When older code see that block, entire block has one virtual entry, which is the first fake entry. Rest of the block is seemed to be body of the first entry. So actually, there is only one entry on the block. Therefore, that is the only case to be recycled. thanks, regards, -- Jiro SEKIBA