Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

losetup -d LOOP_CLR_FD: Device or resource busy

95 views
Skip to first unread message

Scooter

unread,
Nov 6, 2008, 10:04:51 AM11/6/08
to
I am taking advantage of a windows backup process to backup some Linux
boxes by mounting a filesystem on windows, but I'm having some trouble
when attempting to unmount.

I have a windows share that I'm mounting at:

"/mnt/winserver1"

In that share is a previously created sparse file created as an ext3
file system
I attache a loopback device to it:

"losetup /dev/loop1 /mnt/winserver1/fsfile"


Then I mount the loopback device

"mount /dev/loop1 /mnt/backup-tux"

That worked fine for the most part.

But when i want to backup the filesystem file on windows I want to
make sure its unmounted,
so after copying everything to /mnt/backup-tux, I unmount everything

"umount /mnt/backup-tux"

"losetup -d /dev/loop1"

Typically this works fine. But then I get into a situation where the
losetup -d doesn't want to work anymore.
I continue to get a

"ioctl: LOOP_CLR_FD: Device or resource busy"

If I run

"losetup /dev/loop1"

there is a long pause and then it returns

"loop: can't get info on device /dev/loop1: Input/output error"

Any thoughts? I'd love to just reboot but it's not an option, there's
too much stuff going on on this server.


Hactar

unread,
Nov 6, 2008, 4:49:48 PM11/6/08
to
In article <ec4a48da-6b37-47f8...@b2g2000prf.googlegroups.com>,

Scooter <slbe...@gmail.com> wrote:
>
> Typically this works fine. But then I get into a situation where the
> losetup -d doesn't want to work anymore.
> I continue to get a
>
> "ioctl: LOOP_CLR_FD: Device or resource busy"
>
> If I run
>
> "losetup /dev/loop1"
>
> there is a long pause and then it returns
>
> "loop: can't get info on device /dev/loop1: Input/output error"
>
> Any thoughts? I'd love to just reboot but it's not an option, there's
> too much stuff going on on this server.

Got me, that method sounds similar to what I do sometimes.

There's a module "loop"; you could try removing it, but since it thinks
loop1 is busy, that'll probably fail. "lsof | grep loop1"?

As a temporary workaround, you could always use loop2, then loop3, etc.
If /dev gives out before you reach loop255(?) or finish, you could always
make some device files by hand.

--
-eben QebWe...@vTerYizUonI.nOetP http://royalty.mine.nu:81
SCORPIO: Get ready for an unexpected trip when you fall screaming
from an open window. Work a little harder on improving your low self
esteem, you stupid freak. -- Weird Al, _Your Horoscope for Today_

Scooter

unread,
Nov 11, 2008, 9:06:39 AM11/11/08
to
Yeah I've just been using the next loop. I guess that will work until
I can reboot.
0 new messages