[kiofuse] [Bug 482902] Data loss on remote mount when using rmdir in terminal

Evan 'JabberWokky' Edwards bugzilla_noreply at kde.org
Sat Mar 9 01:08:35 GMT 2024


https://bugs.kde.org/show_bug.cgi?id=482902

--- Comment #4 from Evan 'JabberWokky' Edwards <evan+kdebugs at cheshirehall.net> ---
(In reply to Fabian Vogt from comment #1)
> I'm assuming you're using the sftp:// url in dolphin while the terminal sees
> the kio-fuse mount, e.g. /run/user/1000/kio-fuse....
> Can you post a screenshot of such a situation for clarity?

This is accurate.  I will post a screenshot shortly.


> > 1. If a remote directory is not explored, it appears empty within the filesystem (displaying 0 items in the panel)
> 
> Do you mean the terminal panel or the dolphin panel? It's intentional that
> directories are not populated unless necessary to avoid potentially slow
> network requests.

I mean the dolphin view of the filesystem -- the Details View Mode.  I realize
now that I am assuming without evidence that it displaying "0 items" under size
is related to the behavior in the terminal panel.  I have no direct reason to
know that the two are related, and I completely understand why directory
contents are not scanned until opened on remote filesystems.


> rmdir is supposed to fail on nonempty directories, so the question is which
> layer is wrong here. kio-fuse translates the rmdir call on directories to
> KIO::del, unless it already knows that it has items. KIO::del appears to do
> a recursive deletion by default, which is wrong in this context. For
> directories, KIO::rmdir is probably more appropriate.

This makes sense to me.  I do not know fuse (other than as a user), and I may
have erroneously assumed the error was related to presenting a empty directory
within the mount.

Thank you all for a prompt response; I've been using KDE since prior to the
release of KDE 1.0, and I have always appreciated the work everybody has done
and will do.  I will take screenshots and any other requested documentation in
the next couple hours when I am able to do so.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


More information about the kfm-devel mailing list