linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Matwey V. Kornilov" <matwey.kornilov@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: btrfs: obtain block checksums from user space
Date: Thu, 24 Sep 2015 21:06:32 +0300	[thread overview]
Message-ID: <mu1e38$io1$1@ger.gmane.org> (raw)


Hello,

I would like to read the list of the checksums for the specific file
stored onto btrfs filesystem. I think I could use the checksums in the
manner like rsync does, but safe both CPU (because csums are already
calculated for the file) and I/O (because I don't need to reread all the
file from the hard drive).

I've looked through linux kernel sources and not found appropriate ioctl
to do this. Frankly speaking, I've not found good documentations for all
available btrfs ioctls.


             reply	other threads:[~2015-09-24 18:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-24 18:06 Matwey V. Kornilov [this message]
2015-09-24 18:35 ` btrfs: obtain block checksums from user space Austin S Hemmelgarn
2015-09-24 18:48   ` Matwey V. Kornilov
2015-09-24 19:47     ` Austin S Hemmelgarn
2015-09-28 23:11     ` Calvin Walton
2015-09-28 23:16       ` Hugo Mills
2015-09-28 23:25         ` Calvin Walton
2015-10-01 16:59 ` David Sterba

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='mu1e38$io1$1@ger.gmane.org' \
    --to=matwey.kornilov@gmail.com \
    --cc=linux-btrfs@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).