Changes by: buckweat (buckweat at unknown.email)
Date: 2002-08-21 15:34:11 -0700 (Wed, 21 Aug 2002)
Revision: 1628
Log message:
Ahah! Reading/writing now works as desired.
There is quite a major change, as I have moved the chunk table out of
the listed file and into the chunk dir. This file, named "ctable", is
also referred to as chunk 0. If this doesn't make sense, here's an
example:
We have file "foo" at "$MNT/foo" corresponding to inode 11.
All of foo's chunks are at "$MNT/foo/ino_11/chk_<chunk_num>".
foo's chunk table is at "$MNT/foo/ino_11/ctable".
The change was necessary, but I did not realize it until to trying to
implement truncate(), which only gives us an inode to truncate. While we
could have searched through the inode->i_dentry list and done some
frobnicating, this way has a much smaller chance of hitting weird snags.
There is currently a stupid bug in mojave_delete_inode that causes a
kernel oops when the user does an rmdir. This will be fixed promptly.