Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Fwd: Re: Bug#808265: e2fsprogs: support btrfs compression in filefrag
Date: Sun, 20 Dec 2015 09:00:14 +0000 (UTC)	[thread overview]
Message-ID: <pan$7ef4e$d027fedc$245dafe8$58265d51@cox.net> (raw)
In-Reply-To: 1450483255.6251.16.camel@scientia.net

Christoph Anton Mitterer posted on Sat, 19 Dec 2015 01:00:55 +0100 as
excerpted:

> How, exactly, do you propose that filefrag understand this?  It is
> getting the information from the fiemap ioctl:
> 
> https://www.kernel.org/doc/Documentation/filesystems/fiemap.txt
> 
> and the problem is that fiemap returns the logical length of the extent,
> but not the *physical* length of the extent.  So this is why the
> filefrag is show what appears to be overlapping extents:


Thanks.  The devs might have known that, but you definitely just expanded 
my own knowledge and understanding of the subject.  (I had tried to make 
sense of filefrag -v and couldn't, here.  After reading your relay of 
Ted's reply, the output makes /much/ better sense to me! =:^)

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman


      reply	other threads:[~2015-12-20  9:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20151218232521.GB16904@thunk.org>
2015-12-19  0:00 ` Fwd: Re: Bug#808265: e2fsprogs: support btrfs compression in filefrag Christoph Anton Mitterer
2015-12-20  9:00   ` Duncan [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='pan$7ef4e$d027fedc$245dafe8$58265d51@cox.net' \
    --to=1i5t5.duncan@cox.net \
    --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