I don't know what the reason really was for that code in the first place
(Miles wrote it). I suspect it was just transcribed from ufs. In the ufs
format it is improper for the block count to be nonzero in a free inode.
For ext2fs, the observed behavior of the Linux kernel is all we have to
const
On Wed, Jun 20, 2001 at 11:11:46AM -0700, Jeff Bailey wrote:
> Roland, et al.,
>
> Would you accept a patch to add a configure option that removes the
> annoying 'free inode' warning messages? I can set it on by default,
> if you'd like.
>
> My final preference would be to leave it disabled unt
On Wed, Jun 20, 2001 at 07:00:08PM -0400, Igor Khavkine wrote:
> On Wed, Jun 20, 2001 at 06:45:39PM -0500, Neal H Walfield wrote:
> > > I don't think the danger (or lack thereof) presented by these warnings
> > > is being dsiputed. It is simply very annoying. I have a patition
> > > for developmen
On Wed, Jun 20, 2001 at 06:45:39PM -0500, Neal H Walfield wrote:
> > I don't think the danger (or lack thereof) presented by these warnings
> > is being dsiputed. It is simply very annoying. I have a patition
> > for development that I use both in linux and Hurd.
>
> I think it was; Roland mentio
> I don't think the danger (or lack thereof) presented by these warnings
> is being dsiputed. It is simply very annoying. I have a patition
> for development that I use both in linux and Hurd.
I think it was; Roland mentioned this earlier.
> And when I run
> a build from that partition while in
On Wed, Jun 20, 2001 at 04:56:20PM -0500, Neal H Walfield wrote:
> > Would you accept a patch to add a configure option that removes the
> > annoying 'free inode' warning messages? I can set it on by default,
> > if you'd like.
> >
> > My final preference would be to leave it disabled until e2fs
> Would you accept a patch to add a configure option that removes the
> annoying 'free inode' warning messages? I can set it on by default,
> if you'd like.
>
> My final preference would be to leave it disabled until e2fsck is
> willing to fix the problem when the FS is checked with -f, but havi
Roland, et al.,
Would you accept a patch to add a configure option that removes the
annoying 'free inode' warning messages? I can set it on by default,
if you'd like.
My final preference would be to leave it disabled until e2fsck is
willing to fix the problem when the FS is checked with -f, but
