Strange umount problem in latest 2.4.0 kernels
Quoted 1 line
The "none" bit puzzles me the most.
It is a common misconfiguration. Given a line
device dir type options garbage
in /etc/fstab, some umount versions will complain "device busy" when the umount fails. Thus, it is better to use
proc /proc proc devpts /dev/pts devpts
instead of
none /proc proc none /dev/pts devpts
so as to avoid this silly "none busy".
But many distributions come misconfigured like this.
These days umount is done by directory, not by device, since a device may be mounted multiple times, so I expect the silly message is gone.
(Is your umount recent?)
[But this is only about the "none". I don't know what is wrong in your situation.]
Andries
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/
Quoted 8 lines · [email protected] wrote:
These days umount is done by directory, not by device, since a device may be mounted multiple times, so I expect the silly message is gone.
(Is your umount recent?)[But this is only about the "none". I don't know what is wrong in your situation.]
My umount is 2.10r. Alan says he knows what is wrong, so we're all curiously expecting -ac7 ;)
-Udo.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/
Quoted 12 lines · On 2001.01.11 [email protected] wrote:
Quoted 1 line
The "none" bit puzzles me the most.
It is a common misconfiguration. Given a line
device dir type options garbage
in
/etc/fstab, some umount versions will complain "device busy" when the umount fails. Thus, it is better to useproc /proc proc devpts /dev/pts devpts
Quoted 8 lines
instead of
none /proc proc none /dev/pts devptsso as to avoid this silly "none busy".
But many distributions come misconfigured like this.
Same cam be applied to shm ? Thus kernel Documentation/Changes should be changed:
System V shared memory is now implemented via a virtual filesystem. You do not have to mount it to use it. SYSV shared memory limits are set via /proc/sys/kernel/shm{max,all,mni}. You should mount the filesystem under /dev/shm to be able to use POSIX shared memory. Adding the following line to /etc/fstab should take care of things:
none /dev/shm shm defaults 0 0
to
shm /dev/shm shm defaults 0 0
Signature · 9 lines
J.A. Magallon $> cd pub mailto:[email protected] $> more beer Linux werewolf 2.4.0-ac5 #1 SMP Wed Jan 10 23:36:11 CET 2001 i686 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] Please read the FAQ at http://www.tux.org/lkml/
Quoted 2 lines · On Fri, 12 Jan 2001, [email protected] wrote:
Same cam be applied to shm ? Thus kernel
Documentation/Changesshould be changed:
[...]
Quoted 7 lines
none
/dev/shmshm defaults 0 0to
shm
/dev/shmshm defaults 0 0
Yes, I thought that I changed that :-( I always have the type as device in my fstab.
Linus, it is not really crucial, but still could be applied without breaking anything for sure ;-)
Greetings
Christoph
Documentation/Changes Fri Jan 12 09:03:35 2001 renamed from Documentation/Changes Mon Jan 1 19:00:04 2001 +1 -1
@@ -121,7 +121,7 @@ memory. Adding the following line to /etc/fstab should take care of things: -none /dev/shm shm defaults 0 0 +shm /dev/shm shm defaults 0 0 Remember to create the directory that you intend to mount shm on if necessary (The entry is automagically created if you use devfs). You
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/