Steve Litt:
> On Mon, 12 May 2014 17:52:44 +0200
> Jochen Spieker <ml@well-adjusted.de> wrote:
>
>> this looks very weird to me. My wheezy system claims that a filesystem
>> is mounted, but the mount directory appears to be empty and umount
>> fails because the filesystems is not mounted, after all:
…
>> Do you have any ideas what's wrong?
>>
>> Regards,
>> J.
>
> No. :-(
>
> But I do have some thoughts.
>
> First, if you're not unmounting /srv/backup as root, try doing so.
Sure, every command shown was run as root.
> Next, before /dev/mapper/backup-decrypted can exist, something
> (cryptsetup luksOpen) must create it. Look for that, in /etc/fstab and
> elsewhere.
That already happened. The device is there, otherwise I wouldn't be able
to mount it a second time. But thanks for your input anyway.
Unfortunately, I cannot investigate this any further because I had to
reboot the system which cleared things up. But I would still like to
know how to fix such a situation.
I only noticed it because my backup script complained about the missing
path. Prior to running the backup, it checks whether the filesystem is
already mounted and mounts it if it is not mounted yet. That failed
because mount reported that the filesystem is mounted while the mount
point was empty.
J.
--
I use a Playstation to block out the existence of my partner.
[Agree] [Disagree]
<http://www.slowlydownward.com/NODATA/data_enter2.html>
Attachment:
signature.asc
Description: Digital signature