Re: 1.3.69: smbfs/vfat Oops...

Gordon Chaffee (chaffee@odie.cs.berkeley.edu)
Fri, 8 Mar 1996 09:55:56 -0800

In article <199602291853.TAA00541@ld301.ec-lille.fr> you write:
>I've got un oops while running smbfs/vfat/[ctrl][scroll_lock].
>
>I'm using linux-1.3.69 with vfat/smbfs as modules. I'm using kerneld
>to load modules.
>My system is a 486DX2-66,VESA / 20MoRAM / AHA-1542C / NE-2000.
>
>It is the first time I'm using smbfs and I had to patch smbmount because
>the in the ksmbfs-0.3 distribution it searches smbfs.o in /lib/modules/x.xx.xx
>and not in /lib/modules/x.xx.xx/fs where it is now.
>I was using smbfs for 24 hours only.
>Someone was makeing a 'cp -a' from a smbfs mounted partition to a vfat one.
>At the same time I was doing several [ctrl][scroll_lock] and
>[shift][scroll_lock].
>I've got some 'Aiee/Oops' messages and system crashed...

>From your message, I'm not sure where the problem is occurring. There
are a few problems in kernel vfat that might cause this problem. The
latest version can be found at

http://www-plateau.cs.berkeley.edu/people/chaffee/vfat.html

This also fixes one rather serious bug as well as a number of less
serious problems. The serious bug is that you could remove a non-empty
directory with 'rmdir dir'.

Gordon Chaffee
chaffee@bugs-bunny.cs.berkeley.edu