linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Carlos Maiolino <cmaiolino@redhat.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: "Darrick J. Wong" <darrick.wong@oracle.com>,
	Chris Murphy <lists@colorremedies.com>,
	xfs list <linux-xfs@vger.kernel.org>
Subject: Re: filefrag and reflink
Date: Thu, 19 Jul 2018 13:34:50 +0200	[thread overview]
Message-ID: <20180719113450.sbdlljklwkky7isv@odin.usersys.redhat.com> (raw)
In-Reply-To: <165c936c-7dc4-7336-3d7e-268ec6746b56@sandeen.net>

On Wed, Jul 18, 2018 at 01:27:40PM -0700, Eric Sandeen wrote:
> 
> 
> On 7/18/18 12:59 PM, Darrick J. Wong wrote:
> > On Wed, Jul 18, 2018 at 12:41:27PM -0600, Chris Murphy wrote:
> >> xfsprogs 4.17.0 mkfs with reflink=1
> >> kernel 4.17.6
> >>
> >> $ fallocate -l 1g tmp2
> >> $ cp --reflink tmp2 tmp3
> >> $ filefrag -v *
> >> Filesystem type is: 58465342
> >> File size of tmp2 is 1073741824 (262144 blocks of 4096 bytes)
> >>  ext:     logical_offset:        physical_offset: length:   expected: flags:
> >>    0:        0..  130136:         24..    130160: 130137:             unwritten
> >>    1:   130137..  260280:     131082..    261225: 130144:     130161: unwritten
> >>    2:   260281..  262143:     264714..    266576:   1863:     261226:
> >> last,unwritten,eof
> >> tmp2: 3 extents found
> >> File size of tmp3 is 1073741824 (262144 blocks of 4096 bytes)
> >> tmp3: 0 extents found
> >> [chris@f28s xfs]$
> >>
> >>
> >> Is this expected? When I do it on Btrfs, I see identical information
> >> for the two files after reflink copy, with flags "unwritten,shared".
> > 
> > Yes.  xfs doesn't share unwritten extents; what would be the point?
> > 
> > --D
> 
> <materializes somewhere on a US western interstate>
> 
> Seems a little weird that bare cp will create a written file full of
> zeros, while a cp --reflink will create a sparse file, though?

cp actually can have different behaviors when --reflink is specified, from the
manpage (formatting slightly modified):

"
By default, sparse SOURCE files are detected by a crude heuristic and the
corresponding DEST file is made sparse  as  well. That  is  the  behavior
selected  by  --sparse=auto.
Specify --sparse=always  to  create  a  sparse DEST file whenever the SOURCE
file contains a long enough sequence of zero bytes.  Use --sparse=never to
inhibit creation of sparse files.

When --reflink[=always] is specified, perform a lightweight copy,  where  the
data  blocks  are copied  only  when  modified.   If  this is not possible the
copy fails, or if --reflink=auto is specified, fall back to a standard copy.
"

> 
> -Eric
> --
> To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

-- 
Carlos

  parent reply	other threads:[~2018-07-19 12:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-18 18:41 filefrag and reflink Chris Murphy
2018-07-18 19:59 ` Darrick J. Wong
2018-07-18 20:27   ` Eric Sandeen
2018-07-18 20:47     ` Darrick J. Wong
2018-07-18 21:07       ` Eric Sandeen
2018-07-19  0:09         ` Darrick J. Wong
2018-07-19 11:45       ` Carlos Maiolino
2018-07-19 11:34     ` Carlos Maiolino [this message]
2018-07-19 14:39       ` Darrick J. Wong

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=20180719113450.sbdlljklwkky7isv@odin.usersys.redhat.com \
    --to=cmaiolino@redhat.com \
    --cc=darrick.wong@oracle.com \
    --cc=linux-xfs@vger.kernel.org \
    --cc=lists@colorremedies.com \
    --cc=sandeen@sandeen.net \
    /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).