Re: Duplicate inodes in 5.4-RELEASE-i386-disc1.iso

From: John Baldwin (jhb_at_FreeBSD.org)
Date: 06/23/05

  • Next message: Dag-Erling Smørgrav: "Re: Duplicate inodes in 5.4-RELEASE-i386-disc1.iso" 
    To: freebsd-hackers@freebsd.org
Date: Thu, 23 Jun 2005 13:37:25 -0400

    On Thursday 23 June 2005 11:45 am, Dag-Erling Smørgrav wrote:
    > Scott Long <scottl@samsco.org> writes:
    > > Gregg Cooper wrote:
    > > > 15005 -r--r--r-- 2 root wheel 0 May 8 03:05 dumpdates
    > > > 15005 -r--r--r-- 2 root wheel 142 May 8 03:05 fbtab
    > > > 83266 -r--r--r-- 2 root wheel 0 May 8 03:01 locale
    > > > 83266 -r--r--r-- 2 root wheel 31 May 8 03:01 mm.tmac
    > > > 83269 -r--r--r-- 2 root wheel 0 May 8 03:01 se_locale
    > > > 83269 -r--r--r-- 2 root wheel 97 May 8 03:01 se_ms.cov
    > > > 99056 -r--r--r-- 2 root wheel 0 May 8 03:05 utmp
    > > > 99056 -r--r--r-- 2 root wheel 18425 May 8 03:04 Makefile.dist
    > >
    > > Maybe it's a bug in mkisofs?
    >
    > ISO 9660 filesystems donn't have inode numbers. The cd9660 code fakes
    > them based on the location of each file's contents. This model breaks
    > down for empty files, which have no contents and thus no meaningful
    > location. Apparently, mkisofs simply keeps track of the last extent
    > written and uses that for the location of the next file regardless of
    > whether it actually has any contents, so empty files get the same
    > inode number as the previous non-empty file.
    >
    > The attached patch will make mkisofs assign the lowest valid non-zero
    > address to all empty files. They will therefore appear to be hard
    > links to eachother, but not to random non-empty files.

    Even if mkisofs is patched this change isn't a bug in mkisofs. It's really a
    bug in our iso9660 filesystem. :( 

    -- 
John Baldwin <jhb@FreeBSD.org>  <><  http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve"  =  http://www.FreeBSD.org
_______________________________________________
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"
  • Next message: Dag-Erling Smørgrav: "Re: Duplicate inodes in 5.4-RELEASE-i386-disc1.iso"

    Relevant Pages

    • Re: Duplicate inodes in 5.4-RELEASE-i386-disc1.iso
      ... ISO 9660 filesystems donn't have inode numbers. ... down for empty files, which have no contents and thus no meaningful ... mkisofs simply keeps track of the last extent ... inode number as the previous non-empty file. ...
      (freebsd-hackers)
    • Re: Duplicate inodes in 5.4-RELEASE-i386-disc1.iso
      ... This model breaks ... >down for empty files, which have no contents and thus no meaningful ... mkisofs simply keeps track of the last extent ... >inode number as the previous non-empty file. ...
      (freebsd-hackers)
    • Re: Linux ISO-9660 Rock Ridge bug needs fix
      ... Well a simple mkisofs some_file> test.iso and mounting that on a loop ... Well I don't know whats the original implementation bug and rock.c seems to ... Scanning testiso ... new fields, in this case assigning inode->i_ino from the new PX entry field, it ...
      (Linux-Kernel)
    • Re: [kde-linux] k3b wont verify data
      ... If you get useful stuff to add to the bug report, ... RBU 100.0% ... I've had a reply from the developer. ...
      (KDE)
    • Re: [kde-linux] k3b wont verify data
      ... If you get useful stuff to add to the bug report, ... RBU 100.0% ... with the same time constraints as ...
      (KDE)