OK, I think I found the problem with the previous patch. It was
part of the correct patch, but it wasn't quite complete. The
filesystem panic was a side effect of not clearing out all the
appropriate fields in the inode. I just needed to convince the
fat code that it didn't need to free up any of the blocks used by
the inode since the blocks are still in use by the new inode. This
small patch against 2.1.116 should finally take care of the problem
(I hope). It can also be applied on top of the previous patch for
older kernels.
- Gordon
--- linux-2.1.116/fs/vfat/namei.c Wed Aug 19 01:48:44 1998
+++ linux/fs/vfat/namei.c Wed Aug 19 01:47:50 1998
@@ -1771,6 +1771,8 @@
MSDOS_I(new_inode)->i_logstart = MSDOS_I(old_inode)->i_logstart;
MSDOS_I(new_inode)->i_attrs = MSDOS_I(old_inode)->i_attrs;
+ MSDOS_I(old_inode)->i_start = 0;
+ MSDOS_I(old_inode)->i_logstart = 0;
old_inode->i_nlink = 0;
fat_cache_inval_inode(old_inode);
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html