https://bugs.kde.org/show_bug.cgi?id=395023
Bug ID: 395023
Summary: $topdir/.Trash not created or used on btrfs
sub-volumes
Product: frameworks-kio
Version: unspecified
Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: Trash
Assignee: fa...@kde.org
Reporter: commander.sirow+...@googlemail.com
CC: kdelibs-b...@kde.org
Target Milestone: ---
It seems like kio does neither create nor detect existing $topdir/.Trash(-$uid)
directories as mandated by the freedesktop.org trash specification when it
comes to btrfs subvolumes.
This is problematic because it means files will to be moved across subvolume
boundaries, which means the files will actually be copied to
~/.local/share/Trash (and deleted in its original location afterwards).
Eg. with the following btrfs layout:
/dev/sda1
- @root (btrfs subvolume mounted to /)
- @home (btrfs subvolume mounted to /home)
- @workspace (btrfs subvolume mounted to /home/Workspace)
And file-system layout
/bin
/boot
[...]
/home
/home/Documents
/home/Downloads
[...]
/home/Workspace
/home/Workspace/.Trash (Permissions: drwxrwxrwt)
/home/.local/share/Trash
[...]
/.Trash (Permission: drwx-----T)
[...]
When deleting a file under workspace it will actually be moved (across the
subvolume boundary) into /home/.local/share/Trash and not
/home/Workspace/.Trash
My guess is that kio does not "detect" (or treat) btrfs subvolumes as
individual partions, thus there is no check happening.
(Compare LVM issue described here: https://bugs.kde.org/show_bug.cgi?id=178479)
--
You are receiving this mail because:
You are watching all bug changes.
