.Trash-1000 folder in pCloud Drive folder: [Solved]

[Kester]

Hi,
I have emailed pCloud Customer Services about this issue but expect they will take a little while to reply so, in the hope that there will MX-Linux forum members familiar with the issue, I have made this post.

Recently I removed an unwanted folder from my pCloud account. I did this online and emptied the online account trash bin. Unfortunately, in my home/username/pCloudDrive folder there is a .Trash-1000 folder containing a folder that holds deleted files and these cannot be removed. Initially I can delete the individual files but they reappear. Although these files do not take up much space, when I backup my home directory, these deleted files generate error messages in GRsync - this does not stop the backup working but it is a source of irritation. Is there a way I can successfully remove .Trash-1000 or at least the nuisance deleted files stored within it.

I'd be grateful for any advice. Thanks.

[j2mcgreg]

QSI please.

[CharlesV]

Hi,
I have emailed pCloud Customer Services about this issue but expect they will take a little while to reply so, in the hope that there will MX-Linux forum members familiar with the issue, I have made this post.

Recently I removed an unwanted folder from my pCloud account. I did this online and emptied the online account trash bin. Unfortunately, in my home/username/pCloudDrive folder there is a .Trash-1000 folder containing a folder that holds deleted files and these cannot be removed. Initially I can delete the individual files but they reappear. Although these files do not take up much space, when I backup my home directory, these deleted files generate error messages in GRsync - this does not stop the backup working but it is a source of irritation. Is there a way I can successfully remove .Trash-1000 or at least the nuisance deleted files stored within it.

I'd be grateful for any advice. Thanks.

I use pCloud drive and that file is their folder/file(s). When you delete a file from pCloud it remains in their trash folder system until it clears or your delete it from their cloud system. You can remove it, but I believe it must be done from your cloud login.

[Kester]

Hi,
@j2mcgreg Sorry about forgetting the QSI: here it is -

Code: Select all

