From: Rene Rebe <rene.rebe@gmx.net>
To: Kenneth Johansson <ken@canit.se>
Cc: ce@ruault.com, stephane@tuxfinder.org, jmerkey@timpanogas.org,
jjs@pobox.com, linux-kernel@vger.kernel.org
Subject: Re: File system Corruption with 2.4.16
Date: Sun, 2 Dec 2001 19:55:05 +0100 [thread overview]
Message-ID: <20011202195505.57363019.rene.rebe@gmx.net> (raw)
In-Reply-To: <3C0A6ECF.82C34304@canit.se>
In-Reply-To: <3C0954D5.6AA3532B@ruault.com> <3C09580F.5F323195@pobox.com> <3C095B0B.7EA478C1@ruault.com> <003601c17ac2$7a8dec10$f5976dcf@nwfs> <3C096DB3.204CE41C@pobox.com> <001e01c17acb$a44b69c0$f5976dcf@nwfs> <20011202023145.A1628@emeraude.kwisatz.net> <3C09B3FA.61777E84@ruault.com> <3C0A6ECF.82C34304@canit.se>
On Sun, 02 Dec 2001 19:11:27 +0100
Kenneth Johansson <ken@canit.se> wrote:
> I had problems with symlinks also. This is what I know about it so far.
>
> I only get/got this problem on a server running 2.4.10 using reiserfs and when the
> files was used over NFS.
> Once it got itself into this state it is possible to create symlinks by hand but when
> untaring an archive 90% of all links was wrong. Doing the same on the server directly
> showed no problem.
>
> A reboot of the client did not help but rebooting the server did. I have since
> upgraded to 2.4.16 but only run for a few hours the last time needed many days to show
> this problem so it could still be there.
>
> A nice program to use is symlinks that shows all links that points to a file not
> existing
> symlinks -r . | egrep "^dangling"
This general NFS v3 sym-link bug was fixed in 2.4.11 or .12 it was "only" caused
by a non-zero terminated string ...
btw. my 2.4.16 file-server using ReiserFS on a soft-raid5 device of 3 IBM
IDE disks has not yet shown a corruption (but could be a bit faster ...).
server1:~ # cat /proc/version
Linux version 2.4.16 (root@server1.localnet) (gcc version 2.95.3 20010315 (release)) #2 Tue Nov 27 18:58:48 CET 2001
server1:~ # uptime
7:54pm up 3 days, 4:02, 1 user, load average: 0.01, 0.03, 0.00
[...]
k33p h4ck1n6
René
--
René Rebe (Registered Linux user: #248718 <http://counter.li.org>)
eMail: rene.rebe@gmx.net
rene@rocklinux.org
Homepage: http://www.tfh-berlin.de/~s712059/index.html
Anyone sending unwanted advertising e-mail to this address will be
charged $25 for network traffic and computing time. By extracting my
address from this message or its header, you agree to these terms.
next prev parent reply other threads:[~2001-12-02 18:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-01 22:08 Charles-Edouard Ruault
2001-12-01 22:22 ` J Sloan
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 [this message]
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=20011202195505.57363019.rene.rebe@gmx.net \
--to=rene.rebe@gmx.net \
--cc=ce@ruault.com \
--cc=jjs@pobox.com \
--cc=jmerkey@timpanogas.org \
--cc=ken@canit.se \
--cc=linux-kernel@vger.kernel.org \
--cc=stephane@tuxfinder.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®