blocks|key|910020|text|您确定设备不忙吗？您是否曾尝试使用热熔器来确定可能的PID？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|910021|预防获取所有可能的信息：|910022|fuser+-c+/dev/loop0
fuser+-d+/dev/loop0
fuser+-f+/dev/loop0|code-block|syntax|javascript|910023|尝试停止该进程，可以使用/dev/loop0。如有必要，使用kill+-9或尝试使用fuser+-k发送终止信号->，请查看man+fuser。|offset|length|style|CODE|910024|entityMap^0|0|0|0|U|7|16|8|1Q|9|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|S|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|T|8|@$K|U|L|V|M|N]|$K|W|L|X|M|N]|$K|Y|L|Z|M|N]]|9|@]|A|$]]|$1|O|3|-4|5|6|7|10|8|@]|9|@]|A|$]]]|P|$]]

Are you sure that the device isn't busy? Have you ever tried fuser to determine an possible PID?

Precautionary get all possible information:

<pre><code>fuser -c /dev/loop0
fuser -d /dev/loop0
fuser -f /dev/loop0
</code></pre>

Try to stop the process, which could use /dev/loop0. If necessary use <code>kill -9</code> or try <code>fuser -k</code> to send the kill signal -> look at <code>man fuser</code>.

blocks|key|694027|text|您可能还必须使用dmsetup删除设备映射。如果不干扰任何其他映射，最简单的方法就是使用dmsetup+remove_all。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|694028|entityMap^0|8|7|18|I|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|M|8|@]|D|@]|E|$]]]|G|$]]

You may have to also use <code>dmsetup</code> to remove the device mapping. Easiest way, if it doesn't interfere with any other mappings is to use a <code>dmsetup remove_all</code>.

blocks|key|694077|text|我在使用SD卡时也遇到了类似的问题，Aaoron建议我使用dmsetup。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|694078|具体地说，您应该能够ls+/dev/mapper以查看是否存在任何loop0pX分区。|offset|length|style|CODE|694079|如果是这样的话，您可以使用dmsetup+remove+/dev/mapper/loop0p2来清除任何不必要的分区。如果您想要附加一些映射，这会很有用。|694080|entityMap^0|0|A|2|X|7|0|D|Y|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@$D|N|E|O|F|G]|$D|P|E|Q|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|R|8|@$D|S|E|T|F|G]]|9|@]|A|$]]|$1|J|3|-4|5|6|7|U|8|@]|9|@]|A|$]]]|K|$]]

I had a similar issue with an SD card and Aaoron Flin's suggestion to use dmsetup worked for me. 

Specifically, you should be able to <code>ls</code> /dev/mapper to see if any <code>loop0pX</code> partitions exist. 

If so, you can use <code>dmsetup remove /dev/mapper/loop0p2</code> to get rid of any unnecessary partitions. This can be useful if you want to keep some mappings attached.

blocks|key|910229|text|今天我遇到了同样的问题，之前的答案都没有解决它(我没有尝试重新加载循环内核模块，因为我想了解实际的问题)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|910230|事实证明，与循环设备关联的映像文件包含一个"Linux+LVM“分区，该分区是自动设置的，如pvscan所示|offset|length|style|CODE|910231|$+pvscan
++PV+/dev/sda1++++VG+server-vg+++lvm2+[417,76+GiB+/+0++free]
++PV+/dev/loop0+++VG+vbox-vg+++++lvm2+[7,81+GiB+/+0++++free]
++Total:+2+[425,57+GiB]+/+in+use:+2+[425,57+GiB]+/+in+no+VG:+0+[0+++]|code-block|syntax|javascript|910232|因此，我停用了卷组中的所有逻辑卷：|910233|$+vgchange+--activate+n+vbox-vg
++0+logical+volume(s)+in+volume+group+"vbox-vg"+now+active|910234|最终，我能够很好地分离环路设备：|910235|$+losetup+-d+/dev/loop0
$+losetup+-a|910236|entityMap^0|0|1A|6|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|X|8|@$D|Y|E|Z|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|10|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|11|8|@]|9|@]|A|$]]|$1|O|3|P|5|J|7|12|8|@]|9|@]|A|$K|L]]|$1|Q|3|R|5|6|7|13|8|@]|9|@]|A|$]]|$1|S|3|T|5|J|7|14|8|@]|9|@]|A|$K|L]]|$1|U|3|-4|5|6|7|15|8|@]|9|@]|A|$]]]|V|$]]

