> Hmm.... It says the inode doesn't contain a file now. (This is after > a massive e2fsck run. I had to kill -9 the filesystem)
If you ever want to debug any kind of ext2fs problem, you have to examine the situation before running e2fsck. It's the job of ext2fs to repair any bogus state in the filesystem, though it ought to tell you about it when it makes changes. If you ran e2fsck and it produced a lot of output and you asked us here for help debugging the problem without including all those details, then, well, get stuffed--you know better than that. Previously you mentioned an error in read_inode and didn't say anything at all about the filesystem wedging or having to kill it. I'm having a hard time trying to get the facts straight. Since it sounds like you've thoroughly destroyed all the evidence, I'm not going to worry about trying to investigate this particular instance. If you have a similar occurrence again, we'll need a whole lot more information preserved to have any hope of figuring it out. > Quick followup note: I just noticed that the e2fsprogs this Hurd has > installed is over a year old. That's probably a reasonable source of > my problems. *sigh* sorry about this. I don't know any reason to expect problems from an older e2fsprogs. _______________________________________________ Bug-hurd mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-hurd
