On 05-Oct-2000 Ben Logan spoke something to the effect:
> I really need some help here...my system won't shut down properly any
> more.
>
> I have two drives in my RedHat 6.2 box. One of them had linux on it and
> the
> other windoze. I was running out of space in linux, so I wiped windows
> off
> the other disk (/dev/hda1). Then I created an ext2 filesystem on it and
> mounted it in /usr/hda1.
> Then I moved /usr/lib to /usr/hda1/lib and made a symlink so that the
> libraries could still be found in /usr/lib.
>
> Everything went fine, until I tried to shut my system down. Then I got
> the
> following error messages (the first message isn't an error, I included it
> for context):
>
> Turning off quotas [ok]
> Unmounting file systems umount2: Device or resource busy
> umount: /usr/hda1: device is busy
> umount2: Device or resource busy
> umount: /usr: device is busy
>
> No process references; use -v for the complete list
> No automatic removal. Please use umount /usr/hda1
> INIT: no more processes left in this runlevel
I have no idea what this umount2 command is or what's generating it. But,
that is likely what is causing it. Any idea where it came from? If you have
a pure rpm system:
locate umount2
will get a path, and:
rpm -qf /<path>/umount2
will get the name of the rpm that owns it.
I have 6.2, all updates (almost) and tons of compiled tarballs. I have no
such command, so it likely isn't native, though I don't have everything
installed and I can't say it isn't part of one of the packages I didn't
install. It's certainly one I haven't seen before.
> I have another system with which I did the same thing, except that I
> mounted
> the new partition (/dev/hdc1 in this case instead of /dev/hda1) directly
> as
> /usr/lib--no symlinks that way. It has the same problem now when I try
> to
> shut it down.
If the umont2 command is also shown as above, it's likely the culprit.
> Here's my /etc/fstab file:
> /dev/hdb7 / ext2 defaults 1
> 1
> /dev/hdb1 /boot ext2 defaults 1
> 2
> /dev/hdb6 /home ext2 defaults 1
> 2
> /dev/cdrom /mnt/cdrom iso9660 noauto,user,ro 0
> 0
> /dev/hdb5 /usr ext2 defaults 1
> 2
> /dev/fd0 /mnt/floppy auto noauto,user 0
> 0
> /dev/hda1 /usr/hda1 ext2 defaults 1
> 2
> none /proc proc defaults 0
> 0
> none /dev/pts devpts gid=5,mode=620 0
> 0
> /dev/hdb8 swap swap defaults 0
> 0
>
> Any help would be greatly appreciated.
I have, and have had, many symlinks such as these. I've only encountered
problems, not with symlinks, but when I had the sub-mount being called to
_mount_ before the top-level (i.e. mounting /usr/lib before /usr). I can't
recall _ever_ having a problem umounting a subdirectory before a top-level,
which is clearly what the above shows happening.
The only other reason that I can think of for this happening is if /usr/lib
or /usr/hda1/lib was in active use when the shutdown tried to umount it
(like sitting in /mnt/cdrom then issuing the command 'umount /mnt/cdrom' -
will give a device busy error). Since /usr/lib is used by many things, this
could be the case.
You might try (besides locating the umount2 command and shutting it off if
possible) logging in as single user, move the lib directory back where it
was and move something else with a symlink, like /usr/share. That one
shouldn't give you such a problem (unless umount2 is the problem) and it's
generally huge, which would free up a lot of space.
--
I have seen the fun!
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
