Linux-kernel mailing list archive 1998-25,: Re: ext2_truncate: inode 4113, retrying

# Re: ext2_truncate: inode 4113, retrying

Alan Cox (alan@lxorguk.ukuu.org.uk)
Tue, 23 Jun 1998 10:25:35 +0100 (BST)

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Alan Cox: "Re: Y2K"
- Previous message: Andrea Arcangeli: "Re: [{patch} print_eip for 2.0.34] Re: 2.0.34 hangs"
- In reply to: Michael Nelson: "ext2_truncate: inode 4113, retrying"
- Next in thread: Lech Szychowski: "Re: ext2_truncate: inode 4113, retrying"
- Reply: Lech Szychowski: "Re: ext2_truncate: inode 4113, retrying"

> Since installing patch-2.1.106-ac3-ac4, I am seeing several of these
> messages a day in syslog:

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

- Next message: Alan Cox: "Re: Y2K"
- Previous message: Andrea Arcangeli: "Re: [{patch} print_eip for 2.0.34] Re: 2.0.34 hangs"
- In reply to: Michael Nelson: "ext2_truncate: inode 4113, retrying"
- Next in thread: Lech Szychowski: "Re: ext2_truncate: inode 4113, retrying"
- Reply: Lech Szychowski: "Re: ext2_truncate: inode 4113, retrying"