deleting files across file systems

[Jane Silber]

I have my trash on a separate partition from my desktop. If I try to delete a file from the desktop, I get an error message about moving files across file systems (which has some issues, related bug 33210)

I guess that there may be situations when the user should be warned about moving files across file systems (am not sure about that, but am guessing that there must be a reason for the warning/error). But in this case I have explicitly moved my trash to a different file system and don't really want to be stopped or warned about file systems every time I delete something from my desktop. Is it possible to distinguish between the situations that really do merit a warning (whatever they are) and the situation where I clearly do want to move across file systems (in this case by the fact that I moved my trash)?

[beefcurry (jonzwong)]

This is quite strange, I never used to have this problem when deleting files off my NAS in Edgy, however with the recent update to Feisty suddenly I am experiencing the same thing, which means it problely has something to do with device recognition on where the different file system is. I will have to try to see if this also happens on other removable media such as a CF or SD card in FAT/FAT32.

[Warbo (warbo)]

I get this message when trying to delete things from bound folders in my Home (I keep files in a separate partition, and bind the various folders to the Music, Documents, etc. folders in my home). It forces me to open a terminal just to delete a file (this is using Gutsy, Gnome VFS 1:2.19.91-0ubuntu1, nautilus 1:2.19.91-0ubuntu1)

[Wilbur Harvey (wilbur-harvey-spirentcom)]

Same problem in Feisty.
In the file manager, go to Edit-->Preferences-->Behaviou and set "Include a Delete command that bypasses Trash"
Then you can, at least, delete the file.
Still broken, but easier to deal with.
In my case, I have a raid, /md0, where directories like /opt, /usr, /var, and /home are bind mounted to /md0/opt etc. This is necessary since the system cannot boot directly off the raid.

[ne (office-sico)]

Running Feisty:
I have a similar setup as Warbo.
I use different partitions for my data and mount them in some folders in the home directory.

Everything works great for a long time (...since breezy I think) but some days ago I got this error!
But really special is, I get it on only one of my partitions, the other one runs without this problem.
Crazy, isn't it?

But it gets much more wired. Lets call the partition with the error par1 and the other mounted partition par2:
If I try to delete (or send to trash) an image on the broken partition (par1) I get the error: "Not on the same file system"
But if I open the image with gThumb and press the del-key (in gThumb) it is gone.
...but not deleted and not moved to trash, I found the image on the root of par2 (the working partition) after.
I didn' believe and tried it once more: same result.

As in others reports deleting per console (or shift-del) works normal.
Unfortunately this is a production machine, so I cannot do experiments with ..

[David Tangye (davidtangye)]

I have a similar problem. I always keep all my data on a separate partition, mounted to say /mnt/sdaN. I have a directory there for each user and the user can build whatever subdirectories from there he wants, each with links to his home, eg

ln -s /mnt/sda6/fred/workStuff /home/fred
ln -s /mnt/sda6/fred/playStuff /home/fred
ln -s /mnt/sda6/fred/yetMoreStuff /home/fred, etc

I should be able to use the nautilus Trash facility. I tried creating /mnt/sda6/.Trash-fred but that did not work, and I think it ought to.

[den (iznobe)]

Hi , i have the trash not working too , impossible to put item with externals partitions on ubuntu 22.04 :

[code]
iznobe@iznobe-PC:~$ cat /etc/os*release
PRETTY_NAME="Ubuntu 22.04.1 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04.1 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=jammy
iznobe@iznobe-PC:~$
iznobe@iznobe-PC:~$ ls -la /Vidéos/WD8PRO2/.Trash-1000
total 20
drwx------ 5 iznobe iznobe 4096 août 29 23:57 .
drwxrwxr-x 5 root root 4096 août 29 23:45 ..
drwx------ 2 iznobe iznobe 4096 sept. 6 22:01 expunged
drwx------ 2 iznobe iznobe 4096 sept. 6 22:01 files
drwx------ 2 iznobe iznobe 4096 sept. 6 22:01 info
iznobe@iznobe-PC:~$ namei -l /Vidéos/WD8PRO2/.Trash-1000
f: /Vidéos/WD8PRO2/.Trash-1000
drwxr-xr-x root root /
drwxr-xr-x root root Vidéos
drwxrwxr-x root root WD8PRO2
drwx------ iznobe iznobe .Trash-1000
iznobe@iznobe-PC:~$ cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/nvme0n1p7 during installation
UUID=8ab22881-60b3-47aa-a0bf-54c292afae81 / ext4 errors=remount-ro,noatime 0 1

# /boot/efi was on /dev/nvme0n1p3 during installation
UUID=C071-9050 /boot/efi vfat defaults 0 1

# swap was on /dev/sdc4 during installation
UUID=61218fe2-0bd1-4ada-9dd3-5ec996a02456 none swap sw 0 0

# partition de données separée comune aux OS linux
UUID=01c9b796-0869-4ff9-a2a1-6c0f56ed5257 /datas ext4 defaults 0 2
LABEL=WD8 /Vidéos/WD8 ext4 defaults,noatime 0 2
LABEL=WD8PRO2 /Vidéos/WD8PRO2 ext4 defaults,noatime 0 2
#/dev/disk/by-label/Sauvegardes /media/iznobe/Sauvegardes ext4 defaults,noatime 0 2

# limitation ecritures disques SSD ###
tmpfs /tmp tmpfs defaults,noatime 0 0

#ramdisk
tmpfs /mnt/ramdisk tmpfs rw,noatime,size=28G 0 0
##########################################
# FIN limitation ecritures disques SSD ###
iznobe@iznobe-PC:~$ [/code]

before upgrade to 22.04 it was working perfectly .