Transactions in JBD2 proc

Transactions in JBD2 proc

[John R Nelson]

hi,
does the 3640 indicate that there have have 3640 journal writes to this ext4 parition since my computer has been up?

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

Re: Transactions in JBD2 proc

[Jan Kara]

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