From: Sean Bartell <wingedtachikoma@gmail.com>
To: Nathan Caza <mastercactapus@gmail.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: crc32c
Date: Mon, 11 Oct 2010 11:09:33 -0400 [thread overview]
Message-ID: <20101011150933.GA3060@lelouch.nomadic.ncsu.edu> (raw)
In-Reply-To: <AANLkTi=8xYEQ=pwo5faCMqD7gV=OLJxXTmfKvcDvp5i-@mail.gmail.com>
On Mon, Oct 11, 2010 at 03:47:58AM -0500, Nathan Caza wrote:
> I think I'm on the verge of getting all my data back; the only missing
> piece is to recalculate the crc checksum of my altered superblock and
> I'm having trouble finding the correct function/method; the data I am
> checksumming is (based on the sheet) 0x20 (directly after the
> checksum) to 0x32b + n (226 bytes); if im doing something wrong let me
> know; or if theres a quick/dirty way to get the right checksum
The checksum seems to be from 0x20 to 0x1000.
prev parent reply other threads:[~2010-10-11 15:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-11 8:47 crc32c Nathan Caza
2010-10-11 15:09 ` Sean Bartell [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=20101011150933.GA3060@lelouch.nomadic.ncsu.edu \
--to=wingedtachikoma@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=mastercactapus@gmail.com \
/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).