public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Oleg Drokin <green@namesys.com>
To: Alex Riesen <fork0@users.sourceforge.net>
Cc: Luigi Genoni <kernel@Expansa.sns.it>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [reiserfs-dev] 2.5.4-pre1: zero-filled files reiserfs
Date: Mon, 11 Feb 2002 16:09:48 +0300	[thread overview]
Message-ID: <20020211160948.B7863@namesys.com> (raw)
In-Reply-To: <20020211085140.B27189@namesys.com> <Pine.LNX.4.44.0202111247270.21009-100000@Expansa.sns.it> <20020211131713.A8614@steel>
In-Reply-To: <20020211131713.A8614@steel>

Hello!

On Mon, Feb 11, 2002 at 01:17:13PM +0100, Alex Riesen wrote:
> > I got the same with 2.5.4-pre1 on a  ATA66 disk,
> > chipset i810, PentiumIII with 256 MBRAM,
> > and then on Athlon 1300 Mhz, scsi disk, adaptec
> > 2940UW, 512MB RAM.
> > 
> > I saw then just after a reboot.
> > Those file has been opened three or four days before the reboot expect of
> > .history.
> > I got no messages, and, that is the most interesting thing, this
> > corruption was just for text file. I also edited some binary file with
> > kexedit and them have not been corrupted after the reboot.
Hm. Strange. This message have not appeared in my mailbox for some
reason.
.history may be corrupted if your partition was not unmounted properly
before reboot.

Bye,
    Oleg

  reply	other threads:[~2002-02-11 13:10 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 [this message]
     [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
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=20020211160948.B7863@namesys.com \
    --to=green@namesys.com \
    --cc=fork0@users.sourceforge.net \
    --cc=kernel@Expansa.sns.it \
    --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