mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter Osterlund <petero2@telia.com>
To: Andrew Morton <akpm@zip.com.au>
Cc: Peter Osterlund <petero2@telia.com>, linux-kernel@vger.kernel.org
Subject: Re: 2.5.25: buffer layer error at buffer.c:406
Date: 12 Jul 2002 00:30:13 +0200	[thread overview]
Message-ID: <m2n0sxkidm.fsf@best.localdomain> (raw)
In-Reply-To: <3D2DE5D7.B65C7D08@zip.com.au>

Andrew Morton <akpm@zip.com.au> writes:

> Peter Osterlund wrote:
> > 
> > When I booted 2.5.25 I got the error "buffer layer error at
> > buffer.c:406". It happened three times within one second. After that it
> > didn't happen again. The error messages didn't seem to cause any harm.
> > 
> > I rebooted the machine, but the error didn't show up again. The only
> > difference was that on the first boot, the machine decided to run an
> > ext2 file system check.
> > 
> 
> Looks like the fsck left some pagecache behind, perhaps with a
> different blocksize.  I have some adjustments in that ares which
> _may_ make it go away - not sure.
> 
> Is it the root filesystem?  And could you please send me the
> `dumpe2fs -h' output for that filesystem?

Yes, it is the root filesystem, which is the only filesystem on that
machine (An old laptop). I noticed the block size is 1Kb, maybe that
has something to do with the problem.

pengo:/home/petero# /sbin/dumpe2fs -h /dev/hda4
dumpe2fs 1.25 (20-Sep-2001)
Filesystem volume name:   <none>
Last mounted on:          <not available>
Filesystem UUID:          e02ff420-1808-11d2-92dd-b0a589171a72
Filesystem magic number:  0xEF53
Filesystem revision #:    0 (original)
Filesystem features:      (none)
Filesystem state:         not clean
Errors behavior:          Continue
Filesystem OS type:       Linux
Inode count:              759808
Block count:              3032064
Reserved block count:     5000
Free blocks:              202811
Free inodes:              625901
First block:              1
Block size:               1024
Fragment size:            1024
Blocks per group:         8192
Fragments per group:      8192
Inodes per group:         2048
Inode blocks per group:   256
Last mount time:          Thu Jul 11 21:16:09 2002
Last write time:          Fri Jul 12 00:23:44 2002
Mount count:              2
Maximum mount count:      20
Last checked:             Thu Jul 11 20:36:03 2002
Check interval:           15552000 (6 months)
Next check after:         Tue Jan  7 19:36:03 2003
Reserved blocks uid:      0 (user root)
Reserved blocks gid:      0 (group root)

-- 
Peter Osterlund - petero2@telia.com
http://w1.894.telia.com/~u89404340

      reply	other threads:[~2002-07-11 22:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-11 19:40 Peter Osterlund
2002-07-11 20:08 ` Andrew Morton
2002-07-11 22:30   ` Peter Osterlund [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m2n0sxkidm.fsf@best.localdomain \
    --to=petero2@telia.com \
    --cc=akpm@zip.com.au \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®