lkml.org 
[lkml]   [2001]   [Nov]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRE: Unresponiveness of 2.4.16
Date

Yes, I just looked at the code in /fs/reiserfs/bitmap.c and
the comment block above the warning message specifically mentions
the low-latency patches.

I feel better now, looks like my filesystem is safe...

Torrey

Andrew Morton wrote:
[...]

> > fall over, and during the run I got the following error/
> > warning message printed about 20 times on the console
> > and in the kernel log:
> >
> > vs-4150: reiserfs_new_blocknrs, block not free<4>
> >
>
> uh-oh. I probably broke reiserfs in the low-latency patch.
>
> It's fairly harmless - we drop the big kernel lock, schedule
> away. Upon resumption, the block we had decided to allocate
> has been allocated by someone else. The filesystem emits a
> warning and goes off to find a different block.
>
> Will fix.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:13    [W:0.040 / U:2.868 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site