lkml.org 
[lkml]   [2002]   [Nov]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRE: buffer layer error at fs/buffer.c:399 (Was incorrectly FS Corruption)
Date
> Andrew Morton replied so quickly he slipped under the radar:
> John W Fort wrote:
> >
> > I got this just before I went away on a trip.
> >
> > Nov 20 13:46:47 localhost kernel: buffer layer error at fs/buffer.c:399
> > ...
> > Trace; c0139526 <__find_get_block_slow+a6/e0>
> > Trace; c013a447 <unmap_underlying_metadata+17/50>
>
> Why do you say "corruption"?
>
> Was this while you were doing stuff with the root filesystem?
>
> Was that filesystem fsck'ed on that reboot?
>
> Thanks.
>

1. 'FS left in an unclean state' dosn't have the same ring to it
and when you spend so long in 'fsck' that you start contemplating
recovery from backup. Sorry bad choice of words.

2. Yes, was tarring up the kernel source, so reading and writing to
root filesystem (ext2).

3. it was wedged, so just powered down, on return the guilty FS was fscked
from a 2.2.22 boot.

Sorry it took so long to see your reply.

Thanks johnf


-
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:31    [W:0.229 / U:0.024 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site