RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 917008 - mount --move doesn't work
Summary: mount --move doesn't work
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: util-linux
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Karel Zak
QA Contact: Jan Ščotka
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-03-01 12:39 UTC by Petr Sklenar
Modified: 2014-06-13 09:39 UTC (History)
1 user (show)

Fixed In Version: util-linux-2.23-0.5
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-13 09:39:42 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Petr Sklenar 2013-03-01 12:39:09 UTC
Description of problem:
mount --move doesn't work

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

util-linux-2.22.1-2.4.el7.x86_64

Linux pes-guest-92.lab.eng.brq.redhat.com 3.7.0-0.32.el7.x86_64 #1 SMP Fri Jan 18 11:50:31 EST 2013 x86_64 x86_64 x86_64 GNU/Linux


How reproducible:
always

Steps to Reproduce:
1. mount xyz:/mnt/qa on /mnt/qa
2. mkdir /tmp/1234
3. mount --move /mnt/qa /tmp/1234
  
Actual results:
# mount -M /mnt/qa /tmp/tmp.fIC9T6y9lw
mount: wrong fs type, bad option, bad superblock on /mnt/qa,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail or so


Expected results:
mount is moved

Additional info:

Comment 3 Karel Zak 2013-03-01 14:19:19 UTC
Are you really sure that the used parents (mountpoints) are private? The current default in RHEL7 (not sure about RHEL6) is "shared", see /proc/self/mountinfo for the shared flag.

Linux kernel does not allow to move between shared targets.

Fedora 18:

# mount --bind /mnt/test /mnt/test
# mount --make-private /mnt/test
# mkdir /mnt/test/{foo,bar}

# mount /dev/sdb /mnt/test/foo

# findmnt /dev/sdb
TARGET        SOURCE   FSTYPE OPTIONS
/mnt/test/foo /dev/sdb ext2   rw,relatime,stripe=32

# mount --move /mnt/test/foo /mnt/test/bar

# findmnt /dev/sdb
TARGET        SOURCE   FSTYPE OPTIONS
/mnt/test/bar /dev/sdb ext2   rw,relatime,stripe=32

Comment 6 Karel Zak 2013-03-25 14:33:24 UTC
Fixed by upstream commit fcc0413a12efde3f413064a622ea0a0595ede49f (util-linux >= 2.23-rc2).

# mount --move /a /b
mount: bad option. Note that moving a mount residing under a shared
       mount is unsupported.

Comment 8 Ludek Smid 2014-06-13 09:39:42 UTC
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.


Note You need to log in before you can comment on or make changes to this bug.