Copying 100G+ folders from my external drive freezes LMDE4.

Quick to answer questions about finding your way around LMDE as a new user.
Forum rules
There are no such things as "stupid" questions. However if you think your question is a bit stupid, then this is the right place for you to post it. Stick to easy to-the-point questions that you feel people can answer fast. For long and complicated questions use the other forums within the support section.
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Locked
Elysium

Copying 100G+ folders from my external drive freezes LMDE4.

Post by Elysium »

Hey guys,

I have just installed LMD4 cinnamon and I have been trying to copy files to my NFTS partition from my external HD. I am copying a massive folder (100G+) and it starts of at 50Mb/s and then slows down tremendously. It says it would finish in 4 mins (neat the end) yet it takes like 30 mins or so. The whole OS becomes super sluggish and slow. Is there a way to copy files from an external HD to an NTFS partition without the inconvenience of nemo?

Is there a fix to make copying smooth? I understand that an older external drive wont be working smoothly with a newer laptop, but this (starting at 50Mb and going down to 10Mb) is worrying.

Thank you.

Code: Select all

 Kernel: 4.19.0-8-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 
  Desktop: Cinnamon 4.4.8 Distro: LMDE 4 Debbie base: Debian 10.2 buster 
Machine:
  Type: Laptop System: ASUSTeK product: TUF Gaming FX505GT_FX505GT v: 1.0 
  serial: <filter> 
  Mobo: ASUSTeK model: FX505GT v: 1.0 serial: <filter> 
  UEFI: American Megatrends v: FX505GT.304 date: 11/11/2019 
Battery:
  ID-1: BAT0 charge: 44.1 Wh condition: 44.6/48.1 Wh (93%) 
  model: Simplo SDI ICR18650 status: Charging 
CPU:
  Topology: 6-Core model: Intel Core i7-9750H bits: 64 type: MT MCP 
  arch: Kaby Lake rev: D L2 cache: 12.0 MiB 
  flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 62208 
  Speed: 900 MHz min/max: 800/4500 MHz Core speeds (MHz): 1: 900 2: 900 
  3: 900 4: 900 5: 900 6: 901 7: 900 8: 900 9: 900 10: 901 11: 900 12: 900 
Graphics:
  Device-1: Intel UHD Graphics 630 vendor: ASUSTeK driver: i915 v: kernel 
  bus ID: 00:02.0 
  Device-2: NVIDIA vendor: ASUSTeK driver: nvidia v: 440.59 bus ID: 01:00.0 
  Display: x11 server: X.Org 1.20.4 driver: modesetting 
  unloaded: fbdev,nouveau,nvidia,vesa resolution: 1920x1080~60Hz 
  OpenGL: renderer: Mesa DRI Intel UHD Graphics 630 (Coffeelake 3x8 GT2) 
  v: 4.5 Mesa 18.3.6 direct render: Yes 
Audio:
  Device-1: Intel Cannon Lake PCH cAVS vendor: ASUSTeK driver: snd_hda_intel 
  v: kernel bus ID: 00:1f.3 
  Device-2: NVIDIA vendor: ASUSTeK driver: snd_hda_intel v: kernel 
  bus ID: 01:00.1 
  Sound Server: ALSA v: k4.19.0-8-amd64 
Network:
  Device-1: Intel Wireless-AC 9560 [Jefferson Peak] driver: iwlwifi 
  v: kernel port: 5000 bus ID: 00:14.3 
  IF: wlo1 state: up mac: <filter> 
  Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
  vendor: ASUSTeK driver: r8169 v: kernel port: 3000 bus ID: 03:00.0 
  IF: enp3s0 state: down mac: <filter> 
Drives:
  Local Storage: total: 1.14 TiB used: 39.06 GiB (3.3%) 
  ID-1: /dev/nvme0n1 model: HFM256GDJTNG-8310A size: 238.47 GiB 
  ID-2: /dev/sda vendor: Toshiba model: MQ04ABF100 size: 931.51 GiB 
Partition:
  ID-1: / size: 48.97 GiB used: 9.03 GiB (18.4%) fs: ext4 dev: /dev/sda1 
  ID-2: swap-1 size: 18.00 GiB used: 37.0 MiB (0.2%) fs: swap dev: /dev/sda2 
