Messages in this thread |  | | Date | Sun, 29 Sep 1996 00:57:57 -0400 | From | "Theodore Y. Ts'o" <> | Subject | Re: EXT2fs panic! =( |
| |
Date: Fri, 27 Sep 1996 22:41:47 -0300 From: Nicolas Lichtmaier <nick@feedback.com.ar>
According to the man page, llseek its supossed to return 0 on successful operation. It seems that e2fsck thinks that that is an error.
What version of libc are you using? I suspect what's going on is that whoever implemented llseek in the libc did it differently than I had anticipated. (See lib/ext2/llseek.c for how I expected it to be done; yes, the llseek system call returns 0 for successful operation. I however implemented the llseek functions so that it functions just like lseek(); that is, it returns the **old** location of cursor on success, instead of zero.)
A quick work around is to override configure such that you compile files (epsecially lib/ext2fs/llseek.c), so that HAVE_LLSEEK is not this. This will cause lib/ext2fs/llseek to use a built-in llseek() funct9ion, which will work much better for llseek.c().
- Ted
|  |