Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754757AbXAAXW4 (ORCPT ); Mon, 1 Jan 2007 18:22:56 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754748AbXAAXW4 (ORCPT ); Mon, 1 Jan 2007 18:22:56 -0500 Received: from artax.karlin.mff.cuni.cz ([195.113.31.125]:56910 "EHLO artax.karlin.mff.cuni.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754747AbXAAXWz (ORCPT ); Mon, 1 Jan 2007 18:22:55 -0500 Date: Tue, 2 Jan 2007 00:22:54 +0100 (CET) From: Mikulas Patocka To: Nikita Danilov Cc: Arjan van de Ven , Benny Halevy , Jan Harkes , Miklos Szeredi , linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, nfsv4@ietf.org Subject: Re: Finding hardlinks In-Reply-To: <17817.37844.730977.13636@gargle.gargle.HOWL> Message-ID: References: <20061221185850.GA16807@delft.aura.cs.cmu.edu> <1166869106.3281.587.camel@laptopd505.fenrus.org> <4593890C.8030207@panasas.com> <1167300352.3281.4183.camel@laptopd505.fenrus.org> <1167388475.6106.51.camel@lade.trondhjem.org> <17816.29254.497543.329777@gargle.gargle.HOWL> <17817.37844.730977.13636@gargle.gargle.HOWL> X-Personality-Disorder: Schizoid MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1049 Lines: 24 > > BTW. How does ReiserFS find that a given inode number (or object ID in > > ReiserFS terminology) is free before assigning it to new file/directory? > > reiserfs v3 has an extent map of free object identifiers in > super-block. Inode free space can have at most 2^31 extents --- if inode numbers alternate between "allocated", "free". How do you pack it to superblock? > reiser4 used 64 bit object identifiers without reuse. So you are going to hit the same problem as I did with SpadFS --- you can't export 64-bit inode number to userspace (programs without -D_FILE_OFFSET_BITS=64 will have stat() randomly failing with EOVERFLOW then) and if you export only 32-bit number, it will eventually wrap-around and colliding st_ino will cause data corruption with many userspace programs. Mikulas - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/