On Wed, 26 Mar 2003 07:51:06 -0500, Sam Varshavchik wrote: >Gary Stewart writes: > >>I know, rediculous answering my own questions on the list with yet >>more questions, but could this possibly be attributed to an inode >>mismatch after mounting that drive? Unfortunately this was all >>brought to my attention, and I'm out in the dark with no details >>about what exactly was done. I was just told about the dirs being >>moved around for lack of disk space. Course we all get to come home >> >>from fixing problems at work to yet more problems at home <g> >> >>ls: 1048648550.22325.isis.glizard.com: No such file or directory >>ls: 1048648762.23194.isis.glizard.com: No such file or directory > >If you get this in response to a plain 'ls' command, it indicates >that your >filesystem is completely corrupted. > > >>ls: 1048649483.25292.isis.glizard.com: No such file or directory >>ls: 1048655245.17196.isis.glizard.com: No such file or directory >>ls: 1048655682.19088.isis.glizard.com: No such file or directory >>total 8 >>drwx------ 2 vpopmail vchkpw 4096 Mar 25 23:14 . >>drwx------ 5 vpopmail vchkpw 4096 Jan 22 16:24 .. >> >>Now if this is an inode issue, i'm ignorant about what to do to fix >> >>it, e2fsck would seem logical but irrelevant in the sense. > >What exactly is "logical but irrelevant" about fixing a corrupted >filesystem? > > > >
Sorry for being unclear, thats what happens in all the .Drafts/tmp directories within the Maildirs. e2fsck was run and it didn't fix anything. that was one of the first things that was tried by another administrator when this was first found out about. Logical would be that if it indeed was just a filesystem problem that would be what to do, but irrelevant because that doesn't seem to be the root of the problem. -- Gary Stewart, [EMAIL PROTECTED] on 3/26/2003
