Bugzilla – Bug 139581
Yast2 doesn´t resize unmounted partition
Last modified: 2006-01-09 10:09:34 UTC
I can´t resize my /home - partition (65 -> 60 GB) because Yast claims it was still mounted. Another 'umount /home' gives back a 'partition already unmounted' Further infos: HW: Acer Aspire 1652 wlmi notebook Suse 10 OSS is the only OS on disk hda1 = / (ext3) hda5 = swap hda6 = /home (ext3)
Please attach the output of `fdisk -l' as well as of `mount' once you did the unmount. Also provide your /etc/fstab - thanks.
(In reply to comment #1) > Please attach the output of `fdisk -l' as well as of `mount' once you did the > unmount. Also provide your /etc/fstab - thanks. fdisk -l: Platte /dev/hda: 80.0 GByte, 80026361856 Byte 255 Köpfe, 63 Sektoren/Spuren, 9729 Zylinder Einheiten = Zylinder von 16065 a 512 = 8225280 Bytes Gerät boot. Anfang Ende Blöcke Id System /dev/hda1 * 1 851 6835626 83 Linux /dev/hda2 852 9729 71312535 5 Erweiterte /dev/hda5 852 1039 1510078+ 82 Linux Swap / Solaris /dev/hda6 1040 9729 69802393+ 83 Linux /etc/fstab: /dev/hda1 / ext3 acl,user_xattr 1 1 /dev/hda6 /home ext3 acl,user_xattr 1 2 /dev/hda5 swap swap defaults 0 0 proc /proc proc defaults 0 0 sysfs /sys sysfs noauto 0 0 usbfs /proc/bus/usb usbfs noauto 0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0 /dev/dvdrecorder /media/dvdrecorder subfs noauto,fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset=utf8 0 0 When I submitted this bug (if it really is one) mounting and unmounting gave no output linux:/ umount /home linux:/ linux:/ mount /home linux:/ If I try this now I get: linux:/ umount /home linux:/ device /home is busy linux:/ device /home is busy //or something like this - and yes, twice linux:/ I am not aware of having changed anything in the meantime :-(
Michael, if any process (this might include a shell) has an open file on the filesystem you want to unmount, it will fail with the message that it is busy. This is perfectly normal because it avoids filesystem corruption. Check if you hav e no process running that accesses your home-partition (this might include KDE programs). Shells in the homedir (linux:~) will also cause this.
(In reply to comment #3) Yes, after changing stopping X (init 3) and logging in as root I could reproduce this behaviour (yesterday it didn´t work, I don´t know which process interferes here. Maybe kjournald?): linux:~ # cd .. linux:/ # umount /home linux:/ # yast //cool - a bit Debian-like :-) Same as before: "partition can´t be resized because ist is still mounted" (or something similar) [btw: after restarting X with 'init 5' I couldn´t log in as user: all I got was a grey box in the top left corner, stating a problem with ksysconfig "check your installation". Logging in as root worked.]
This has already been fixed in current code base.