[[CODE]Snapshot created on: 20240624_1914
System:
  Kernel: 6.1.0-34-amd64 [6.1.135-1] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-34-amd64 root=UUID=<filter> ro quiet splash
  Desktop: Xfce v: 4.20.0 tk: Gtk v: 3.24.38 info: xfce4-panel wm: xfwm v: 4.20.0 vt: 7
    dm: LightDM v: 1.32.0 Distro: MX-23.6_x64 Libretto July 31  2023 base: Debian GNU/Linux 12
    (bookworm)
Machine:
  Type: Desktop Mobo: Gigabyte model: H310M H v: x.x serial: <superuser required>
    UEFI: American Megatrends v: F11 GK date: 11/21/2018
CPU:
  Info: model: Intel Core i3-8100 bits: 64 type: MCP arch: Coffee Lake gen: core 8 level: v3
    note: check built: 2018 process: Intel 14nm family: 6 model-id: 0x9E (158) stepping: 0xB (11)
    microcode: 0xF6
  Topology: cpus: 1x cores: 4 smt: <unsupported> cache: L1: 256 KiB desc: d-4x32 KiB; i-4x32 KiB
    L2: 1024 KiB desc: 4x256 KiB L3: 6 MiB desc: 1x6 MiB
  Speed (MHz): avg: 800 min/max: 800/3600 scaling: driver: intel_pstate governor: powersave
    cores: 1: 800 2: 800 3: 800 4: 800 bogomips: 28800
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: gather_data_sampling mitigation: Microcode
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT disabled
  Type: mds mitigation: Clear CPU buffers; SMT disabled
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data mitigation: Clear CPU buffers; SMT disabled
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed mitigation: IBRS
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: IBRS; IBPB: conditional; STIBP: disabled; RSB filling;
    PBRSB-eIBRS: Not affected; BHI: Not affected
  Type: srbds mitigation: Microcode
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Intel CoffeeLake-S GT2 [UHD Graphics 630] vendor: Gigabyte driver: i915 v: kernel
    arch: Gen-9.5 process: Intel 14nm built: 2016-20 ports: active: HDMI-A-2 empty: DP-1,HDMI-A-1
    bus-ID: 00:02.0 chip-ID: 8086:3e91 class-ID: 0300
  Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.20.0 driver: X:
    loaded: modesetting unloaded: fbdev,vesa dri: iris gpu: i915 display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 509x286mm (20.04x11.26") s-diag: 584mm (22.99")
  Monitor-1: HDMI-A-2 mapped: HDMI-2 model: AOC 2269WM serial: <filter> built: 2016
    res: 1920x1080 hz: 60 dpi: 102 gamma: 1.2 size: 477x268mm (18.78x10.55") diag: 547mm (21.5")
    ratio: 16:9 modes: max: 1920x1080 min: 720x400
  API: OpenGL v: 4.6 Mesa 22.3.6 renderer: Mesa Intel UHD Graphics 630 (CFL GT2)
    direct-render: Yes
Audio:
  Device-1: Intel Cannon Lake PCH cAVS vendor: Gigabyte driver: snd_hda_intel v: kernel
    alternate: snd_soc_skl,snd_sof_pci_intel_cnl bus-ID: 00:1f.3 chip-ID: 8086:a348 class-ID: 0403
  API: ALSA v: k6.1.0-34-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 1.0.0 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Gigabyte driver: r8169
    v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: 3000 bus-ID: 01:00.0 chip-ID: 10ec:8168
    class-ID: 0200
  IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter>
Drives:
  Local Storage: total: 4.66 TiB used: 703.1 GiB (14.7%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Toshiba model: HDWD110 size: 931.51 GiB block-size:
    physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 7200 serial: <filter> rev: A8J0
    scheme: MBR
  ID-2: /dev/sdb maj-min: 8:16 vendor: Gigabyte model: GP-GSTFS31120GNTD size: 111.79 GiB
    block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 61.2
    scheme: GPT
  ID-3: /dev/sdc maj-min: 8:32 type: USB vendor: Western Digital model: WD40EDAZ-11SLVB0
    size: 3.64 TiB block-size: physical: 4096 B logical: 512 B type: HDD rpm: 5400 serial: <filter>
    rev: 1031 scheme: GPT
Partition:
  ID-1: / raw-size: 105.86 GiB size: 103.64 GiB (97.90%) used: 46.17 GiB (44.5%) fs: ext4
    dev: /dev/sdb2 maj-min: 8:18
  ID-2: /boot/efi raw-size: 304 MiB size: 299.3 MiB (98.46%) used: 411 KiB (0.1%) fs: vfat
    dev: /dev/sdb1 maj-min: 8:17
Swap:
  Kernel: swappiness: 10 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: file size: 4 GiB used: 0 KiB (0.0%) priority: -2 file: /swapfile
Sensors:
  System Temperatures: cpu: 38.0 C pch: 43.0 C mobo: N/A
  Fan Speeds (RPM): N/A
Repos:
  Packages: 2676 pm: dpkg pkgs: 2664 libs: 1448 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
    pkgs: 0 pm: flatpak pkgs: 12
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/brave-browser-release.list
    1: deb [signed-by=/usr/share/keyrings/brave-browser-archive-keyring.gpg] https://brave-browser-apt-release.s3.brave.com/ stable main
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
    1: deb http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/debian.list
    1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
    2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/insync.list
    1: deb [signed-by=/etc/apt/trusted.gpg.d/insynchq.gpg] http://apt.insync.io/debian bookworm non-free contrib
  Active apt repos in: /etc/apt/sources.list.d/megasync.list
    1: deb [signed-by=/usr/share/keyrings/meganz-archive-keyring.gpg] https://mega.nz/linux/repo/Debian_12/ ./
  Active apt repos in: /etc/apt/sources.list.d/microsoft-edge.list
    1: deb [arch=amd64] https://packages.microsoft.com/repos/edge/ stable main
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb http://mxlinux.mirrors.uk2.net/packages/mx/repo/ bookworm main non-free
Info:
  Processes: 244 Uptime: 3h 53m wakeups: 1 Memory: 7.62 GiB used: 2.05 GiB (26.9%) Init: SysVinit
  v: 3.06 runlevel: 5 default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
  Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI

/code]

@CharlesV: The files concerned are the residue from an otherwise successful deletion. I believe they have been corrupted at some stage during the process of backing them up to pCloud or possibly during the process of deleting them from the online account. I'll investigate this further - thanks for your interest and observations.

[CharlesV]

@Kester It sounds like something is amiss, as I have no problems deleting old trash files on mine.

[DukeComposed]

I believe they have been corrupted at some stage during the process of backing them up to pCloud or possibly during the process of deleting them from the online account.

It's common on Linux systems to move files to a directory called .Trash-1000 instead of deleting them. This is how Linux provides a Windows/Mac-like Trash/Recycle Bin feature and has nothing to do with file corruption. If you don't want to restore the files it's safe to delete this directory, but you'll have to remove it from both sides of your backup before you do any further synchronization between them or else you'll just end up ping-ponging the directory back and forth between endpoints.

[Kester]

@DukeComposed: Thanks for your comments. Unfortunately I cannot delete the .Trash-1000 folder in my pCloudDrive directory. It does not appear in my online account with pCloud either. File corruption does appear to be linked with the issue because if I try to create a backup in another drive using GRsync, the program runs, appears to be copying files and then stops and displays the following warning:

Code: Select all

rsync: [sender] read errors mapping "/home/chris/pCloudDrive/.Trash-1000/expunged/3760246128/ashampoo_licenses.doc": Input/output error (5)
WARNING: chris/pCloudDrive/.Trash-1000/expunged/3760246128/ashampoo_licenses.doc failed verification -- update discarded (will try again).
rsync: [sender] read errors mapping "/home/chris/pCloudDrive/.Trash-1000/expunged/3760246128/ashampoo_licenses.doc": Input/output error (5)
ERROR: chris/pCloudDrive/.Trash-1000/expunged/3760246128/ashampoo_licenses.doc failed verification -- update discarded.
rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1338) [sender=3.2.7]
Rsync process exit status: 23

