[systemd-devel] fstab Mounts Not Getting Waken Up

Reindl Harald h.reindl at thelounge.net
Fri Jul 12 09:22:00 PDT 2013

Am 12.07.2013 18:06, schrieb Michael Biebl:
> 2013/7/12  <CACook at quantum-sci.com>:
>> Reindl Harald:
>>>>>> Your use of sshfs# as a FUSE type is wrong -- you must use fuse.sshfs
>>>>>> as
>>>>>> the fstype instead.
>>> this simply wrong, this line below in /etc/fstab works day
>>> and night from FC9 to Fedora 18 as well as curlftpsfs
>>> mounts in /etc/fstab are starting with curlftpfs#
>>> and *both* have "fuse" and nothing else as fstype
>>> sshfs#reindl at webserver:/ /mnt/webserver fuse
>>> noauto,user,rw,noexec,nosuid,nodev,uid=harry
>>> the server is a simple openssh on F17 with native sftp-chroot
>> Reindl, thank goodness you're listening.  Have you by chance, tried this
>> with auto, to see whether it automounts on wake from suspend?
> systemd doesn't unmount the fs on suspend, why should it mount it on resume?
> Maybe you are mixing up what "auto" means

maybe the mount freezes to unuseable after wakeup and this
is what he means which would have more to do with
KeepALive (network-layer and ssh/sshd) or in case of
changed the location a re-mount would be needed

but both cases has hardly to do anything with systemd and
could be fixed in th efuse-modules by catch wakeup events
and remount all fuse mountpoints

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 263 bytes
Desc: OpenPGP digital signature
URL: <http://lists.freedesktop.org/archives/systemd-devel/attachments/20130712/40c3db30/attachment.pgp>

More information about the systemd-devel mailing list