Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 87658

Summary:	mount --bind creates directories with shared dev/ino
Product:	[Retired] Red Hat Linux	Reporter:	Tim Waugh <twaugh>
Component:	kernel	Assignee:	Arjan van de Ven <arjanv>
Status:	CLOSED WONTFIX	QA Contact:	Brian Brock <bbrock>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	9	CC:	mitr, wtogami
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2004-09-30 15:40:42 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	86302

Description Tim Waugh 2003-03-31 22:58:23 UTC

Description of problem:
The device/inode numbers of the mount-point and the source directory of a bind
mount are the same.

Version-Release number of selected component (if applicable):
2.4.20-8

How reproducible:
100%

Steps to Reproduce:
As root:

mkdir x y
mount --bind x y
stat --format='%d %n' x y
touch x/foo
ln x/foo y/bar

Actual results:
773 x
773 y
ln: creating hard link `y/bar' to `x/foo': Invalid cross-device link

Expected results:
Different device numbers.

Additional info:
This is connected with bug #86302 (cp --preserve=links vs mount --bind).

Comment 1 Arjan van de Ven 2003-04-11 13:26:29 UTC

it's the same device.... what's the issue ??????

Comment 2 Tim Waugh 2003-05-22 10:32:47 UTC

That ln is told it can't make a *cross*-device link, i.e. a link between two
different devices.

If the mount points are the same device, why can't I make a link between them?

Comment 3 Bugzilla owner 2004-09-30 15:40:42 UTC

Thanks for the bug report. However, Red Hat no longer maintains this version of
the product. Please upgrade to the latest version and open a new bug if the problem
persists.

The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, 
and if you believe this bug is interesting to them, please report the problem in
the bug tracker at: http://bugzilla.fedora.us/