All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@clusterfs.com>
To: Matt Stegman <matts@ksu.edu>
Cc: reiserfs-list@namesys.com
Subject: Re: reiser4 metas/bmap problem
Date: Wed, 28 Jul 2004 21:25:49 -0400	[thread overview]
Message-ID: <20040729012549.GE1439@schnapps.adilger.int> (raw)
In-Reply-To: <Pine.GSO.4.44L.0407281754290.11129-100000@unix2.cc.ksu.edu>

[-- Attachment #1: Type: text/plain, Size: 1490 bytes --]

On Jul 28, 2004  18:26 -0500, Matt Stegman wrote:
> I'm finally taking the time to start testing reiser4, and I'm running into
> something odd.  Some of the time, reiser4 doesn't report a file's blocks
> until I run 'sync'.  This shows up in metas/bmap as many blocks are
> reported as 0.
> 
> # dd if=/dev/zero of=/mnt/reiser4/file bs=1M count=50
> 50+0 records in
> 50+0 records out
> # chmod +x /mnt/reiser4/file
> # grep '^0$' /mnt/reiser4/file/metas/bmap | wc -l
> 1792
> # sleep 100
> # grep '^0$' /mnt/reiser4/file/metas/bmap | wc -l
> 1792
> # sync
> # grep '^0$' /mnt/reiser4/file/metas/bmap | wc -l
> 0
> 
> I tried waiting to see if it gets written out in the background
> asynchronously.  As you can see, it still shows up after a couple minutes,
> so it doesn't appear to get written until an actual 'sync' command is run.
> But it shows up inconsistently - many files don't show this.

I believe one of the speedups of reiser4 is that it doesn't actually write
data to disk for minutes at a time, vs. 5s or so for most other filesystems.

The ext3_bmap() function flushes all file data to disk when called, and it
would be prudent to do the same with reiser4, since bmap users tend to be
important and not speed critical (e.g. lilo) and failing to do so can mean
not booting later.

Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://members.shaw.ca/adilger/             http://members.shaw.ca/golinux/


[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-07-29  1:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-28 23:26 reiser4 metas/bmap problem Matt Stegman
2004-07-29  1:25 ` Andreas Dilger [this message]
2004-07-29  7:41   ` Hans Reiser
2004-07-29  7:48     ` Vladimir V. Saveliev
2004-07-30 18:37       ` Hans Reiser
2004-07-30 19:26         ` Andreas Dilger
2004-07-31 11:43         ` Vladimir V. Saveliev
2004-07-31 17:08           ` Christophe Saout
2004-08-01 12:18             ` Vladimir V. Saveliev
2004-07-29  8:07   ` Vladimir V. Saveliev
2004-07-30  2:30     ` daniel.poelzleithner
2004-07-30  2:42       ` Andreas Dilger

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=20040729012549.GE1439@schnapps.adilger.int \
    --to=adilger@clusterfs.com \
    --cc=matts@ksu.edu \
    --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.