From: Andreas Dilger <adilger@turbolinux.com>
To: Petri Kaukasoina <kaukasoi@elektroni.ee.tut.fi>
Cc: linux-kernel@vger.kernel.org
Subject: Re: EXT2-fs error in 2.4.0
Date: Wed, 10 Jan 2001 12:04:28 -0700 (MST) [thread overview]
Message-ID: <200101101904.f0AJ4St12593@webber.adilger.net> (raw)
In-Reply-To: <20010110171535.A206@elektroni.ee.tut.fi> "from Petri Kaukasoina at Jan 10, 2001 05:15:35 pm"
You write:
> Got these in 2.4.0. Sorry if it's a known problem: I haven't been following
> the list very closely. This is a 100 MHz pentium and the kernel was compiled
> with gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release). After
> booting to 2.2.latest.latest fsck did its fscking without telling anything.
>
> Jan 10 16:28:22 elektroni kernel: EXT2-fs error (device ide0(3,3)): ext2_free_blocks: Freeing blocks not in datazone - block = 779318387, count = 1
> Jan 10 16:28:22 elektroni kernel: EXT2-fs error (device ide0(3,3)): ext2_free_blocks: Freeing blocks not in datazone - block = 1600484464, count = 1
> Jan 10 16:28:22 elektroni kernel: EXT2-fs error (device ide0(3,3)): ext2_free_blocks: Freeing blocks not in datazone - block = 1852403827, count = 1
> Jan 10 16:28:22 elektroni kernel: EXT2-fs error (device ide0(3,3)): ext2_free_blocks: Freeing blocks not in datazone - block = 1801678700, count = 1
Decoding the first few words to hex, then ASCII gives
sts.pte_spinlock
#define pgtable_cache_size (pgt_quicklists.pgtable_cache_sz)
#define pgd_
and I it continues. The defines are from include/asm-sparc/pgalloc.h
and it is possible the first few words are out-of-order frees of indirect
blocks or something. In any case, were you just untarring a 2.4 kernel
tree at the time of this problem? That would be a bad thing, since it
would point to a bug still in the 2.4.0 kernel.
Alternately, were you just rm -r an old kernel tree? Is it possible you
have not fsck'd this filesystem since running one of 2.4.0-test10 through
2.4.0-test12 (or maybe even test13)? In this case, it is possible that
the filesystem was corrupted with the older kernels, but you just didn't
notice it if it was in an unused kernel tree.
The sequence of events leading to this bug would help a great deal...
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
\ would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/ -- Dogbert
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-10 19:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-10 15:15 Petri Kaukasoina
2001-01-10 19:04 ` Andreas Dilger [this message]
2001-01-10 20:39 ` Petri Kaukasoina
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=200101101904.f0AJ4St12593@webber.adilger.net \
--to=adilger@turbolinux.com \
--cc=kaukasoi@elektroni.ee.tut.fi \
--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®