These are debugging
> Jun 22 06:15:09 seahunt kernel: ext2_truncate: inode 4113, retrying
> Jun 22 10:15:22 seahunt kernel: ext2_truncate: inode 4185, retrying
> 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..
Alan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu