From: "H. Peter Anvin" <hpa@zytor.com>
To: frank.van.maarseveen@altium.nl
Cc: linux-kernel@vger.kernel.org
Subject: Re: restoring hard linked files from zisofs/iso9660 w. RR
Date: Mon, 28 Jan 2002 11:43:06 -0800 [thread overview]
Message-ID: <3C55A9CA.5050105@zytor.com> (raw)
In-Reply-To: <20020125135545.A28897@espoo.tasking.nl> <a2s67d$8s0$1@cesium.transmeta.com> <20020128170704.A2632@espoo.tasking.nl>
Okay... I have successfully reproduced this bug. It's definitely a Linux
kernel bug -- mkisofs correctly puts file numbers (inode numbers) in the
PX Rock Ridge entries.
Unfortunately it is a pretty deep decision in the Linux isofs that the
inode number is the offset of the directory entry; isofs pretty much needs
to be rewritten to be dentry-centric rather than inode-centric on order to
resolve this. Note that dentry-centric operation is the sane thing for
something like isofs, so this wouldn't be a bad idea.
Unfortunately, that doesn't solve all problems: there is no structure to
the inode numbers provided in the PX entries, and there is the potential
for collision when used on a disc which is only partially RockRidge (which
is legal.) This has to be taken into account, and all of these things
have to be done without reading the whole disc first...
-hpa
prev parent reply other threads:[~2002-01-28 19:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-25 12:55 restoring hard linked files from zisofs/iso9660 w. RR Frank van Maarseveen
2002-01-25 13:28 ` Peter Wächtler
2002-01-25 17:55 ` H. Peter Anvin
2002-01-28 16:07 ` Frank van Maarseveen
2002-01-28 18:46 ` H. Peter Anvin
2002-01-28 19:43 ` H. Peter Anvin [this message]
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=3C55A9CA.5050105@zytor.com \
--to=hpa@zytor.com \
--cc=frank.van.maarseveen@altium.nl \
--cc=linux-kernel@vger.kernel.org \
/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