Bug#805845: marked as done (mount --move broken)
Your message dated Sat, 01 May 2021 23:39:02 -0700 (PDT)
with message-id <608e4906.1c69fb81.4edc.0023@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #805845,
regarding mount --move broken
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
805845: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805845
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: mount --move broken
- From: Phillip Susi <psusi@ubuntu.com>
- Date: Sun, 22 Nov 2015 20:23:02 -0500
- Message-id: <56526A76.6020708@ubuntu.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Package: util-linux
Version: 2.25.2-6
Control: affects -1 +udisks2 +gparted
gparted runs udisks2-inhibit, which runs mount --move /a /b, and this
fails with "mount: bad option...".
Manually running mount --move /a /b ( where /a is a tmpfs mount and /b
is a directory ) likewise fails. Running mount --bind /a /b, then
umount /a works however.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAEBCgAGBQJWUmptAAoJEBB5UWFcu6UWhmEH/1dCLGXsWFElNLOvRLDF3q4L
M9DL6TzZDX5PPN2GdKswuGLEhgbAaMufz2wLxo8/UpBKGpA9WrbfsciCVWTyGOFl
Y2ze/TPUa3ZfyWC3y1QCDSAqT1EIPKGHPsTjBfUaMXoM0qo0J5j95EuCT/b/K9hi
bCNGsNTjQej65F7ctwmkUGD8ZI/F3qO7r8tcwTIISmJ1M3uMLVaLl6Oz4+jRC/vN
1uU8IWoUoAUkgPWeFzawZQ1otZixhsccZrdRElpR9XCrRntR68/ufHoemOE0fQ8A
3Uv092g2zMXfKjxW3X9OEjLvyWQBKWG5HbKJpyIvF2iHdUmg5nx9hUUANhtMqNc=
=gSG/
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
Hi
This bug was filed for a very old kernel or the bug is old itself
without resolution.
If you can reproduce it with
- the current version in unstable/testing
- the latest kernel from backports
please reopen the bug, see https://www.debian.org/Bugs/server-control
for details.
Regards,
Salvatore
--- End Message ---
Reply to: