[Top] [All Lists]

Re: [reiserfs-list] Re: benchmarks

To: Xuan Baldauf <xuan--reiserfs@xxxxxxxxxxx>, Nikita Danilov <NikitaDanilov@xxxxxxxxx>
Subject: Re: [reiserfs-list] Re: benchmarks
From: Chris Mason <mason@xxxxxxxx>
Date: Tue, 17 Jul 2001 14:26:31 -0400
Cc: Russell Coker <russell@xxxxxxxxxxxx>, Chris Wedgwood <cw@xxxxxxxx>, rsharpe@xxxxxxxxxx, Seth Mos <knuffie@xxxxxxxxx>, Federico Sevilla III <jijo@xxxxxxxxxxxxxxxxxxxx>, linux-xfs@xxxxxxxxxxx, reiserfs-list@xxxxxxxxxxx
In-reply-to: <3B534B74.BDE19961@xxxxxxxxxxx>
Sender: owner-linux-xfs@xxxxxxxxxxx

On Monday, July 16, 2001 10:15:48 PM +0200 Xuan Baldauf
<xuan--reiserfs@xxxxxxxxxxx> wrote:

[ nfs, benchmarks, reiserfs generation number support ]

>>  > P.S.: Hans, how do you prevent object_id|inode reusing? Using
>>  > mount_id+generation counter per mount?
>> There is generation counter stored persistently with super-block,
>> incremented on each inode deletion.
> Is the superblock always logged on inode-deletion for other reasons than
> the generation counter? If not, would the above method be more efficient,
> because it does not require logging superblocks?

inode deletion requires updating the oid map, which lives in the
superblock, so the super is always logged during an inode delete.
deletion/creation usually also involve bitmap changes, which change the
free block count, which ends up logging the super as well.


<Prev in Thread] Current Thread [Next in Thread>