public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Marc Lehmann <schmorp@schmorp.de>
To: 924307@bugs.debian.org
Subject: Bug#924307: xfsprogs: xfs_fsr needlessly defragments fully defragmented files
Date: Sun, 27 Nov 2022 18:43:47 +0100	[thread overview]
Message-ID: <Y4Oh0y9gHZ77iwl/@schmorp.de> (raw)
In-Reply-To: 155230535650.755.1614381112413278305.reportbug@cerebro.laendle

Seems that current versions of e2fsprogs have improved filefrag, which now
reports one "extent" for these files, even though it has two extents:

   File size of 014798 is 87556096 (21376 blocks of 4096 bytes)
    ext:     logical_offset:        physical_offset: length:   expected: flags:
      0:        0..   21373:  352550127.. 352571500:  21374:            
      1:    21374..   21375:  352571501.. 352571502:      2:             last,unwritten,eof
   014798: 1 extent found

not quite correct, but arguably more useful (2 _extents_ vs. 1
_fragment_, just a wording issue).

xfs_fsr still considers these files fragmented, though:

   014798
   extents before:2 after:1 DONE 014798

-- 

           reply	other threads:[~2022-11-27 18:30 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <155230535650.755.1614381112413278305.reportbug@cerebro.laendle>]

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=Y4Oh0y9gHZ77iwl/@schmorp.de \
    --to=schmorp@schmorp.de \
    --cc=924307@bugs.debian.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