All of lore.kernel.org
 help / color / mirror / Atom feed
From: dexen deVries <dexen.devries-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: nilfs2 doesn't garbage collect checkpoints for me
Date: Wed, 1 Jun 2011 21:19:25 +0200	[thread overview]
Message-ID: <201106012119.26289.dexen.devries@gmail.com> (raw)
In-Reply-To: <BANLkTinsZZeRDmQR8sAWrqUP1N4UK5ktAA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

Hi again, Dima,


On Wednesday 01 June 2011 20:21:07 you wrote:
> Thanks for the tip, bkltrace seems to give me what I want and much more!

yay :)


dunno if that'll help you at all, but:
I've been observing some process writing to NILFS2 to-day. It was issuing one 
(filesystem) transaction every couple seconds. About 250kb was written to the 
drive (of both data and metadata) -- and the interesting thing is, it was 
written as one I/O operation (as reported by iostat).

Depending on configuration and properties of your storage (possibly including 
multiple-sector i/o configuration, see hdparm's `-m' option), a (filesystem-
level) transaction on to NILFS2 may issue just one drive-level operation.

As opposed to other filesystems, which keep data and various kinds of metadataa 
all separate.

Of course later on the GC will kick in, but it also writes large chunks at 
once, rather than spreading them all over the storage.



Cheers,
-- 
dexen deVries

``One can't proceed from the informal to the formal by formal means.''
--
To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      parent reply	other threads:[~2011-06-01 19:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-26 18:11 nilfs2 doesn't garbage collect checkpoints for me Dima Tisnek
     [not found] ` <BANLkTim4BBKwFJUzbnsKw0_Ru2k8ZW3MYw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-05-26 18:32   ` dexen deVries
     [not found]     ` <201105262032.54257.dexen.devries-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-05-26 20:24       ` Dima Tisnek
     [not found]         ` <BANLkTimNm6QcNOmc1Gwp2K+SVKoRV8+8Cg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-05-27  4:38           ` Ryusuke Konishi
     [not found]             ` <20110527.133803.215389018.ryusuke-sG5X7nlA6pw@public.gmane.org>
2011-05-31 22:08               ` Dima Tisnek
     [not found]                 ` <BANLkTinnpFyrxeO2_DF5gXLgas2WLdqw4Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-06-01  8:03                   ` dexen deVries
     [not found]                     ` <201106011003.24656.dexen.devries-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-06-01 17:32                       ` Dima Tisnek
     [not found]                         ` <BANLkTimhLPM3TU1uw10Ub5t-GEW_s-B_tQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-06-01 17:34                           ` dexen deVries
     [not found]                             ` <201106011934.30725.dexen.devries-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-06-01 18:21                               ` Dima Tisnek
     [not found]                                 ` <BANLkTinsZZeRDmQR8sAWrqUP1N4UK5ktAA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-06-01 19:19                                   ` dexen deVries [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=201106012119.26289.dexen.devries@gmail.com \
    --to=dexen.devries-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 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.