From: Alex Riesen <fork0@users.sourceforge.net>
To: Oleg Drokin <green@namesys.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [reiserfs-dev] 2.5.4-pre1: zero-filled files reiserfs
Date: Tue, 12 Feb 2002 20:33:23 +0100 [thread overview]
Message-ID: <20020212203323.A1685@steel> (raw)
In-Reply-To: <20020211172747.A1815@namesys.com> <Pine.LNX.4.44.0202121753360.15594-100000@Expansa.sns.it> <20020212200124.A2267@namesys.com>
In-Reply-To: <20020212200124.A2267@namesys.com>
On Tue, Feb 12, 2002 at 08:01:24PM +0300, Oleg Drokin wrote:
> Hello!
>
> What kind of corruption? Can we look at corrupted file if there is something
> unusual?
> What Linux Distribution do you run?
i have my own system (but with sysVinit), and am somewhat sure about unmounts.
> You can check cleanness by looking into kernel messages.
> If there is "replaying journal" message - umount was not clean.
I've had the "replaying journal" after "machine check exception".
But after this crash the filesystem was perfect. The zerofiles was before...
>
> Bye,
> Oleg
> On Tue, Feb 12, 2002 at 05:55:54PM +0100, Luigi Genoni wrote:
> > Sorry but I got a corrupted file also with 2.5.4. I could see it after the
> > reboot to 2.4.17. It was /etc/exports and it was OK since i edited it
> > running 2.5.4, and It was readable by exportfs, so it corrupted at reboot.
> >
> > The reboot was clean, of course. Maybe wrong umount?
-alex
next prev parent reply other threads:[~2002-02-12 19:33 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-07 7:23 2.5.4-pre1: zero-filled files resiserfs Alex Riesen
2002-02-07 7:44 ` [reiserfs-dev] " Oleg Drokin
2002-02-07 22:02 ` Alex Riesen
2002-02-08 5:51 ` Oleg Drokin
2002-02-08 6:34 ` Oleg Drokin
2002-02-08 22:07 ` [reiserfs-dev] 2.5.4-pre1: zero-filled files reiserfs Alex Riesen
2002-02-11 5:51 ` Oleg Drokin
[not found] ` <Pine.LNX.4.44.0202111247270.21009-100000@Expansa.sns.it>
2002-02-11 12:17 ` Alex Riesen
2002-02-11 13:09 ` Oleg Drokin
[not found] ` <20020211141422.A16832@steel>
[not found] ` <20020211162743.A1282@namesys.com>
2002-02-11 14:03 ` Alex Riesen
2002-02-11 14:23 ` Luigi Genoni
2002-02-11 14:27 ` Oleg Drokin
2002-02-11 19:19 ` Luigi Genoni
2002-02-12 16:55 ` Luigi Genoni
2002-02-12 17:01 ` Oleg Drokin
2002-02-12 17:13 ` Luigi Genoni
2002-02-13 5:56 ` Oleg Drokin
2002-02-13 11:11 ` Luigi Genoni
2002-02-13 13:08 ` Oleg Drokin
2002-02-13 17:15 ` Luigi Genoni
2002-02-14 5:50 ` Oleg Drokin
2002-02-14 9:57 ` reiserfs oops with 2.5.5-pre1 (was: [reiserfs-dev] 2.5.4-pre1:)zero-filled " Luigi Genoni
2002-02-14 10:01 ` Oleg Drokin
2002-02-13 20:01 ` [reiserfs-dev] 2.5.4-pre1: zero-filled " Alex Riesen
2002-02-14 5:46 ` Oleg Drokin
2002-02-12 19:33 ` Alex Riesen [this message]
2002-02-11 14:20 ` Luigi Genoni
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=20020212203323.A1685@steel \
--to=fork0@users.sourceforge.net \
--cc=green@namesys.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