linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: John R Nelson <jrnelson@bhcc.edu>
Cc: "linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
Subject: Re: Transactions in JBD2 proc
Date: Mon, 29 Oct 2012 19:24:09 +0100	[thread overview]
Message-ID: <20121029182409.GH18767@quack.suse.cz> (raw)
In-Reply-To: <4B9BD6EF1B194041BF688A9AAE347E37064B168BA039@mercury-stu.bhcc.dom>

On Mon 29-10-12 13:20:43, John R Nelson wrote:
> hi,
> does the 3640 indicate that there have have 3640 journal writes to this
> ext4 parition since my computer has been up?
  Well, it depends on what you call "journal write". There were 3640
trasactions to your ext4 partition. Each transaction can contain more
"logical" operations like file creation, file write, rename, ... Each
transaction also consists of more blocks. In your case there were 7 blocks
per transaction on average - which is rather small but I expect that's
because the filesystem is mostly idle.
	
								Honza
> 
> 3640 transaction, each up to 8192 blocks
> average: 
>   0ms waiting for transaction
>   2032ms running transaction
>   0ms transaction was being locked
>   0ms flushing data (in ordered mode)
>   52ms logging transaction
>   71647us average transaction commit time
>   316 handles per transaction
>   7 blocks per transaction
>   8 logged blocks per transaction
> 
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
-- 
Jan Kara <jack@suse.cz>
SUSE Labs, CR

      reply	other threads:[~2012-10-29 18:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-29 17:20 Transactions in JBD2 proc John R Nelson
2012-10-29 18:24 ` Jan Kara [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=20121029182409.GH18767@quack.suse.cz \
    --to=jack@suse.cz \
    --cc=jrnelson@bhcc.edu \
    --cc=linux-ext4@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;
as well as URLs for NNTP newsgroup(s).