Re: ext2_truncate: inode 4113, retrying

Lech Szychowski (lech7@lech.pse.pl)
Tue, 23 Jun 1998 13:09:27 +0200 (CEST)

> > Jun 22 15:49:44 seahunt kernel: ext2_truncate: inode 282708, retrying
> >
> > Is this something I need to be concerned about? My drive fscks clean when I
> > do a forced check on it.
>
> Chances are thats why your drive fsck's clean not with some slightly
> incorrect block counts..

I've got the same messages:

Jun 23 12:40:48 lech kernel: ext2_truncate: inode 12, retrying
Jun 23 12:40:49 lech kernel: ext2_truncate: inode 12, retrying
Jun 23 12:42:27 lech kernel: ext2_truncate: inode 12, retrying
Jun 23 12:44:43 lech kernel: ext2_truncate: inode 12, retrying
Jun 23 12:51:51 lech kernel: ext2_truncate: inode 12, retrying
Jun 23 12:55:06 lech kernel: ext2_truncate: inode 12, retrying
Jun 23 13:02:18 lech kernel: ext2_truncate: inode 12, retrying
Jun 23 13:06:15 lech kernel: ext2_truncate: inode 12, retrying

Of course "e2fsck -vf" doesn't complain at all. It looks like those
started to appear right after I've upgraded 106 from ac3 to ac4...

-- 


	Leszek.


+==========================================================================+
| lech7@pse.pl 2:480/33.7                - REAL programmers use INTEGERS - |
| Speaking just for myself...                                              |
+==========================================================================+


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu