public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kalpak Shah <kalpak@linsyssoft.com>
To: Folkert van Heusden <folkert@vanheusden.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: statistics of filesystem-journal usage
Date: Fri, 11 May 2007 19:54:26 +0530	[thread overview]
Message-ID: <1178893466.6016.5.camel@garfield> (raw)
In-Reply-To: <20070511140004.GD6261@vanheusden.com>

On Fri, 2007-05-11 at 16:00 +0200, Folkert van Heusden wrote:
> Hi,
> 
> Maybe it is a nice idea to export statistics on the usage of a journal
> of a filesystem as well. That way one can more easy see if it would help
> to put a journal on an other harddisk.

There is a patch posted on linux-ext4 which maintains the journal
statistics such as transaction sizes and their lifetimes. These stats
are provided through procfs and can only be used with ext4 since ext2/3
still use the jbd layer.

You can see the patch here:
http://lists.openwall.net/linux-ext4/2007/04/02/6

- Kalpak.
> 
> 
> Folkert van Heusden
> 


      reply	other threads:[~2007-05-11 14:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-11 14:00 statistics of filesystem-journal usage Folkert van Heusden
2007-05-11 14:24 ` Kalpak Shah [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=1178893466.6016.5.camel@garfield \
    --to=kalpak@linsyssoft.com \
    --cc=folkert@vanheusden.com \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox