Here’s an example: take a mounted BTRFS filesystem called ‘VIDEO’. What is mildly irritating is that there is no visual indication of a non-empty state for trash on mounted BTRFS subvoumes. Now, this in itself is not a problem (is this something to do with subvolume ID level?). See, when deleting a file on a mounted BTRFS filesystem with multiple subvolumes, the file is moved to a hidden trash folder within each individual subvolume. Again, visual indication is given for the non-empty state and emptying is easy.īTRFS subvolumes behave a little differently. As expected, these files are typically moved to the hidden trash folder created in the root directory of the device. This process is the same when deleting files from mounted FAT32, EXT4 and NTFS flash drives or hard disk drives. I can then empty trash easily at the end of my session.
UBUNTU EMPTY TRASH FULL
The non-empty state of the trash bin is visually indicated (the Unity launcher full bin icon in 16.04 or the top bar icon of the Trash Gnome shell extension in 17.10). I tap the delete button which, on the local filesystem, typically moves the selected file to /.local/share/Trash.
I typically use nautilus to delete files. I also mount other BTRFS volumes regularly.
I’ve removed the support question since I’m less concerned with workarounds than I am with how the system ought to handle trash on mounted BTRFS subvolumes. I’ve edited and re-posted this since the last post was (ironically) trashed for reading like a support request.
0 kommentar(er)