Sensors:
  System Temperatures: cpu: 39.0 C mobo: 27.8 C 
  Fan Speeds (RPM): N/A 
Info:
  Processes: 291 Uptime: 17m Memory: 15.52 GiB used: 2.13 GiB (13.7%) 
  Init: systemd runlevel: 5 Compilers: gcc: 8.3.0 Shell: bash v: 5.0.3 
  inxi: 3.0.32 
UPDATE:

I have tried xef so far. Pretty neat and fast, but the exact same thing happened when it got half-way through copying the folder. It became super slow and I could hardly move the mouse cursor (let alone do things like browsing). I aborted the task and had to manually restart the OS. When I booted up and system went crazy:

Code: Select all

$ systemd-analyze
Startup finished in 7.880s (firmware) + 2.427s (loader) + 12.192s (kernel) + 2min 8.530s (userspace) = 2min 31.030s 
graphical.target reached after 2min 8.519s in userspace

Code: Select all

~$ systemd-analyze blame
    1min 21.232s udisks2.service
         49.539s debian-system-adjustments.service
         37.523s accounts-daemon.service
         34.581s NetworkManager.service
         30.492s NetworkManager-wait-online.service
         29.013s ModemManager.service
         28.660s acpi-support.service
         25.926s mnt-59A8170370134255.mount
         18.595s nvidia-persistenced.service
         18.595s sysfsutils.service
         18.583s systemd-logind.service
         16.033s avahi-daemon.service
         15.895s lm-sensors.service
         15.894s rsyslog.service
         15.892s wpa_supplicant.service
         15.891s bluetooth.service
         15.886s thermald.service
         15.301s lightdm.service
         13.684s user@1000.service
         12.847s polkit.service
         12.540s plymouth-quit-wait.service
          9.318s colord.service
          5.784s systemd-udev-settle.service
lines 1-23...skipping...
    1min 21.232s udisks2.service
         49.539s debian-system-adjustments.service
         37.523s accounts-daemon.service
         34.581s NetworkManager.service
         30.492s NetworkManager-wait-online.service
         29.013s ModemManager.service
         28.660s acpi-support.service
         25.926s mnt-59A8170370134255.mount
         18.595s nvidia-persistenced.service
         18.595s sysfsutils.service
         18.583s systemd-logind.service
         16.033s avahi-daemon.service
         15.895s lm-sensors.service
         15.894s rsyslog.service
         15.892s wpa_supplicant.service
         15.891s bluetooth.service
         15.886s thermald.service
         15.301s lightdm.service
         13.684s user@1000.service
         12.847s polkit.service
         12.540s plymouth-quit-wait.service
          9.318s colord.service
          5.784s systemd-udev-settle.service
          4.941s dev-sda1.device
          3.881s upower.service
          3.653s brltty.service
          2.698s systemd-tmpfiles-setup.service
          2.465s apparmor.service
          2.171s dns-clean.service
          1.064s systemd-modules-load.service
           922ms lvm2-monitor.service
           765ms systemd-remount-fs.service
           720ms systemd-backlight@backlight:intel_backlight.service
           587ms hddtemp.service
           512ms systemd-udevd.service
           456ms systemd-udev-trigger.service
           435ms networking.service
           424ms keyboard-setup.service
           395ms ufw.service
           389ms kmod-static-nodes.service
           388ms blk-availability.service
           387ms dev-mqueue.mount
           385ms dev-hugepages.mount
Running journalctl -b gives 47 lines with errors in them.

Then I restarted the OS again and now it is back to normal. How on earth can copying files make this to an OS is beyond me.

I have been enjoying LM for years, but lately I keep getting these system freezes and it feels like its the file manager that makes it happen, but I cant pinpoint what exactly does it. Any ideas how to fix this issue?
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 6 times in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
jaundice

Re: Does copying big (100G+) folder cause system lag?

Post by jaundice »

Nemo can sometime lag when it come to copying or moving files .
use ultracopier or gcp instead .

Code: Select all

sudo apt-get install ultracopier

Code: Select all

sudo apt-get install gcp

Code: Select all

sudo apt-get install python-progressbar
ultracopier have a GUI and gcp can be used that way :
gcp [OPTIONS] FILE DEST
gcp [OPTIONS] FILE1 [FILE2...] DEST-DIR

hope that fix the isuue , good luck
Locked

Return to “Beginner Questions”