public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: Emmanuel Varagnat-AEV010 <Emmanuel_Varagnat-AEV010@email.mot.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: ReiserFS file corruption
Date: Tue, 07 Aug 2001 23:02:19 +0400	[thread overview]
Message-ID: <3B703B3B.F02DB414@namesys.com> (raw)
In-Reply-To: <3B6E84A1.1A13969@crm.mot.com>

Emmanuel Varagnat wrote:
> 
> Today, I crashed the kernel and after reboot the source file
> I was working on, was completly unreadable. The size indicated
> by 'ls' seems to be good but with bad data.
> 
> Is this behavior normal (because the FS seems correct) ?
> The worst I hoped is loosing the last save, but not everything.
> 
> Must I patch to a newer version ?
> I'm using a 2.4.3 version.
> 
> Thanks
> 
> -Manu
> 
> PS: Finally I greped the partition and recover my file.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

If your editor rewrites the entire file with every small change (and it probably
does), then if you crash at the wrong moment you can corrupt the entire file. 
If you use emacs or vi, it keeps a backup copy until the write is synced to disk
successfully.

You should definitely use 2.4.7, it is much better.

Hans

      parent reply	other threads:[~2001-08-07 19:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-06 11:50 ReiserFS file corruption Emmanuel Varagnat
2001-08-06 12:04 ` Rasmus Bøg Hansen
2001-08-06 12:13 ` bvermeul
2001-08-06 12:14 ` Arjan van de Ven
2001-08-07 18:28   ` Troy Benjegerdes
2001-08-07 19:02 ` Hans Reiser [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=3B703B3B.F02DB414@namesys.com \
    --to=reiser@namesys.com \
    --cc=Emmanuel_Varagnat-AEV010@email.mot.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