I have had a problem.
I unpacked a CVS tree of gimp, connected to my ISP
tried to start cvs with "cvs -z9 update -d" and I got
a kernel error saying that a directory inode in between
my tree got corrupted. To be more funny I couldn't kill
that cvs process and the system hung softly without panicing.
I haven't been able to unmount that device and after
syncing and rebooting e2fsck had to connect the whole
directory to lost+found.
I'm sorry that I have no snipped of this error (because it wasn't
fatal and therefore not written to disk) and I can't reproduce it either...
I just wanted to let you know that the modification in AFAIR patch-2.1.95
could have introduced a bug.....
--Servus, Daniel
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu