Your message dated Mon, 18 Aug 2014 17:33:37 +0000
with message-id <e1xjqol-0006fk...@franck.debian.org>
and subject line Bug#758090: fixed in ltspfs 1.4-1
has caused the Debian Bug report #758090,
regarding ltspfs: lbmount use of "mount --move" incompatible with systemd
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 ow...@bugs.debian.org
immediately.)
--
758090: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758090
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ltspfs
Version: 1.3-1
Justification: unusable with default init system
Severity: serious
X-Debbugs-Cc: alk...@gmail.com
ltspfs doesn't appear to work with systemd, as it relies on mounting the
fuse based ltspfs filesystem in one location, and then using "mount
--move" to relocate it to another section. But using "mount --move" with
a system running systemd results in this:
sudo mount --move test test2
mount: wrong fs type, bad option, bad superblock on /media/test,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
Apparently this has something to do with "MS_REC|MS_SHARED" and can be
disabled on a per-filesystem basis with "mount --make-private /", for
example. This may change behavior for other systems (such as containers)
which assume it is not marked private...
A quick workaround is to use "mount --bind" instead of "mount --move",
but this has the undesired side-effect of leaving two mounts in place,
one in /tmp/.USERNAME-ltspfs/MOUNT and one in /media/USERNAME/MOUNT.
Though some brief experiments show that unmounting the /tmp mount left
the /media mount in place when i tried it... that might make it a viable
workaround.
Honestly, I'd rather figure out a way to safely mount the ltspfs mount
directly without "mount --move". We could have a setuid wrapper that instead
creates the mountpoint directly as /media/USERNAME/MOUNT and ensures it
actually mounts, and some way of ensuring that it unmounts and removes
the /media/USERNAME/MOUNT directory when done... possibly with a
mount.helper and/or umount.helper.
live well,
vagrant
pgpLa2LoxYVkd.pgp
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: ltspfs
Source-Version: 1.4-1
We believe that the bug you reported is fixed in the latest version of
ltspfs, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 758...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Vagrant Cascadian <vagr...@debian.org> (supplier of updated ltspfs package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Mon, 18 Aug 2014 09:48:57 -0700
Source: ltspfs
Binary: ltspfs ltspfsd ltspfsd-core
Architecture: all source
Version: 1.4-1
Distribution: unstable
Urgency: medium
Maintainer: Debian LTSP Maintainers <pkg-ltsp-de...@lists.alioth.debian.org>
Changed-By: Vagrant Cascadian <vagr...@debian.org>
Closes: 758090 758093
Description:
ltspfsd-core - Fuse based remote filesystem daemon for LTSP thin clients
ltspfsd - Fuse based remote filesystem hooks for LTSP thin clients
ltspfs - Fuse based remote filesystem for LTSP thin clients
Changes:
ltspfs (1.4-1) unstable; urgency=medium
.
* New upstream version:
- Fix filesystem size calculations. Thanks to datube for the initial
patch! (LP: #1021579).
- Mount ltspfs filesystem directly to /media/username/mountpoint
(Closes: #758090).
- Add support for starting ltspfsd from systemd service file when
systemd is running (Closes: #758093).
- ltspfsd: Don't add duplicate entries to ltspfs_fstab.
Checksums-Sha1:
c3c6eb96b9d03de7b829aee29f7b75cf34f16750 2061 ltspfs_1.4-1.dsc
962839af8fefaeff068d3274b1692da46008b9e0 44329 ltspfs_1.4.orig.tar.gz
bdcf927196e9a270d9a286d1d88631b49eb1554b 8460 ltspfs_1.4-1.debian.tar.xz
7e96bfb46eed1274aa296fc0fa60606397a3e3ff 17158 ltspfsd_1.4-1_all.deb
Checksums-Sha256:
e76020eaaf97561a48cd213f36cb081ae33c61783891d37695d35c03f6298185 2061
ltspfs_1.4-1.dsc
601f6a355c3494c6cf2eef3f02babd6043a1aea77e1d6170c7a9e6d0ad328a23 44329
ltspfs_1.4.orig.tar.gz
0911488c701727a3aa1c4692ee6abc700475880dc55719f18e53b237ad92db5c 8460
ltspfs_1.4-1.debian.tar.xz
9ada0236d68b6620dc140b7386b5e2e912b44263525c08241346a816d12d321f 17158
ltspfsd_1.4-1_all.deb
Files:
c0005daf491bcafdd26fa1dd0ab9c9ae 2061 net optional ltspfs_1.4-1.dsc
c25775a308059f228697176119551325 44329 net optional ltspfs_1.4.orig.tar.gz
cb7f723a763efcd14216c56a04f6082e 8460 net optional ltspfs_1.4-1.debian.tar.xz
ed5a0fd92542601e3031e6cb58392e0b 17158 net optional ltspfsd_1.4-1_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQIcBAEBCgAGBQJT8jbIAAoJELeLgtSBS5G2nK0P/2MQdLUhdyyxMeWY18NaB7xa
+EYrUcTccXn+bi0zNZMtQYJZbK0C0DNoq81I2MFGMox3m7UYJlcV5P9oStDs80NF
Bda0sabutzlrpUEmL+7PEQK0TfQNIwU9VWLqLtMnATBO44Nl909YpHts+rL+YThG
8uh99448B1WOUckl/2s6s7nFNx9BGF1frYdVw3R+gaRQNVUXLrrcc/Nd+vt2oIoy
rHwxyGuTcQI0m+TRq8n0egk2yrzWkFOmgLe5wBVyzWE82+zExAzWAMsT1Rq79Lz8
SefTWKbvnVlrW4cny3iCNUBbs+9TvctqpjJcHMynpvnJUpz4NOdwJjSd1BsivzQg
Hr7E6MZtE6cFZE8RKhnR3m4wXh2kBj2/09OJuhsBe9qcbbURqOI6A1FxoGyRVFE9
UThWpt4Xr1OFyxU6FQmcrj3/Y/Z/ruLpKFMuIknpmU3gtQtae/b3fvnLiCmFNfYb
F5QlQjJDgk+2O9LbMbamfSQV1HTH0eMVN/7FOk36ei1Gb6lyp286ovQm3q6IXBy7
ZPFfxdA+OlHJTA5a2IQbA26XVd0MPKWaeVfXu4cP+HW7kMTKqTBtlVmMqbyf8r9C
AeRSAvvbo7pCGmVAQX+c5dETAy5dmGitYOqSVgTXfm6mtAvyW6teLecq54X/FeFt
jMOWMOQk7rbFMKjh7W+h
=eL1e
-----END PGP SIGNATURE-----
--- End Message ---
