Messages in this thread |  | | Date | Fri, 27 Sep 1996 22:41:47 -0300 | From | Nicolas Lichtmaier <> | Subject | Re: EXT2fs panic! =( |
| |
More info about problems with the new release of e2fsck:
I got back to 1.05, but when trying to check te partition (4 Gb) it said it got a Read only filesuystem error (?) when reading (?). I strace'd it and this is the result:
open("/etc/mtab", O_RDONLY) = 3 fstat(3, {st_mode=S_IFREG|0644, st_size=47, ...}) = 0 brk(0x8045000) = 0x8045000 read(3, "/dev/sda1 / ext2 rw 1 1\nnone /p"..., 4096) = 47 lseek(3, -23, SEEK_CUR) = 24 close(3) = 0 open("/etc/mtab", O_RDWR) = -1 EROFS (Read-only file system) open("/etc/mtab", O_RDWR) = -1 EROFS (Read-only file system) ioctl(0, TCGETS, {B38400 opost isig icanon echo ...}) = 0 ioctl(1, TCGETS, {B38400 opost isig icanon echo ...}) = 0 sync() = 0 sync() = 0
[....]
lseek(3, 9113600, SEEK_SET) = 9113600 read(3, "\305\"\0\0\306\"\0\0\0\0\0\0\0\0"..., 1024) = 1024 lseek(3, 9136128, SEEK_SET) = 9136128 read(3, "\333\"\0\0\334\"\0\0\335\"\0\0\336"..., 1024) = 1024 lseek(3, 9191424, SEEK_SET) = 9191424 read(3, "\21#\0\0\22#\0\0\23#\0\0\24#\0\0"..., 1024) = 1024 lseek(3, 1233966080, SEEK_SET) = 1233966080 read(3, "6c\22\0007c\22\0008c\22\0009c\22"..., 1024) = 1024 _llseek(0x3, 0, 0xb4425400, 0xbffff770, 0) = 0 write(1, "Error reading block 2953365 (Rea"..., 98) = 98 ioctl(0, TCGETS, {B38400 opost isig icanon echo ...}) = 0 ioctl(0, SNDCTL_TMR_START, {B38400 opost isig -icanon -echo ...}) = 0 write(1, "Ignore error<y>? ", 17) = 17 fstat(0, {st_mode=S_IFCHR|0622, st_rdev=makedev(4, 0), ...}) = 0 ioctl(0, TCGETS, {B38400 opost isig -icanon -echo ...}) = 0 read(0, "y", 4096) = 1 write(1, "yes\n\n", 5) = 5 ioctl(0, SNDCTL_TMR_START, {B38400 opost isig icanon echo ...}) = 0 write(1, "Inode 4144, i_blocks wrong 1196 "..., 48) = 48 ioctl(0, TCGETS, {B38400 opost isig icanon echo ...}) = 0 ioctl(0, SNDCTL_TMR_START, {B38400 opost isig -icanon -echo ...}) = 0 write(1, "Set i_blocks to counted<y>? ", 28) = 28 read(0, <unfinished ...>
According to the man page, llseek its supossed to return 0 on successful operation. It seems that e2fsck thinks that that is an error.
Anybody has been having trouble with >2Gb filesystems and e2fsc ?
Nicolas Lichtmaier.- nick@feedback.com.ar --- FeedBack BBS - Buenos Aires/Argentina. 54-1-903-0000/1
|  |