reiserfs-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Łukasz Mierzwa" <prymitive@pcserwis.net>
To: David Masover <ninja@slaphack.com>,
	"reiserfs-list@namesys.com" <reiserfs-list@namesys.com>
Subject: Re: reiser4 resize
Date: Thu, 21 Sep 2006 09:52:13 +0200	[thread overview]
Message-ID: <op.tf7xhbxbd4os1z@localhost> (raw)
In-Reply-To: <45123F81.4040909@slaphack.com>

Dnia Thu, 21 Sep 2006 09:30:09 +0200, David Masover <ninja@slaphack.com>  
napisa³:

> On 9/20/06, £ukasz Mierzwa <prymitive@pcserwis.net> wrote:
>  It's been proven that flushes are doing much more job then they should.
> Not so long ago someone send a trace of block device io accesess during
> reiser4 work and someone anylized it and said that some files or parts of
> file where written over and over 200 times or so.
>  Wow.  I should go back and read that -- I assume this is being worked  
> on?

Well it was not a file but a block, but the effect is the same.

http://marc.theaimsgroup.com/?l=reiserfs&m=115488109712570&w=2

  parent reply	other threads:[~2006-09-21  7:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-19  1:12 reiser4 resize Jack Byer
2006-09-19 13:23 ` Vladimir V. Saveliev
2006-09-19 17:54   ` David Masover
2006-09-20  7:39     ` Alexey Polyakov
     [not found]       ` <op.tf52pansd4os1z@localhost>
2006-09-20  9:00         ` Alexey Polyakov
2006-09-21  7:30           ` David Masover
2006-09-21  7:49             ` Łukasz Mierzwa
2006-09-21  7:52             ` Łukasz Mierzwa [this message]
2006-09-21  7:48       ` David Masover
2006-09-20  1:09   ` Jack Byer
  -- strict thread matches above, loose matches on Subject: below --
2008-01-25 14:38 Reiser4 resize Oleg Osovitskiy
2008-01-30 20:40 ` Edward Shishkin
2008-03-02 22:39 No space left on rfs4 Christopher Sawtell
2008-03-03 20:59 ` Reiser4 resize John

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=op.tf7xhbxbd4os1z@localhost \
    --to=prymitive@pcserwis.net \
    --cc=ninja@slaphack.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).