Off-Topic > Release Candidate Testing

Error in the umount

(1/2) > >>

vinnie:
In the new rc5, after install programs (geany and xfe +locales) the usbstick where the system is installed is unable to unmount, the error declare a partition busy.
The older rc2 don't have this problem (I tried simply replacing the kernel and the ramdisk and reinstalling from scratch).
The file tcz2ram.lst is complete.

vinnie:
with 2.4 stable this problem is resolved!
you are mythic!

danielibarnes:
It sounds like this is the problem I observed recently in TC 2.3.1 caused by the tcz2ram function in tce-load. The script did not "umount -d" so the loop device was not deleted when the extension is unmounted. The loop device was still linked to the file on shutdown, so the filesystem could not be re-mounted read-only. TC 2.4 fixes this.

An addition to rc.shutdown in an earlier version of TC addresses the "umount: can't mount xyz read-only" problem:
for loop in $(losetup -a|cut -d: -f1); do umount -d $loop 2>/dev/null; done

and adding "losetup -d" to the end prevents this error even if -d is omitted when unmounting:
for loop in $(losetup -a|cut -d: -f1); do umount -d $loop 2>/dev/null || losetup -d $loop; done

It might be worth adding to the next version as a safeguard, but as observed, the real issue is resolved in 2.4.

vinnie:
This problem returns.
This time on a microcore 2.4.1 installed in this manner.
Plus I added core elements in tcz2ram.list, that is complete.
   
The error is the same: "umount: can't umount /mnt/hda1: Device or resource busy"

combo3:
To see which process is using the device try running:

fuser -m /mnt/hda1
ps | grep PID#

Navigation

[0] Message Index

[#] Next page