There were other files that were included in the GRsync warnings but I have been able to eliminate them being included as I found copies of the originals that were not corrupted and copy them into the .Trash-1000 folder where they replaced the faulty files. Although they cannot, as yet, be permanently deleted they no longer are included in the GRsync warning. However the ashampoo_licences.doc file remains a problem.

I don't know if this information helps or if there is a way I can force the removal of the file. Using root privileges does not help.

[MXRobo]

Probably useless - and admittedly 'cheap' on my part , but a Google search (yes I broke down and used Google) of,

Code: Select all

ERROR: user/pCloudDrive/.Trash-1000/expunged/ ashampoo_licenses.doc failed verification -- update discarded.

revealed the following - form it's AI.

The error message "ERROR: user/pCloudDrive/.Trash-1000/expunged/ ashampoo_licenses.doc failed verification -- update discarded" indicates that pCloud Drive, a cloud storage service, encountered a problem while attempting to update or verify a file named "ashampoo_licenses.doc" located within its trash folder.
Here's a breakdown of what this error means and potential causes:
1. Location of the File:
user/pCloudDrive: This signifies that the file is located within the user's pCloud Drive folder.
.Trash-1000: This is a hidden folder, likely the pCloud Drive trash or recycle bin.
expunged: This subfolder suggests that the file was previously deleted and is being purged or permanently removed from the trash.
2. File in Question:
ashampoo_licenses.doc: This is a document file, likely related to Ashampoo software licenses.
3. Error Message:
failed verification: This indicates that pCloud Drive could not verify the integrity or authenticity of the file, potentially due to corruption, modification, or an issue with the file's metadata.
update discarded: As a result of the failed verification, pCloud Drive discarded the attempted update or change to the file.
Potential Causes:
File Corruption: The "ashampoo_licenses.doc" file might have become corrupted during transfer, storage, or while in the trash.
File Modification: The file may have been modified after it was initially placed in the trash or after pCloud Drive last synchronized it, leading to a mismatch in verification.
Sync Issues: Problems with pCloud Drive's syncing process might lead to inconsistencies and cause verification to fail.
Temporary Server Issue: A temporary problem with pCloud Drive's servers could potentially cause this type of verification failure.
Troubleshooting Steps:
Check pCloud Drive Status: Confirm that pCloud Drive is running and connected to the internet.
Update pCloud Drive: Ensure you are using the latest version of pCloud Drive, as updates often include bug fixes and improvements.
Check Ashampoo Software: Verify that your Ashampoo software is working correctly and that there are no issues with its license verification process.
Restart pCloud Drive and Computer: A simple restart of both the pCloud Drive application and your computer can often resolve temporary glitches.
Clear pCloud Drive Cache (if necessary): If the issue persists, you might consider clearing pCloud Drive's cache to remove any potentially corrupted temporary files.
Contact pCloud Support: If you continue to encounter the error, contacting pCloud support is recommended to seek further assistance.
Consider pCloud Extension Error Codes: You can check the pCloud Extension Error Codes for more detailed information on error codes and troubleshooting steps, according to ServMask.
Note: It's important to understand that this error does not necessarily mean that your files are lost or permanently damaged. The error primarily indicates that a specific update to a file in the trash could not be verified and was discarded.

I did not search a line of your message exactly, and also omitted chris.

FWIW?

Cheers!

[Kester]

@MXRobo: Thanks for your interest and the trouble you took on my behalf.
I've been experimenting a bit and the following appears to have sorted the problem. I dragged the troublesome .Trash-1000 folder from my home directory directly into my pCloud account home screen and uploaded it. I then deleted all the folders in the 'expunged' directory. No error messages were generated by pCloud. Next I cleared the pCloud 'trash' folder - again no error messages generated but only warning about the result could not be undone if I went ahead. I went ahead and later found the issue no longer appeared in my pCloudDrive's .Trash-1000 folder in my system's 'home' folder.

Cheers, and thanks all. I'll mark this solved.