• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Inviting everyone to the UX test of a new security feature in the WP Toolkit
    For WordPress site owners, threats posed by hackers are ever-present. Because of this, we are developing a new security feature for the WP Toolkit. If the topic of WordPress website security is relevant to you, we would be grateful if you could share your experience and help us test the usability of this feature. We invite you to join us for a 1-hour online session via Google Meet. Select a convenient meeting time with our friendly UX staff here.

Resolved /dev/loop is 100%

mariodieck

New Pleskian
Server operating system version
Debian 11.7
Plesk version and microupdate number
Plesk Obsidian 18.0.54
Hello, I noticed that /dev/loop has a utilization of 100%

df -h outputs the following
Code:
Dateisystem    Größe Benutzt Verf. Verw% Eingehängt auf
udev             16G       0   16G    0% /dev
tmpfs           3,2G    2,8M  3,2G    1% /run
/dev/md2        2,7T    403G  2,2T   16% /
tmpfs            16G     36K   16G    1% /dev/shm
tmpfs           5,0M     24K  5,0M    1% /run/lock
/dev/loop7      128K    128K     0  100% /snap/bare/5
/dev/loop3      9,5M    9,5M     0  100% /snap/chromium-ffmpeg/34
/dev/loop6       24M     24M     0  100% /snap/chromium-ffmpeg/33
/dev/loop1      165M    165M     0  100% /snap/gnome-3-28-1804/198
/dev/loop9      119M    119M     0  100% /snap/core/15511
/dev/loop4       56M     56M     0  100% /snap/core18/2785
/dev/loop5       56M     56M     0  100% /snap/core18/2790
/dev/loop12     165M    165M     0  100% /snap/gnome-3-28-1804/194
/dev/loop11     185M    185M     0  100% /snap/opera/251
/dev/loop10      82M     82M     0  100% /snap/gtk-common-themes/1534
/dev/loop8       92M     92M     0  100% /snap/gtk-common-themes/1535
/dev/md0        470M     84M  362M   19% /boot
/dev/loop13     186M    186M     0  100% /snap/opera/253
/dev/loop0      106M    106M     0  100% /snap/core/15925

snap list --all outputs the following
Code:
Name               Version                     Rev    Tracking       Publisher        Notes
bare               1.0                         5      latest/stable  canonical✓       base
chromium-ffmpeg    0.1                         34     latest/stable  canonical✓       -
chromium-ffmpeg    0.1                         33     latest/stable  canonical✓       disabled
core               16-2.60.2                   15925  latest/stable  canonical✓       core
core               16-2.59.5                   15511  latest/stable  canonical✓       core,disabled
core18             20230703                    2790   latest/stable  canonical✓       base
core18             20230530                    2785   latest/stable  canonical✓       base,disabled
gnome-3-28-1804    3.28.0-19-g98f9e67.98f9e67  198    latest/stable  canonical✓       -
gnome-3-28-1804    3.28.0-19-g98f9e67.98f9e67  194    latest/stable  canonical✓       disabled
gtk-common-themes  0.1-81-g442e511             1535   latest/stable  canonical✓       -
gtk-common-themes  0.1-79-ga83e90c             1534   latest/stable  canonical✓       disabled
opera              102.0.4880.16               253    latest/stable  opera-software✓  -
opera              101.0.4843.58               251    latest/stable  opera-software✓  disabled

is there a solution for this?
 

Attachments

  • Desktop Screenshot 2023.08.27 - 11.16.35.12.jpg
    Desktop Screenshot 2023.08.27 - 11.16.35.12.jpg
    628.5 KB · Views: 13
Hi,
Loop devices technically consist of the exact size of the mounted filesystem content, hence they will always be 100%. No fix is needed here.

>> Mounting a file containing a file system via such a loop mount makes the files within that file system accessible.
 
Back
Top