lkml.org 
[lkml]   [2003]   [Jan]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
Date
SubjectISO-9660 Rock Ridge gives different links different inums

In linux 2.5.54, multiple links to the same file on a rock-ridge CD
have different inode numbers. This confuses cpio, tar and cp -ra
because the multiple links are each copied separately as a single file.

It'll probably also confuse NFS, but I haven't tried that.

Example from the knoppix CD:

$ ls -il gunzip gzip uncompress zcat
1896278 -rwxr-xr-x 4 root root 49256 Oct 10 01:31 gunzip
1896564 -rwxr-xr-x 4 root root 49256 Oct 10 01:31 gzip
1902292 -rwxr-xr-x 4 root root 49256 Oct 10 01:31 uncompress
1902856 -rwxr-xr-x 4 root root 49256 Oct 10 01:31 zcat

(For comparison, here's what I see on XFS:
100663485 -rwxr-xr-x 4 root root 49288 Nov 7 11:37 gunzip
100663485 -rwxr-xr-x 4 root root 49288 Nov 7 11:37 gzip
100663485 -rwxr-xr-x 4 root root 49288 Nov 7 11:37 uncompress
100663485 -rwxr-xr-x 4 root root 49288 Nov 7 11:37 zcat
)


Currently the inode number appears to be the offset in bytes from the start of
the file system to the iso directory entry. Files with multiple
directory entries (i.e., links) therefore have different inums.

I don't know enough about the ISO9660 standard to be sure what's best
to do about this.

--
Dr Peter Chubb peterc@gelato.unsw.edu.au
You are lost in a maze of BitKeeper repositories, all almost the same.
-
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/

\
 
 \ /
  Last update: 2005-03-22 13:32    [W:0.067 / U:3.768 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site