To “delete” /dev/loop0, first unmount anything using it, then detach its backing file with sudo losetup -d /dev/loop0. If you also want the unused device node removed, run sudo losetup --remove /dev/loop0 after detaching. Neither command deletes the backing image or partition data.
What “deleting loop0” means
/dev/loop0 is a Linux loop device: a kernel mapping that lets a file, ISO, or partition be used like a block device. It is not usually a separate physical disk. There are two distinct operations:
- Detach: disconnects the loop device from its backing storage. The node can remain in
/devand be reused. - Remove: deletes the unused loop-device node after detachment. This does not erase the backing storage.
The Linux man-pages project explains that losetup --remove removes the loop-device node through the LOOP_CTL_REMOVE ioctl (losetup(8)). Debian’s losetup(8) likewise notes that after detachment the node remains available in /dev for reuse (losetup(8)).
Safely detach or remove /dev/loop0
- Inspect what is attached. Run
losetup -ato see loop-device backing files,lsblk -fto inspect block-device filesystems and relationships, andfindmntto list mounts. Confirm that the device is really/dev/loop0and note any mount point. - Unmount its filesystem. If a filesystem from loop0 is mounted, run
sudo umount <mountpoint>, replacing<mountpoint>with the path shown byfindmnt. Do not try to remove the node while the filesystem is mounted. - Resolve dependent mappings. If device-mapper or partition mappings were created from loop0, remove or deactivate those child mappings before detaching the loop device.
- Detach the backing storage. Run
sudo losetup -d /dev/loop0. This disassociates the backing storage; it does not delete it. Detaching is sufficient if you only want the mapping gone and prefer to keep the node available for reuse. - Optionally remove the node. If you specifically want the node removed, and it is now unused, run
sudo losetup --remove /dev/loop0. - Verify the result. Re-run
losetup -a,lsblk -f, andfindmntto check that the mapping and associated mount are gone.
Why loop0 is busy
A mounted filesystem or a child mapping can keep a loop device in use. If unmounting reports that the target is busy, identify which processes have it open before stopping anything:
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
#1 Best Overall
- Check users with
sudo fuser -vm /dev/loop0orsudo lsof /dev/loop0. - Stop the responsible process or service, or close the application using the mounted filesystem.
- Unmount the filesystem and remove any dependent device-mapper or partition mappings.
- Retry
sudo losetup -d /dev/loop0.
For example, a Linux Foundation support case described /dev/loop0 backed by /dev/sda1, mounted at /mnt/1, and held by a kernel mount. In that situation, deleting the node alone cannot resolve the active use: unmount /mnt/1, address any dependent mapping, and then detach loop0.
Will removing loop0 delete the image or partition?
No. Detaching disconnects the mapping; removing the node removes the device entry. Neither operation, by itself, deletes the backing image or changes a backing partition’s contents. Linux kernel documentation for zoned loop block devices treats removing the loop device and deleting its backing files as separate steps (Zoned Loop Block Device). Delete a backing file separately only if you have confirmed it is the intended file and you want its data destroyed.
Which option should you choose?
| Goal | Action | Effect on backing data |
|---|---|---|
| Stop using the current mapping but keep the node reusable | Unmount dependents, then run sudo losetup -d /dev/loop0. |
Preserved. |
| Remove the mapping and the unused node | Unmount dependents, detach with losetup -d, then run sudo losetup --remove /dev/loop0. |
Preserved. |
| Remove the mapping and intentionally delete the backing image | Unmount dependents, detach, optionally remove the node, then delete the confirmed backing file separately. | Deleted only by the separate file-deletion action. |
If loop0 comes back
If /dev/loop0 reappears after reboot or package updates, find the service, package, or image that creates the mapping and change that source if you want it to stay absent. Repeatedly removing the node does not prevent another service from recreating it.
Quick Recap
Best Value
- 1. 9-in-1 Linux:32GB Bootable Linux USB Flash Drive for Ubuntu 24.04 LTS, Linux Mint cinnamon 22, MX Linux xfce 23, Elementary OS 8.0, Linux Lite xfce 7.0, Manjaro kde 24(Replaced by Fedora Workstation 43), Peppermint Debian 32bit (being replaced by MX Linux 32bit) for older PC, Pop OS 22, Zorin OS core xfce 17. The versions you received might be latest than above as we update them to latest/LTS when we think necessary.
- 2. Try or install:Before installing on your PC, you can try them one by one without touching your hard disks.
- 3. Easy to use: These distros are easy to use and built with beginners in mind. Most of them Come with a wide range of pre-bundled software that includes office productivity suite, Web browser, instant messaging, image editing, multimedia, and email. Ensure transition to Linux World without regrets for Windows users.
- 4. Support: Printed user guide on how to boot up and try or install Linux; please contact us for help if you have an issue. Please press "Enter" a couple of times if you see a black screen after selecting a Linux.
- 5. Compatibility: Except for MACs,Chromebooks and ARM-based devices, works with any brand's laptop and desktop PC, legacy BIOS or UEFI booting, Requires enabling USB boot in BIOS/UEFI configuration and disabling Secure Boot is necessary for UEFI boot mode. Packing: The bootable USB drive comes in a colored PET/CPP zipper bag with instructions on how to get started. The box pictured is not included.
Rank #4
- Used Book in Good Condition
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitches
