All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Vier <tmv5@home.com>
To: linux-kernel@vger.kernel.org
Subject: Re: File system Corruption with 2.4.16
Date: Sun, 2 Dec 2001 01:00:59 -0500	[thread overview]
Message-ID: <20011202010059.A9744@zero> (raw)
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>
In-Reply-To: <3C09B3FA.61777E84@ruault.com>; from ce@ruault.com on Sat, Dec 01, 2001 at 08:54:18PM -0800

On Sat, Dec 01, 2001 at 08:54:18PM -0800, Charles-Edouard Ruault wrote:
> The symlink problem you're reporting is exactly what i've been experiencing among
> other things ...
> on both systems i had multiple ext2 partitions and one reseirfs partition.

are you seeing corruption on the reiserfs? have you run reiserfsck?

-- 
Tom Vier <tmv5@home.com>
DSA Key id 0x27371A2C

  reply	other threads:[~2001-12-02  6:01 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
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 [this message]
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=20011202010059.A9744@zero \
    --to=tmv5@home.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 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.