I had the same issue today and none of the previous answers fixed it (I didn't try to reload the loop kernel module, because I wanted to understand the actual issue).

It turns out the image file associated with the loop device contained an "Linux LVM" partition, which was automatically set as shown by <code>pvscan</code>:

<pre><code>$ pvscan
 PV /dev/sda1 VG server-vg lvm2 [417,76 GiB / 0 free]
 PV /dev/loop0 VG vbox-vg lvm2 [7,81 GiB / 0 free]
 Total: 2 [425,57 GiB] / in use: 2 [425,57 GiB] / in no VG: 0 [0 ]
</code></pre>

So I had de deactivate all the logical volumes inside the volume group:

<pre><code>$ vgchange --activate n vbox-vg
 0 logical volume(s) in volume group "vbox-vg" now active
</code></pre>

Eventually I was able to nicely detach the loop device:

<pre><code>$ losetup -d /dev/loop0
$ losetup -a
</code></pre>

blocks|key|909972|text|尝试重新加载循环内核模块。如果没有帮助，则重新启动。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|909973|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Try reloading the loop kernel module. If it does not help then reboot.

blocks|key|910132|text|如果您使用的是Luk，则需要首先使用luksClose|type|unstyled|depth|inlineStyleRanges|entityRanges|data|910133|cryptsetup+luksClose+$whatever
losetup+-D|code-block|syntax|javascript|910134|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

If you're using Luks, you need to luksClose first

<pre><code>cryptsetup luksClose $whatever
losetup -D
</code></pre>

blocks|key|910384|text|跑|type|unstyled|depth|inlineStyleRanges|entityRanges|data|910385|mount+%7C+grep+/dev/loopN|code-block|syntax|javascript|910386|要检查循环设备是否安装在某个位置，请运行|910387|umount+/dev/loopN+|910388|来卸载它。|910389|如果仍有问题，则运行|910390|lsof+%7C+grep+loopN|910391|检查哪个进程正在使用它，然后杀死它。|910392|entityMap^0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|W|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|X|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|Y|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|Z|8|@]|9|@]|A|$]]|$1|O|3|P|5|D|7|10|8|@]|9|@]|A|$E|F]]|$1|Q|3|R|5|6|7|11|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|T|$]]

Run

<pre><code>mount | grep /dev/loopN
</code></pre>

to check if the loop device is being mounted somewhere,
then run 

<pre><code>umount /dev/loopN 
</code></pre>

to unmount it.

If still have problem, then run

<pre><code>lsof | grep loopN
</code></pre>

to check which process is using it then kill it.

blocks|key|910147|text|肯定有一个进程在使用它。如果你不能确定是哪个进程阻止了它的删除，那么如果可以的话，重新启动你的服务器。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|910148|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Definitely there is a process using it. If you couldn't determine which process is preventing it from deleting, then restart your server if you can.

blocks|key|910289|text|与@frntn相同。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|910290|循环被RAID占用：|910291|#+cat+/proc/mdstat

Personalities+:+[raid0]

md126+:+active+raid0+loop6p5[1]+loop5p3[0]
++209584128+blocks+super+1.2+512k+chunks

md127+:+active+raid0+loop6p2[1]+loop5p2[0]
++31440896+blocks+super+1.2+512k+chunks|code-block|syntax|javascript|910292|我把它们移走了，所有的东西都会再次服从命令。|910293|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|O|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|P|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

Same as by @frntn.

Loops were occupied by RAID:

<pre><code># cat /proc/mdstat

Personalities : [raid0]

md126 : active raid0 loop6p5[1] loop5p3[0]
 209584128 blocks super 1.2 512k chunks

md127 : active raid0 loop6p2[1] loop5p2[0]
 31440896 blocks super 1.2 512k chunks
</code></pre>

I removed them and everything obeys the orders again.

blocks|key|694294|text|我只需右键单击dolphin中的环路设备并将其卸载。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|694295|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I just right click the loop device in dolphin and unmount it.

I unsafely removed a USB device that was attached to loop0 with <code>losetup</code> and could not delete nor detach loop0 afterwards.

<code>losetup -a</code> shows <code>/dev/loop0: [0005]:145606719 (/dev/sdb1)</code>

When I remount the device to /dev/sdb1, <code>umount</code> it and try <code>losetup -d /dev/loop0</code>, I will still get the same error <code>loop: can't delete device /dev/loop0: Device or resource busy</code>. Is there a way to get rid of the loop device?

Cannot delete device /dev/loop0

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋 

腾讯云代码助手

CODING DevOps

Cloud Studio

SDK中心

API中心

命令行工具

我不安全地移除了一个通过losetup连接到loop0的USB设备，之后无法删除或分离loop0。losetup -a显示/dev/loop0: [0005]:145606719 (/dev/sdb1)当我将设备重新挂载到/dev/sdb1，umount它并尝试losetup -d /dev/loop0时，我仍然会得到相同的错误loop: can't delete device /dev/loop

问无法删除设备/dev/loop0
EN

回答 10

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问无法删除设备/dev/loop0EN

回答 10

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问无法删除设备/dev/loop0
EN