Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1030201AbWLTQg7 (ORCPT ); Wed, 20 Dec 2006 11:36:59 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1030200AbWLTQg7 (ORCPT ); Wed, 20 Dec 2006 11:36:59 -0500 Received: from artax.karlin.mff.cuni.cz ([195.113.31.125]:41058 "EHLO artax.karlin.mff.cuni.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1030198AbWLTQg6 (ORCPT ); Wed, 20 Dec 2006 11:36:58 -0500 Date: Wed, 20 Dec 2006 17:36:57 +0100 (CET) From: Mikulas Patocka To: Miklos Szeredi Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org Subject: Re: Finding hardlinks In-Reply-To: Message-ID: References: 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: 1746 Lines: 41 >> I've came across this problem: how can a userspace program (such as for >> example "cp -a") tell that two files form a hardlink? Comparing inode >> number will break on filesystems that can have more than 2^32 files (NFS3, >> OCFS, SpadFS; kernel developers already implemented iget5_locked for the >> case of colliding inode numbers). Other possibilities: >> >> --- compare not only ino, but all stat entries and make sure that >> i_nlink > 1? >> --- is not 100% reliable either, only lowers failure probability >> --- create a hardlink and watch if i_nlink is increased on both files? >> --- doesn't work on read-only filesystems >> --- compare file content? >> --- "cp -a" won't then corrupt data at least, but will create >> hardlinks where they shouldn't be. >> >> Is there some reliable way how should "cp -a" command determine that? >> Finding in kernel whether two dentries point to the same inode is trivial >> but I am not sure how to let userspace know ... am I missing something? > > The stat64.st_ino field is 64bit, so AFAICS you'd only need to extend > the kstat.ino field to 64bit and fix those filesystems to fill in > kstat correctly. There is 32-bit __st_ino and 64-bit st_ino --- what is their purpose? Some old compatibility code? > SUSv3 requires st_ino/st_dev to be unique within a system so the > application shouldn't need to bend over backwards. I see but kernel needs to be fixed for that. Would patches for changing kstat be accepted? Mikulas > Miklos > - 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/