All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: Andreas Dilger <adilger@clusterfs.com>
Cc: Zygo Blaxell <eazgwmir@umail.furryterror.org>, reiserfs-list@namesys.com
Subject: Re: reiserfs on removable media
Date: Wed, 02 Jul 2003 22:53:39 +0400	[thread overview]
Message-ID: <3F032A33.3050303@namesys.com> (raw)
In-Reply-To: <20030702124544.Z7414@schatzie.adilger.int>

Andreas Dilger wrote:

>On Jul 02, 2003  14:23 -0400, Zygo Blaxell wrote:
>  
>
>>Two reiserfs improvements come to mind:
>>
>>- There is a tendency for files that were being grown at crash time to
>>contain invalid data.  It seems that the inodes are being updated before
>>the data blocks they refer to are written.  It would be nice if the inode
>>writes were deferred (or at least made invisible) until after the data
>>blocks were written.  I'd rather lose my data than possibly have random
>>garbage masquerading as my data.
>>    
>>
>
>This is called ordered data mode, and exists on ext3 and also reiserfs with
>Chris Mason's patches.  Under normal usage it shouldn't change performance
>compared to writeback data mode (which is what reiserfs does by default).
>
It had some impact, I forget exactly how much, maybe Chris can 
resuscitate his benchmark of it?

Remind me about removable media around January, and we'll write some 
code for reiser4 to make it more graceful for it (somehow prompt the 
user to insert disk, etc.)

-- 
Hans



  reply	other threads:[~2003-07-02 18:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-02 18:23 reiserfs on removable media Zygo Blaxell
2003-07-02 18:45 ` Andreas Dilger
2003-07-02 18:53   ` Hans Reiser [this message]
2003-07-02 18:59     ` Chris Mason
2003-07-02 19:08       ` Dieter Nützel
2003-07-02 19:17         ` Chris Mason
2003-07-02 20:19     ` Zygo Blaxell
2003-07-03  2:02   ` Recipe for reiserfs oops on "removable" disks (was: Re: reiserfs on removable media) Zygo Blaxell
2003-07-03  6:08 ` reiserfs on removable media Oleg Drokin

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=3F032A33.3050303@namesys.com \
    --to=reiser@namesys.com \
    --cc=adilger@clusterfs.com \
    --cc=eazgwmir@umail.furryterror.org \
    --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.