From: J Sloan <jjs@pobox.com>
To: Charles-Edouard Ruault <ce@ruault.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: File system Corruption with 2.4.16
Date: Sat, 01 Dec 2001 14:22:07 -0800 [thread overview]
Message-ID: <3C09580F.5F323195@pobox.com> (raw)
In-Reply-To: <3C0954D5.6AA3532B@ruault.com>
Charles-Edouard Ruault wrote:
> Hi there,
>
> i've experienced very weird behaviour with kernel 2.4.16 ( on at least 2
> different machines with different motherboards & CPUs ).
> I'm having ext2 filesystem problems on both machines now, one is totally
> unusable i need to reinstall it from scratch.
Are you sure? perhaps a forced fsck of all
filesystems would do the trick. New linux users
coming from a microsoft background are too
quick to reinstall as a means of maintenance.
>
> I've noticed the problem on different points :
> - first lots of problems with symlinks ....
> unable to compile the kernel for example it bails out with "too many
> symlinks levels" ,
>
> /usr/include/asm/pgtable.h:109:33:
> /usr/src/linux/include/asm/pgtable-2level.h: Too many levels of symbolic
> links
Yes, it looks like the filesystem is corrupted.
> I backtracked to kernel 2.4.14 and now after doing an fsck on all my
> partitions ( only one problem reported on /home ) , everything is back
> to normal.
Have you tried 2.4.16 since the fsck?
> I've read that there was a filesystem problem in 2.4.15 that is supposed
> to be fixed in 2.4.16.
That is the case,
> These 2 machines did run 2.4.15 from it's birtday until 2.4.16 was born
> so maybe the problem was created in 2.4.15 but showed up in 2.4.16 ...
> If someone has an explanation to this behaviour, i would be really happy
Of course.
The 2.4.15 filesystem corruption problem occurred
on shutdown. When you booted up into 2.4.16, the
filesystem was corrupt and you began to see the
strange symptoms. when you backtracked to 2.4.14
and did the fsck, the problems were corrected.
I'll bet $20 that 2.4.16 runs fine now as well.
cu
jjs
next prev parent reply other threads:[~2001-12-01 22:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-01 22:08 File system Corruption with 2.4.16 Charles-Edouard Ruault
2001-12-01 22:22 ` J Sloan [this message]
2001-12-01 22:34 ` Charles-Edouard Ruault
2001-12-01 23:47 ` Jeff Merkey
2001-12-01 23:54 ` J Sloan
2001-12-02 0:52 ` Jeff Merkey
2001-12-02 1:31 ` Stephane Jourdois
2001-12-02 2:58 ` Jeff Merkey
2001-12-02 4:54 ` Charles-Edouard Ruault
2001-12-02 6:00 ` Tom Vier
2001-12-02 6:27 ` Charles-Edouard Ruault
2001-12-02 6:03 ` J Sloan
[not found] ` <1007273541.408.5.camel@psuedomode>
2001-12-02 6:51 ` Charles-Edouard Ruault
2001-12-02 7:25 ` J Sloan
2001-12-02 12:03 ` Heinz Diehl
2001-12-02 18:11 ` Kenneth Johansson
2001-12-02 18:55 ` Rene Rebe
2001-12-02 6:08 ` J Sloan
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=3C09580F.5F323195@pobox.com \
--to=jjs@pobox.com \
--cc=ce@ruault.com \
--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