From: Andrew McGregor <andrew@indranet.co.nz>
To: Peter Chubb <peter@chubb.wattle.id.au>, eric@andante.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: ISO-9660 Rock Ridge gives different links different inums
Date: Fri, 10 Jan 2003 16:23:31 +1300 [thread overview]
Message-ID: <1345590000.1042169011@localhost.localdomain> (raw)
In-Reply-To: <15902.14667.489252.346007@wombat.chubb.wattle.id.au>
--On Friday, January 10, 2003 14:08:59 +1100 Peter Chubb
<peter@chubb.wattle.id.au> wrote:
>
> 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.
Shouldn't do, but it will probably make the buffer cache on the server less
effective.
> 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.
Change it to be the offset to the data area, which should be the same for
all of them?
>
> --
> Dr Peter Chubb peterc@gelato.unsw.edu.au
> You are lost in a maze of BitKeeper repositories, all almost the same.
next prev parent reply other threads:[~2003-01-10 3:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-10 3:08 Peter Chubb
2003-01-10 3:23 ` Andrew McGregor [this message]
2003-01-10 3:34 ` Peter Chubb
2003-01-10 6:34 ` Denis Vlasenko
2003-01-10 8:56 ` Peter Chubb
2003-01-10 8:54 ` Denis Vlasenko
2003-01-10 15:58 ` Horst von Brand
2003-01-15 21:07 ` Mark H. Wood
2003-01-15 21:28 ` Jesse Pollard
2003-01-13 22:16 ` Bill Davidsen
2003-01-13 23:10 ` Peter Chubb
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1345590000.1042169011@localhost.localdomain \
--to=andrew@indranet.co.nz \
--cc=eric@andante.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter@chubb.wattle.id.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome