public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Girish Shilamkar <girish@clusterfs.com>
To: linux-ext4@vger.kernel.org
Cc: Andreas Dilger <adilger@clusterfs.com>
Subject: Re: [Patch 0/2] Journal Checksums
Date: Wed, 30 May 2007 16:06:40 +0530	[thread overview]
Message-ID: <1180521400.13497.1.camel@alpha.linsyssoft.com> (raw)
In-Reply-To: <1180520892.3787.43.camel@alpha.linsyssoft.com>

Hi,
	I forgot mention, this patch is spinoff of patch originally written by
Vijayan Prabhakaran.

Thanks & Regards.
Girish

On Wed, 2007-05-30 at 16:01 +0530, Girish Shilamkar wrote:
> Hi,
>  	The following patch set adds journal checksumming support for linux
> kernel and e2fsprogs. 
> 
> Two new flags have been added i.e 
> JBD2_FEATURE_INCOMPAT_ASYNC_COMMIT and JBD2_FEATURE_COMPAT_CHECKSUM.
> 
> _CHECKSUM flag indicates that the commit block contains the checksum for
> the blocks described the the descriptor blocks.
> Due to checksums, writing of the commit record no longer needs to be
> synchronous, this behavior is controlled using _ASYNC_COMMIT flag. Older
> kernels/e2fsck should not be able to recover the journal with
> _ASYNC_COMMIT hence it is made incompat. 
> The commit header has been extended to hold the checksum along with the
> type of the checksum.
> 
> For recovery in pass scan checksums are verified to ensure the sanity
> and completeness(in case of _ASYNC_COMMIT) of every transaction.
> 
> Any suggestions/comments are welcome.
> 
> Thanks & Regards,
> Girish.
> 
> 
> 

      reply	other threads:[~2007-05-30 10:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-30 10:28 [Patch 0/2] Journal Checksums Girish Shilamkar
2007-05-30 10:36 ` Girish Shilamkar [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=1180521400.13497.1.camel@alpha.linsyssoft.com \
    --to=girish@clusterfs.com \
    --cc=adilger@clusterfs.com \
    --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