From: Daniel Elstner <daniel.elstner@gmx.net>
To: Chris Mason <mason@suse.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: reiserfs+lndir problem [was: 2.4.4 SMP: spurious EOVERFLOW "Value too large for defined data type"]
Date: Wed, 2 May 2001 00:41:52 +0200 [thread overview]
Message-ID: <20010502004152.23a0751b.daniel@master.daniel.homenet> (raw)
In-Reply-To: <1026200000.988679027@tiny>
In-Reply-To: <20010430225557.3f28d1b0.daniel@master.daniel.homenet> <1026200000.988679027@tiny>
Hi,
On Mon, 30 Apr 2001 21:03:47 -0400 Chris Mason <mason@suse.com> wrote:
> > Apparently it's a reiserfs/symlink problem.
> > I tried doing the lndir on an ext2 partition, sources still
> > on reiserfs. And it worked just fine!
>
> Neat, thanks for the extra details. Does that mean you can consistently
> repeat on reiserfs now? What happens when you do the lndir on reiserfs and
> diff the directories?
I just played around a bit with the following results:
sources on reiserfs, lndir on reiserfs -> make fails, diff ok
sources on reiserfs, lndir on ext2 -> make ok
sources on ext2, lndir on reiserfs -> make fails, diff ok
Doing the diff against a second copy of the tree shows no errors, too.
Always the same behaviour: You have to run lndir at least twice to
get the error. If the link tree was already set up after a boot, the
error occurs only after rm + lndir + rm + lndir.
There's a strange way to get things working just like after a reboot.
After diff'ing the link tree with the 2nd copy (both on reiserfs),
make World won't fail - at least once.
I also tried in the link tree:
find ! -type d -exec cat '{}' \; >/dev/null
And it seems to have the same effect as the diff.
> Any useful messages in /var/log/messages?
Nope, not any single message (except the usual ones).
The error on shutdown (when umounting /proc) appeared once again,
with the the same error message. Though I have no clue how that
could be related to reiserfs.
Two missed details: the reiserfs partion exists on a software
raid0 device. I configured glibc-2.2.3 with --enable-kernel=2.4.1.
Shall I try moving back to glibc-2.2.2 / configuring for lower kernel?
-- Daniel
next prev parent reply other threads:[~2001-05-01 22:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-30 18:56 2.4.4 SMP: spurious EOVERFLOW "Value too large for defined data type" Daniel Elstner
2001-04-30 20:09 ` Daniel Elstner
2001-04-30 20:55 ` reiserfs+lndir problem [was: 2.4.4 SMP: spurious EOVERFLOW "Value too large for defined data type"] Daniel Elstner
2001-05-01 1:03 ` Chris Mason
2001-05-01 22:41 ` Daniel Elstner [this message]
2001-05-01 22:48 ` Chris Mason
2001-05-02 20:41 ` Daniel Elstner
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=20010502004152.23a0751b.daniel@master.daniel.homenet \
--to=daniel.elstner@gmx.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mason@suse.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.