• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

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: 14
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