Problem with Snapshot Program  [Solved]

Message
Author
User avatar
Falcon
Posts: 478
Joined: Mon Apr 22, 2019 9:34 pm

Problem with Snapshot Program

#1 Post by Falcon »

I try to do a snapshot of my computer every Sunday and since today is Sunday, I started the MX Snapshot program. When it was partially finished, an Error window opened and stated that Snapshot needed a little over 41 GB of disk space to do the snapshot, and the Snapshot directory had only a little over 39 GB available. I went into the Snapshot directory and deleted an older Snapshot file which was about 5 GB. This should have given the program enough space to store the file. I started the Snapshot program again, and got the same message with the same required storage. Finally I decided to use a 256 GB USB drive to contain the Snapshot file. I started the MX Snapshot program again and got a similar error, but this time with no data on available versus required storage space.

After the first error occurred, I started Gparted and verified that there was only 39 GB of space available. After deleting the old Snapshot file, Gparted showed that there was about 45 GB available. In spite of this, it failed the second time with incorrect information on the available space. Does anyone have any suggestions as to what I can try to fix this? Thanks.

Code: Select all

Snapshot created on: 20201011_2120
System:    Host: <filter> Kernel: 5.10.0-4mx-amd64 x86_64 bits: 64 compiler: N/A 
           parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-4mx-amd64 
           root=UUID=<filter> ro quiet splash 
           Desktop: Xfce 4.14.2 tk: Gtk 3.24.5 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0 
           Distro: MX-19.4_x64 patito feo May 31  2020 base: Debian GNU/Linux 10 (buster) 
Machine:   Type: Desktop Mobo: ASUSTeK model: B150M-A D3 v: Rev X.0x serial: <filter> 
           UEFI [Legacy]: American Megatrends v: 0212 date: 07/10/2015 
Battery:   Device-1: hidpp_battery_0 model: Logitech Wireless Keyboard K270 serial: <filter> 
           charge: 100% (should be ignored) rechargeable: yes status: Discharging 
           Device-2: hidpp_battery_1 model: Logitech Wireless Mouse M185 serial: <filter> 
           charge: 55% (should be ignored) rechargeable: yes status: Discharging 
CPU:       Topology: Dual Core model: Intel Core i3-6100 bits: 64 type: MT MCP arch: Skylake-S 
           family: 6 model-id: 5E (94) stepping: 3 microcode: D6 L2 cache: 3072 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 29598 
           Speed: 800 MHz min/max: 800/3700 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 
           Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled 
           Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable 
           Type: mds mitigation: Clear CPU buffers; SMT vulnerable 
           Type: meltdown mitigation: PTI 
           Type: spec_store_bypass 
           mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW, 
           STIBP: conditional, RSB filling 
           Type: srbds status: Vulnerable: No microcode 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel HD Graphics 530 vendor: ASUSTeK driver: i915 v: kernel 
           bus ID: 00:02.0 chip ID: 8086:1912 
           Display: x11 server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa 
           resolution: 1920x1200~60Hz 
           OpenGL: renderer: Mesa DRI Intel HD Graphics 530 (Skylake GT2) v: 4.5 Mesa 18.3.6 
           compat-v: 3.0 direct render: Yes 
Audio:     Device-1: Intel Sunrise Point-H HD Audio 
           vendor: ASUSTeK 100 Series/C230 Series Family driver: snd_hda_intel v: kernel 
           bus ID: 00:1f.3 chip ID: 8086:a170 
           Sound Server: ALSA v: k5.10.0-4mx-amd64 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASUSTeK 
           driver: r8169 v: kernel port: e000 bus ID: 05:00.0 chip ID: 10ec:8168 
           IF: eth0 state: down mac: <filter> 
           Device-2: TRENDnet TEW-648UBM 802.11n 150Mbps Micro Wireless N Adapter [Realtek 
           RTL8188CUS] 
           type: USB driver: rtl8192cu bus ID: 1-9:3 chip ID: 20f4:648b serial: <filter> 
           IF: wlan0 state: up mac: <filter> 
Drives:    Local Storage: total: 698.65 GiB used: 67.33 GiB (9.6%) 
           ID-1: /dev/sda vendor: Samsung model: SSD 850 EVO 250GB size: 232.89 GiB block size: 
           physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 1B6Q scheme: MBR 
           ID-2: /dev/sdb vendor: Western Digital model: WD5000AZRX-00A3KB0 size: 465.76 GiB 
           block size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s rotation: 5400 rpm 
           serial: <filter> rev: 1A01 scheme: MBR 
Partition: ID-1: / raw size: 114.96 GiB size: 112.66 GiB (98.00%) used: 67.33 GiB (59.8%) 
           fs: ext4 dev: /dev/sda3 
Sensors:   System Temperatures: cpu: 31.0 C mobo: N/A 
           Fan Speeds (RPM): N/A 
Repos:     No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian buster-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian buster main contrib non-free
           2: deb http://deb.debian.org/debian-security buster/updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mxrepo.com/mx/repo/ buster main non-free
           No active apt repos in: /etc/apt/sources.list.d/various.list 
           Active apt repos in: /etc/apt/sources.list.d/vivaldi.list 
           1: deb http://repo.vivaldi.com/stable/deb/ stable main
Info:      Processes: 222 Uptime: 7h 53m Memory: 15.52 GiB used: 1.73 GiB (11.1%) Init: SysVinit 
           v: 2.93 runlevel: 5 default: 5 Compilers: gcc: 8.3.0 alt: 8 Shell: quick-system-in 
           running in: quick-system-in inxi: 3.0.36 

Huckleberry Finn

Re: Problem with Snapshot Program

#2 Post by Huckleberry Finn »

There was the same issue previously on French forum. And it was solved when only the user made the space bigger on disk though the target was a big external device. To my understanding it still needs that space as if it's going to create that iso there (for temp files etc.) + some more space so that it won't approach to 100% full even temporarily, for the system to "breathe".

User avatar
Falcon
Posts: 478
Joined: Mon Apr 22, 2019 9:34 pm

Re: Problem with Snapshot Program

#3 Post by Falcon »

I went into the Snapshot directory and deleted ALL of the files in it. This should have made the available space at least 50 GB. Then I ran the program again and it still failed with the same error, including stating that there was only 39 GB available and 41 GB was required.

User avatar
dolphin_oracle
Developer
Posts: 22657
Joined: Sun Dec 16, 2007 12:17 pm

Re: Problem with Snapshot Program

#4 Post by dolphin_oracle »

did you empty the trash/recycle bin?
http://www.youtube.com/runwiththedolphin
lenovo ThinkPad X1 Extreme Gen 4 - MX-23
FYI: mx "test" repo is not the same thing as debian testing repo.
Live system help document: https://mxlinux.org/wiki/help-antix-live-usb-system/

Huckleberry Finn

Re: Problem with Snapshot Program

#5 Post by Huckleberry Finn »

Also .. "MX Cleanup" ...

Code: Select all

cat /var/log/mx-snapshot.log

User avatar
Falcon
Posts: 478
Joined: Mon Apr 22, 2019 9:34 pm

Re: Problem with Snapshot Program  [Solved]

#6 Post by Falcon »

Dolphin, that was the fix for the problem. When I deleted the old Snapshot files I was under the assumption that they were deleted and not just moved to the trash.

After I finish the Live USB maker, I'll run MX Cleanup.

Thanks for the timely assistance...!!!

Post Reply

Return to “Software / Configuration”