All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vince <fuzzy77@free.fr>
To: reiserfs-list@namesys.com
Subject: Re: Linux 2.4 -> 2.6 migration
Date: Fri, 07 Nov 2003 18:10:57 +0100	[thread overview]
Message-ID: <3FABD221.2010805@free.fr> (raw)
In-Reply-To: <m3k76c9m5a.fsf@toyland.sauerland.de>

Sebastian Kaps wrote:

> 
> The problem is not that newly written data is lost but that files
> suddenly have contents that belong to other files. I could live with the
> loss of unsaved data but for example I hate it when my window manager
> configuration is wrecked because contents that would belong to
> /var/log/messages appear in its config files. I've never had this with
> ext2 but quite a few times with ReiserFS.

Same here, and I couldn't agree more. I've had several bad corruption in 
my config files and logs happening because of this particular - and way 
too common - reiserfs behaviour...   :-/

>>If you want your data to be consistent in such cases you need to apply
>>Chris Mason's data logging patches, or use the SuSE Linux kernel.
>>See http://ftp.suse.com/pub/people/mason

On the same topic : does anybody know if there is a 2.6 version of these 
patches available somewhere ? (or else if a 2.6 port of those is planned 
in the short term ?)

Vincent


  reply	other threads:[~2003-11-07 17:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-07 13:39 Linux 2.4 -> 2.6 migration Sebastian Kaps
2003-11-07 15:29 ` Eric Whiting
     [not found] ` <3FABA80A.1090608@gmx.net>
2003-11-07 16:30   ` Sebastian Kaps
2003-11-07 17:10     ` Vince [this message]
     [not found] ` <20031107160935.3f02f334.pegasus@nerv.eu.org>
2003-11-07 16:33   ` Sebastian Kaps
2003-11-08  7:09   ` Soeren Sonnenburg
2003-11-08  4:08 ` Quinn Harris
2003-11-08 10:11 ` Alex Zarochentsev
2003-11-08 11:09   ` Vitaly Fertman
2003-11-08 12:40   ` Sebastian Kaps
2003-11-08 12:21 ` Matthias Andree
     [not found] ` <200311072107.50957.>
2003-11-08 12:32   ` Sebastian Kaps
2003-11-09  5:45   ` Alejandro Sanchez Acosta
2003-11-08 17:05     ` Marcelo Pacheco

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=3FABD221.2010805@free.fr \
    --to=fuzzy77@free.fr \
    --cc=reiserfs-list@namesys.com \
    /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.