Re: [Cooker] Error unmounting loop devices - Nautilus is guilty!
So sprach Guillaume Cottenceau am Tue, Apr 17, 2001 at 12:51:45AM +0200: What happens when you don't have gkrellm? does it work? It doesn't matter - GKrellM doesn't interfere with it. Ie. no matter if GKrellM is running or not, I can umount loop devices just fine. Not so with nautilus. Only when I shutdown nautilus I can umount loop devices fine. Alexander Skwar -- How to quote: http://learn.to/quote (german) http://quote.6x.to (english) Homepage: http://www.digitalprojects.com | http://www.iso-top.de iso-top.de - Die gnstige Art an Linux Distributionen zu kommen Uptime: 10 hours 14 minutes
Re: [Cooker] Error unmounting loop devices
Alexander Skwar [EMAIL PROTECTED] writes: So sprach Guillaume Cottenceau am Sun, Apr 15, 2001 at 10:33:25PM +0200: sure you were doing things cleanly? Yup: [root@teich /boot]# mount -o loop /ISO-Images/Done/RedHat/7.0/7.0-updates-20010408.iso /mnt/loop [root@teich /boot]# mount /dev/sda5 on / type reiserfs (rw) none on /proc type proc (rw) /dev/sda2 on /boot type ext2 (rw,sync,errors=panic,check=strict) /dev/md0 on /div type reiserfs (rw) none on /dev/pts type devpts (rw,mode=0620) /proc/bus/usb on /proc/bus/usb type usbdevfs (rw,devmode=0664,devgid=43) /div/ftp/pub/ISO-Images/Done/RedHat/7.0/7.0-updates-20010408.iso on /mnt/loop type iso9660 (rw,loop=/dev/loop1) why does it choose loop1 and not loop0? [root@teich /boot]# umount /mnt/loop ioctl: LOOP_CLR_FD: Das Gert oder die Ressource ist belegt [root@teich /boot]# rpm -q kernel kernel-2.4.3-16mdk kernel-2.4.3-19mdk Using kernel-2.4.3-19mdk I just retested on a full ISO image, I can't reproduce. Uhm, what do you mean by "cleanly"? If you were not doing things which was putting a lock on the mount. -- Guillaume Cottenceau - http://us.mandrakesoft.com/~gc/
Re: [Cooker] Error unmounting loop devices
Alexander Skwar [EMAIL PROTECTED] writes: So sprach Guillaume Cottenceau am Mon, Apr 16, 2001 at 03:37:33PM +0200: why does it choose loop1 and not loop0? Because I had mounted a loop device beforehand which didn't get released. It didn't appear into your output of "mount", that's why I asked. This seemed curious. I just retested on a full ISO image, I can't reproduce. Happens here all the time - could somebody else please check this? Would be helpful. [...] Hm, so for some reason the device really seems to be busy Hmm. Why? Please lurk into /proc and see anything. And if it really is busy, why can I still (more or less) successfully umount it? When? and how. -- Guillaume Cottenceau - http://us.mandrakesoft.com/~gc/
Re: [Cooker] Error unmounting loop devices
So sprach Guillaume Cottenceau am Mon, Apr 16, 2001 at 03:37:33PM +0200: why does it choose loop1 and not loop0? Because I had mounted a loop device beforehand which didn't get released. I just retested on a full ISO image, I can't reproduce. Happens here all the time - could somebody else please check this? [root@teich /tmp]# ls -la /boot/ insgesamt 3065 drwxr-xr-x4 root root 1024 Apr 15 15:30 ./ drwxr-xr-x 21 root root 725 Apr 13 07:17 ../ lrwxrwxrwx1 root root 22 Apr 15 15:30 System.map - System.map-2.4.3-19mdk -rw-r--r--1 root root 410599 Apr 11 06:58 System.map-2.4.3-16mdk -rw-r--r--1 root root 410731 Apr 13 05:15 System.map-2.4.3-19mdk lrwxrwxrwx1 root root1 Apr 11 21:24 boot - ./ -rw-r--r--1 root root 5868 Apr 8 18:11 boot-graphic.b -rw-r--r--1 root root 6108 Apr 8 18:11 boot-menu.b -rw-r--r--1 root root 4356 Apr 8 18:11 boot-text.b -rw-r--r--1 root root 512 Mr 31 13:12 boot.0800 lrwxrwxrwx1 root root 14 Mr 31 13:12 boot.b - boot-graphic.b -rw-r--r--1 root root 608 Apr 8 18:11 chain.b lrwxrwxrwx1 root root 18 Apr 15 15:30 config - config-2.4.3-19mdk -rw-r--r--1 root root33417 Apr 11 06:58 config-2.4.3-16mdk -rw-r--r--1 root root33572 Apr 13 05:15 config-2.4.3-19mdk -rw-r--r--1 root root 256 Mr 31 13:12 de-latin1-nodeadkeys.klt drwxr-xr-x2 root root 1024 Apr 14 23:11 grub/ -rw-r--r--1 root root 196058 Apr 11 21:24 initrd-2.4.3-16mdk.img -rw-r--r--1 root root 194902 Apr 14 22:31 initrd-2.4.3-19mdk.img lrwxrwxrwx1 root root 28 Apr 14 22:31 initrd.img - /boot/initrd-2.4.3-19mdk.img lrwxrwxrwx1 root root 14 Apr 14 22:33 kernel.h - kernel.h-2.4.3 -rw-r--r--1 root root 441 Apr 15 15:31 kernel.h-2.4.3 drwxr-xr-x2 root root 1024 Mr 31 20:05 lost+found/ -rw---1 root root27648 Mr 31 13:12 map -rw-r--r--1 root root67580 Apr 9 19:00 memtest-2.5.bin -rw-r--r--1 root root 159 Mr 31 13:12 message -rw-r--r--1 root root35130 Apr 8 18:11 message-graphic -rw-r--r--1 root root 640 Apr 8 18:11 os2_d.b lrwxrwxrwx1 root root 19 Apr 14 22:30 vmlinuz - vmlinuz-2.4.3-19mdk -rw-r--r--1 root root 840671 Apr 11 06:58 vmlinuz-2.4.3-16mdk -rw-r--r--1 root root 833283 Apr 13 05:15 vmlinuz-2.4.3-19mdk [root@teich /tmp]# mkisofs -f -o boot.iso /boot/ Already cached directory seen (/boot/boot) Using INITR000.IMG;1 for /initrd-2.4.3-16mdk.img (initrd-2.4.3-19mdk.img) Using VMLIN000.3_1;1 for /vmlinuz-2.4.3-16mdk (vmlinuz-2.4.3-19mdk) Using CONFI000.3_1;1 for /config-2.4.3-16mdk (config-2.4.3-19mdk) Using SYSTE000.3_1;1 for /System.map-2.4.3-16mdk (System.map-2.4.3-19mdk) Using MESSA000.;1 for /boot/grub/messages-r (messages) Using MENU000.LST;1 for /boot/grub/menu.lst~ (menu.lst) Total translation table size: 0 Total rockridge attributes bytes: 0 Total directory bytes: 4096 Path table size(bytes): 38 Max brk space used 6504 1628 extents written (3 Mb) [root@teich /tmp]# mount -o loop boot.iso /mnt/loop [root@teich /tmp]# mount /dev/sda5 on / type reiserfs (rw) none on /proc type proc (rw) /dev/sda2 on /boot type ext2 (rw,sync,errors=panic,check=strict) /dev/md0 on /div type reiserfs (rw) none on /dev/pts type devpts (rw,mode=0620) /proc/bus/usb on /proc/bus/usb type usbdevfs (rw,devmode=0664,devgid=43) /tmp/boot.iso on /mnt/loop type iso9660 (rw,loop=/dev/loop3) [root@teich /tmp]# ls -la /mnt/loop insgesamt 4512 dr-xr-xr-x1 root root 2048 Apr 15 15:30 ./ drwxr-xr-x9 root root 186 Apr 11 17:36 ../ -r-xr-xr-x1 root root 512 Mr 31 13:12 boot.080* -r-xr-xr-x1 root root 5868 Apr 8 18:11 boot.b* -r-xr-xr-x1 root root 5868 Apr 8 18:11 boot_gra.b* -r-xr-xr-x1 root root 6108 Apr 8 18:11 boot_men.b* -r-xr-xr-x1 root root 4356 Apr 8 18:11 boot_tex.b* -r-xr-xr-x1 root root 608 Apr 8 18:11 chain.b* -r-xr-xr-x1 root root33417 Apr 11 06:58 confi000.3_1* -r-xr-xr-x1 root root33572 Apr 13 05:15 config* -r-xr-xr-x1 root root33572 Apr 13 05:15 config_2.3_1* -r-xr-xr-x1 root root 256 Mr 31 13:12 de_latin.klt* dr-xr-xr-x1 root root 2048 Apr 14 23:11 grub/ -r-xr-xr-x1 root root 196058 Apr 11 21:24 initr000.img* -r-xr-xr-x1 root root 194902 Apr 14 22:31 initrd.img* -r-xr-xr-x1 root root 194902 Apr 14 22:31 initrd_2.img* -r-xr-xr-x1 root root 441 Apr 15 15:31 kernel.h* -r-xr-xr-x1 root root 441 Apr 15 15:31 kernel_h.3* dr-xr-xr-x1 root root
Re: [Cooker] Error unmounting loop devices - Nautilus is guilty!
So sprach Guillaume Cottenceau am Mon, Apr 16, 2001 at 09:01:02PM +0200: [..nothing wrt. below..] Okay, I updated to the newest kernel 2.4.3-20mdk. I still have the exact same behaviour, *IF* I do the mounting when X + Nautilus + GKrellM is running. IOW: I tried the mounting/umounting before I logged into X, and everything worked fine. Conclusion: it's something local on my machine which you don't have. Okay, I've just killed nautilus (nautilus-1.0.1.1-4mdk), and now it's working fine even under X. Real conclusion: Loop devices and nautilus do not play well together. Alexander Skwar -- How to quote: http://learn.to/quote (german) http://quote.6x.to (english) Homepage: http://www.digitalprojects.com | http://www.iso-top.de iso-top.de - Die gnstige Art an Linux Distributionen zu kommen Uptime: 0 hours 8 minutes
Re: [Cooker] Error unmounting loop devices - Nautilus is guilty!
Alexander Skwar [EMAIL PROTECTED] writes: So sprach Guillaume Cottenceau am Mon, Apr 16, 2001 at 09:01:02PM +0200: [..nothing wrt. below..] Okay, I updated to the newest kernel 2.4.3-20mdk. I still have the exact same behaviour, *IF* I do the mounting when X + Nautilus + GKrellM is running. IOW: I tried the mounting/umounting before I logged into X, and everything worked fine. Conclusion: it's something local on my machine which you don't have. What happens when you don't have gkrellm? does it work? Okay, I've just killed nautilus (nautilus-1.0.1.1-4mdk), and now it's working fine even under X. Real conclusion: Loop devices and nautilus do not play well together. Nautilus rulz. -- Guillaume Cottenceau - http://us.mandrakesoft.com/~gc/
Re: [Cooker] Error unmounting loop devices
Alexander Skwar [EMAIL PROTECTED] writes: When I try to umount a file, I get this error: [root@teich 7.1]# umount fisher-i386-SRPMS.iso ioctl: LOOP_CLR_FD: Das Gert oder die Ressource ist belegt [root@teich 7.1]# rpm -q kernel kernel-2.4.3-19mdk sure you were doing things cleanly? [root@obiwan /tmp]# mount -o loop initrd /mnt/disk [root@obiwan /tmp]# mount | tail -1 /tmp/initrd on /mnt/disk type ext2 (rw,loop=/dev/loop0) [root@obiwan /tmp]# umount /tmp/initrd [root@obiwan /tmp]# rpm -q kernel kernel-2.4.3-19mdk -- Guillaume Cottenceau - http://us.mandrakesoft.com/~gc/
Re: [Cooker] Error unmounting loop devices
So sprach Guillaume Cottenceau am Sun, Apr 15, 2001 at 10:33:25PM +0200: sure you were doing things cleanly? Yup: [root@teich /boot]# mount -o loop /ISO-Images/Done/RedHat/7.0/7.0-updates-20010408.iso /mnt/loop [root@teich /boot]# mount /dev/sda5 on / type reiserfs (rw) none on /proc type proc (rw) /dev/sda2 on /boot type ext2 (rw,sync,errors=panic,check=strict) /dev/md0 on /div type reiserfs (rw) none on /dev/pts type devpts (rw,mode=0620) /proc/bus/usb on /proc/bus/usb type usbdevfs (rw,devmode=0664,devgid=43) /div/ftp/pub/ISO-Images/Done/RedHat/7.0/7.0-updates-20010408.iso on /mnt/loop type iso9660 (rw,loop=/dev/loop1) [root@teich /boot]# umount /mnt/loop ioctl: LOOP_CLR_FD: Das Gert oder die Ressource ist belegt [root@teich /boot]# rpm -q kernel kernel-2.4.3-16mdk kernel-2.4.3-19mdk Using kernel-2.4.3-19mdk Uhm, what do you mean by "cleanly"? Alexander Skwar -- How to quote: http://learn.to/quote (german) http://quote.6x.to (english) Homepage: http://www.digitalprojects.com | http://www.iso-top.de iso-top.de - Die gnstige Art an Linux Distributionen zu kommen Uptime: 10 hours 50 minutes
