[I tried to send this to mouse in private email, but he refuses to accept it]
> I'd have a close look at the containing directory. [Asterisks denote information manually hidden for privacy. The filenames, owner and group names all make sense.] I=158304666 MODE=40770 SIZE=512 MTIME=Oct 18 16:54:06 2013 [575961711 nsec] CTIME=Oct 18 16:54:06 2013 [575961711 nsec] ATIME=Oct 19 03:30:49 2013 [445762748 nsec] OWNER=******** GRP=******** LINKCNT=2 FLAGS=0x0 BLKCNT=0x4 GEN=0x2b3d037c fsdb (inum: 158304666)> ls slot 0 ino 158304666 reclen 12: directory, `.' slot 1 ino 158304653 reclen 12: directory, `..' slot 2 ino 158304678 reclen 40: directory, `.svn' slot 3 ino 158304690 reclen 20: regular, `********.tex' slot 4 ino 158304760 reclen 20: regular, `********.tex' slot 5 ino 158304761 reclen 24: regular, `********.tex' slot 6 ino 158304762 reclen 28: regular, `********.tex' slot 7 ino 158304763 reclen 24: regular, `********.tex' slot 8 ino 158304764 reclen 24: regular, `********.tex' slot 9 ino 158304765 reclen 24: regular, `********.tex' slot 10 ino 158304766 reclen 24: regular, `********.tex' slot 11 ino 158304767 reclen 32: regular, `********.tex' slot 12 ino 158304768 reclen 28: regular, `********.tex' slot 13 ino 158304792 reclen 200: regular, `********.ps' fsdb (inum: 158304666)> lookup ********.ps component `Blatt02.ps': current inode 158304792: unallocated inode fsdb (inum: 158304792)> print current inode 158304792: unallocated inode fsdb (inum: 158304792)> back current inode: directory I=158304666 MODE=40770 SIZE=512 MTIME=Oct 18 16:54:06 2013 [575961711 nsec] CTIME=Oct 18 16:54:06 2013 [575961711 nsec] ATIME=Oct 19 03:30:49 2013 [445762748 nsec] OWNER=******** GRP=******** LINKCNT=2 FLAGS=0x0 BLKCNT=0x4 GEN=0x2b3d037c fsdb (inum: 158304666)> lookup .svn component `.svn': current inode 158304678: unallocated inode fsdb (inum: 158304678)> print current inode 158304678: unallocated inode > In particular, I'd make sure the d_type values match the types of the > pointed-to inodes. They look correct. I didn't inspect the other inodes apart from slots 2 and 13, though. > I'd also have an intensive look at the entries which produce errors, > and at the inodes named by them. Well, I just get "unallocated inode". > If you just want to repair it, rather than figuring out what's going on, I would like to find out what's going on, but I need to repair it by monday morning. Moreover, I'm rather frightned by these errors, especially the two panics on the same dir. > and you can afford to lose what's in the file Given that it's obviously an SVN working copy, I can live with losing the whole directory. I guess simply running fsck will clear slots 2 and 13. > If you have the space I don't. How do I find out which disc block a directory or inode resides in? I guess it will be hard enough to translate that to a physical block given it's a RAID, but it would be a starting point.