From mackler@barter.dewline.com  Sat Jul  8 00:14:42 2000
Return-Path: <mackler@barter.dewline.com>
Received: from barter.dewline.com (barter.dewline.com [209.208.153.2])
	by hub.freebsd.org (Postfix) with ESMTP id EB30F37B594
	for <FreeBSD-gnats-submit@freebsd.org>; Sat,  8 Jul 2000 00:14:40 -0700 (PDT)
	(envelope-from mackler@barter.dewline.com)
Received: (from mackler@localhost)
	by barter.dewline.com (8.9.1/8.9.1) id DAA16366;
	Sat, 8 Jul 2000 03:14:40 -0400 (EDT)
Message-Id: <200007080714.DAA16366@barter.dewline.com>
Date: Sat, 8 Jul 2000 03:14:40 -0400 (EDT)
From: mackler-fb@dewline.com
Sender: mackler@barter.dewline.com
Reply-To: mackler-fb@dewline.com
To: FreeBSD-gnats-submit@freebsd.org
Subject: mkisofs 1.12.1 (i386-unknown-freebsd4.0) doesn't preserve hard links
X-Send-Pr-Version: 3.2

>Number:         19782
>Category:       kern
>Synopsis:       mkisofs 1.12.1 (i386-unknown-freebsd4.0) doesn't preserve hard links
>Confidential:   no
>Severity:       non-critical
>Priority:       high
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat Jul 08 00:20:00 PDT 2000
>Closed-Date:    
>Last-Modified:  Sun Jul 01 16:10:30 UTC 2012
>Originator:     Adam Mackler
>Release:        FreeBSD 4.0-STABLE i386
>Organization:
Dewline Communications
>Environment:

	mkisofs 1.12.1 (i386-unknown-freebsd4.0)

>Description:

	When using mkisofs 1.12.1 from the ports collection, hard
	links in the source tree are not preserved in the ISO9660 that mkisofs
	creates.

Joerg Schilling <schilling@fokus.gmd.de>, who is listed on the man page as
the maintainer says by email (7 Jul 2000):

    " . . . send a bugreport to the Freebsd kernel team. Mkisofs is OK,
    the bug is in the FreeBSD filesystem code."

>How-To-Repeat:

	Do this:

	1) make a test directory:
		mkdir /tmp/exampletree

	2) make a test file:
		touch /tmp/exampletree/file1

	3) make a link to the test file:
		ln /tmp/exampletree/file1 /tmp/exampletree/file2

	4) take a look and see the hard link:
		ls -li /tmp/exampletree/

	   see (notice files have same inode):
			total 0
			14 -rw-r--r--  2 mackler  wheel  0 Jul  8 06:48 file1
			14 -rw-r--r--  2 mackler  wheel  0 Jul  8 06:48 file2

	5) use mkisofs to make an iso9660 filesystem:
		mkisofs -o /tmp/iso9660.test /tmp/exampletree/

	6) mount the new iso9660 filesystem:
		vnconfig -cv vn0 /tmp/iso9660.test
		mount_cd9660 /dev/vn0c /mnt

	7) take a look and see the two files are not linked:
		ls -li /mnt 

	   see (notice files have different inodes):
			total 0
			47172 -r-xr-xr-x  1 root  wheel  0 Jul  8 06:48 file1
			47214 -r-xr-xr-x  1 root  wheel  0 Jul  8 06:48 file2

	8) clean up:
		umount /mnt
		vnconfig -u vn0
		rm /tmp/iso9660.test
		rm -rf /tmp/exampletree/

>Fix:


>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: freebsd-bugs->dirk 
Responsible-Changed-By: sheldonh 
Responsible-Changed-When: Mon Jul 10 05:43:24 PDT 2000 
Responsible-Changed-Why:  
Dirk, could you chase up on this?  I realize that the PR 
suggests a bug in a part of FreeBSD which is not your 
area, but since you're the maintainer of the port, you 
might be a good person to run around asking the right 
people the right questions. :-) 

http://www.freebsd.org/cgi/query-pr.cgi?pr=19782 
Responsible-Changed-From-To: dirk->freebsd-ports-bugs 
Responsible-Changed-By: kris 
Responsible-Changed-When: Sat Feb 21 18:00:34 PST 2004 
Responsible-Changed-Why:  
dirk no longer maintains this port 

http://www.freebsd.org/cgi/query-pr.cgi?pr=19782 
Responsible-Changed-From-To: freebsd-ports-bugs->marius 
Responsible-Changed-By: eik 
Responsible-Changed-When: Mon May 10 20:10:38 CEST 2004 
Responsible-Changed-Why:  
over to Marius Strobl, who is the port's maintainer and a src committer ;) 

http://www.freebsd.org/cgi/query-pr.cgi?pr=19782 
State-Changed-From-To: open->analyzed 
State-Changed-By: marius 
State-Changed-When: Tue May 11 08:10:28 PDT 2004 
State-Changed-Why:  

This was "fixed" in sys/isofs/cd9660/cd9660_vnops.c rev. 1.77, which 
in turn broke NFS readdir plus support (PR 63446). While this NFS 
problem is considered second order I somewhat hesitate to just MFC 
cd9660_vnops.c 1.77 and I'm not yet sure what to do in order to also 
fix this in RELENG_4. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=19782 
Responsible-Changed-From-To: marius->freebsd-bugs@FreeBSD.org 
Responsible-Changed-By: marius 
Responsible-Changed-When: Wed Aug 10 21:28:37 GMT 2005 
Responsible-Changed-Why:  

Assign back to the pool as I have have no idea what to do about it (the 
fix in rev. 1.77 of sys/isofs/cd9660/cd9660_vnops.c was backed out in rev. 
1.99 again) and this also isn't about cdrtools/mkisofs (which I also no 
longer maintain). 

http://www.freebsd.org/cgi/query-pr.cgi?pr=19782 

Adding to audit trail manually by bugmeister on 20080125:
 
 bugbuster vwerth@ confirms that this is still a problem with 7.0-RC1.
State-Changed-From-To: analyzed->open 
State-Changed-By: eadler 
State-Changed-When: Sun Jul 1 16:10:29 UTC 2012 
State-Changed-Why:  
unowned PRs must not be in analyzed state 

http://www.freebsd.org/cgi/query-pr.cgi?pr=19782 
>Unformatted:
