Displaying 8 results from an estimated 8 matches for "loop_clr_fd".
2011 Jul 12
1
after mounting with -o degraded: ioctl: LOOP_CLR_FD: Device or resource busy
...bs=1 seek=2G
dd if=/dev/null of=img6 bs=1 seek=2G
mkfs.btrfs -d raid1 -m raid1 img5 img6
losetup /dev/loop4 img5
losetup /dev/loop5 img6
btrfs device scan
mount -t btrfs /dev/loop4 dir
umount dir
losetup -d /dev/loop5
mount -t btrfs -o degraded /dev/loop4 dir
umount dir
losetup -d /dev/loop4
ioctl: LOOP_CLR_FD: Device or resource busy
mkfs.ext3 /dev/loop4
mke2fs 1.39 (29-May-2006)
/dev/loop4 is apparently in use by the system; will not make a filesystem here!
this only happens after mouting with -o degraded. loopback device is
unusable until next reboot
--
To unsubscribe from this list: send the line &q...
2005 Nov 17
2
ext3-image doesn't mount anymore and reports errors
Hi folks,
we made an image of a partition by using dd. Original filesystem is
ext3 (4k block-size).
My colleague was able to mount this image once (using mount with "-o loop").
Since then anytime we try to mount it, it ends in the following error-message:
ioctl: LOOP_CLR_FD: Device or resource busy
mount: you must specify the filesystem type
We also tried to mount it on another system than our backup-machine -
without success but with the same error.
Fsck.ext3 ends in lots of inode-errors and the following one:
Error while iterating over blocks in inode 131736: Ill...
2010 Mar 14
0
[patches] klibc review unsorted patch queue
...poweroff
diff --git a/usr/utils/loop.h b/usr/utils/loop.h
new file mode 100644
index 0000000..9839f57
--- /dev/null
+++ b/usr/utils/loop.h
@@ -0,0 +1,49 @@
+#define LO_CRYPT_NONE 0
+#define LO_CRYPT_XOR 1
+#define LO_CRYPT_DES 2
+#define LO_CRYPT_CRYPTOAPI 18
+
+#define LOOP_SET_FD 0x4C00
+#define LOOP_CLR_FD 0x4C01
+#define LOOP_SET_STATUS 0x4C02
+#define LOOP_GET_STATUS 0x4C03
+#define LOOP_SET_STATUS64 0x4C04
+#define LOOP_GET_STATUS64 0x4C05
+
+#define LO_NAME_SIZE 64
+#define LO_KEY_SIZE 32
+
+struct loop_info {
+ int lo_number;
+ dev_t lo_device;
+ unsigned long lo_inode;
+ dev_t lo_rdevice;...
2019 Oct 31
0
[PATCH 2/2] loop: switch to linux/loop.h
...h
diff --git a/usr/utils/loop.h b/usr/utils/loop.h
deleted file mode 100644
index 667f7dc0..00000000
--- a/usr/utils/loop.h
+++ /dev/null
@@ -1,49 +0,0 @@
-#define LO_CRYPT_NONE 0
-#define LO_CRYPT_XOR 1
-#define LO_CRYPT_DES 2
-#define LO_CRYPT_CRYPTOAPI 18
-
-#define LOOP_SET_FD 0x4C00
-#define LOOP_CLR_FD 0x4C01
-#define LOOP_SET_STATUS 0x4C02
-#define LOOP_GET_STATUS 0x4C03
-#define LOOP_SET_STATUS64 0x4C04
-#define LOOP_GET_STATUS64 0x4C05
-
-#define LO_NAME_SIZE 64
-#define LO_KEY_SIZE 32
-
-struct loop_info {
- int lo_number;
- __kernel_old_dev_t lo_device;
- unsigned long lo_inode;
- __ker...
2005 Dec 21
1
/dev/loopX not released when domU terminates ?
Hello all,
I have some DomU''s with root and swap images
on files under Xen 3.0.0
Investigating some cases of boot failure of domUs,
I stumbled upon the fact that when a domU is shutdown
via xm shutdown, not all of its images are released
from their /dev/loopX - devices.
That is,
for i in /dev/loop*; do losetup $i; done
still shows output for that image.
It seems to me that the
2019 Nov 05
0
[klibc:master] loop: switch to linux/loop.h
...)
diff --git a/usr/utils/loop.h b/usr/utils/loop.h
deleted file mode 100644
index 9abc2874..00000000
--- a/usr/utils/loop.h
+++ /dev/null
@@ -1,49 +0,0 @@
-#define LO_CRYPT_NONE 0
-#define LO_CRYPT_XOR 1
-#define LO_CRYPT_DES 2
-#define LO_CRYPT_CRYPTOAPI 18
-
-#define LOOP_SET_FD 0x4C00
-#define LOOP_CLR_FD 0x4C01
-#define LOOP_SET_STATUS 0x4C02
-#define LOOP_GET_STATUS 0x4C03
-#define LOOP_SET_STATUS64 0x4C04
-#define LOOP_GET_STATUS64 0x4C05
-
-#define LO_NAME_SIZE 64
-#define LO_KEY_SIZE 32
-
-struct loop_info {
- int lo_number;
- dev_t lo_device;
- unsigned long lo_inode;
- dev_t lo_rdevice;...
2009 Aug 05
2
Unable to start domU because losetup fails
...039235 (/xen/iso/i386-netbsd-5.iso)
/dev/loop104: [0012]:3039235 (/xen/iso/i386-netbsd-5.iso)
/dev/loop105: [0012]:3039235 (/xen/iso/i386-netbsd-5.iso)
/dev/loop106: [0012]:3039235 (/xen/iso/i386-netbsd-5.iso)
/dev/loop107: [0012]:3039235 (/xen/iso/i386-netbsd-5.iso)
# losetup -d /dev/loop1
ioctl: LOOP_CLR_FD: Device or resource busy
# lsof | grep "loop1 "
loop1 15416 root cwd DIR 254,0 4096
2 /
loop1 15416 root rtd DIR 254,0 4096
2 /
loop1 15416 root txt unknown
/proc/15416/exe
# p...
2019 Oct 31
3
[PATCH 1/2] loop: fix loop_info struct
Otherwise, stack can be corrupted resulting in incorrect runtime
behaviour. For example, overriding argc from main().
References: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1850184
Signed-off-by: Michael Hudson-Doyle <michael.hudson at ubuntu.com>
Signed-off-by: Adam Conrad <adconrad at ubuntu.com>
Signed-off-by: Dimitri John Ledkov <xnox at ubuntu.com>
---