mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Patrick Scharrenberg" <pittipatti@web.de>
To: "Andreas Dilger" <adilger@turbolabs.com>
Cc: <linux-kernel@vger.kernel.org>, <ext2-devel@lists.sourceforge.net>
Subject: Re: 2.4.17 strange ext2 error
Date: Fri, 18 Jan 2002 01:49:05 +0100	[thread overview]
Message-ID: <003201c19fb9$ee32b030$fd358286@koenigsnet.rwthaachen.de> (raw)
In-Reply-To: <006701c19f97$5531f520$fd358286@koenigsnet.rwthaachen.de> <20020117141853.I29178@lynx.adilger.int>

Hi,

> On Jan 17, 2002  21:40 +0100, Patrick Scharrenberg wrote:
> > yesterday I got a very strange ext2 error on my linux machine..
> > The system has a 5-disk raid-5-software-raid and on top of this there is
one
> > ext2 fs which was clean when mounted 1 week ago..
> >
> > kernel 2.4.17 (since 1 week)
> > before it was 2.4.10
>
> When you say it was "clean when mounted 1 week ago" does this mean that
you
> had run e2fsck on it at that time, or just that it did not report any
> errors when you mounted it?  Sometimes it is possible to have corruption
> in your fs for a while without noticing it if you don't run fsck on it.

I meant that I  had run fsck one week ago, because the filesystem was
corrupt (but this was my fault).
At that same time (but after the fsck) I decided to switch to kernel 2.4.17.
But this shouldn't cause such errors with file-loss...

I don't know if it is save for me to run 2.4.17. For now I switched back to
2.4.10.
Tomorrow I'll start an new backup of the data and then try again the.17.
If the error occurs again, I'll post again.... :-)

..patrick


      reply	other threads:[~2002-01-18  0:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-17 20:40 Patrick Scharrenberg
2002-01-17 21:18 ` Andreas Dilger
2002-01-18  0:49   ` Patrick Scharrenberg [this message]

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='003201c19fb9$ee32b030$fd358286@koenigsnet.rwthaachen.de' \
    --to=pittipatti@web.de \
    --cc=adilger@turbolabs.com \
    --cc=ext2-devel@lists.sourceforge.net \
    --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®