Bug 22351 - fusermount doesn't unmount the encrypted folder after opening one of the files it contains with kwrite or kate
Summary: fusermount doesn't unmount the encrypted folder after opening one of the file...
Status: RESOLVED WORKSFORME
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 6
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Guillaume Rousse
QA Contact:
URL:
Whiteboard:
Keywords:
: 22349 (view as bug list)
Depends on:
Blocks:
 
Reported: 2018-01-08 18:19 CET by peter lawford
Modified: 2018-10-27 10:40 CEST (History)
1 user (show)

See Also:
Source RPM: encfs-1.8.1-6.mga6
CVE:
Status comment:


Attachments

Description peter lawford 2018-01-08 18:19:30 CET
Description of problem:this is a replica of bug #22349 written in better english

I have installed encfs file system on my mageia6, mysafeencrypt is the folder containing encrypted files, and mysafedecrypt is the mounting point of mysafeencrypt with fuse where it appears in its decrypted form
accessing to the decrypted files is possible with the command
[alain4@mag6 ~]$ encfs mysafeencrypt mysafedecrypt
suppose the latter one contains a file 'toto.txt', and I open it with kwrite or kate:
[alain4@mag6 ~]$ kwrite mysafedecrypt/toto.txt  (or the same replacing kwrite by kate), and I close it with the keys combination Ctrl+Q or Alt+F4
when attempting to unmount the encrypted folder with the command:

[alain4@mag6 ~]$ fusermount -u mysafedecrypt 
I get the return:
fusermount: failed to unmount mysafedecrypt: Device or resource busy

although toto.txt be already closed

that doesn't happen with mageia5





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


How reproducible: install encfe filesystem and make the trial


Steps to Reproduce:
1.
2.
3.
Comment 1 Marja Van Waes 2018-01-08 20:41:51 CET
(In reply to peter lawford from comment #0)
> Description of problem:this is a replica of bug #22349 written in better
> english
> 

Thanks.

It would have been fine if you had closed that report as duplicate of this one ;-)

CC: (none) => marja11
Assignee: bugsquad => guillomovitch

Comment 2 Marja Van Waes 2018-01-08 20:42:24 CET
*** Bug 22349 has been marked as a duplicate of this bug. ***
Comment 3 Guillaume Rousse 2018-02-13 20:52:19 CET
I can't reproduce here. Check with lsof which process is currently holding a file open in this directory:
$> lsof | grep mysafedecrypt
Comment 4 Guillaume Rousse 2018-10-27 10:40:45 CEST
No news from original reporter, closing.

Status: NEW => RESOLVED
Resolution: (none) => WORKSFORME


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