From: Andreas Philipp <philipp.andreas@gmail.com>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: strange filefrag output on btrfs
Date: Mon, 13 Jun 2011 17:16:42 +0200 [thread overview]
Message-ID: <4DF629DA.4050300@gmail.com> (raw)
In-Reply-To: <20110613115018.GT12709@twin.jikos.cz>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 13.06.2011 13:50, David Sterba wrote:
> On Sat, Jun 11, 2011 at 05:39:15PM +0200, Andreas Philipp wrote:
>> On one of my btrfs volumes I see a strange output from filefrag when
>> run against a particular large (~8GB) file. filefrag and filefrag -v
>> give me a different number of extents, see below.
>>
>> aph@thor /mnt/nutshell $ sudo filefrag -v funtoo.img | grep extents
>> funtoo.img: 2624 extents found
>> aph@thor /mnt/nutshell $ sudo filefrag funtoo.img | grep extents
>> funtoo.img: 2653 extents found
>
> is the file open and being written to? did you run sync before the first
> command?
The file is not open. Yes, I have run sync before the first command.
Now, I tested again with a copy of file but the results is more or
less the same.
aph@thor /mnt/nutshell $ cp funtoo.img funtoo.1.img
aph@thor /mnt/nutshell $ sync
aph@thor /mnt/nutshell $ sudo filefrag -v funtoo.img funtoo.1.img |
grep extents
funtoo.img: 2624 extents found
funtoo.1.img: 57 extents found
aph@thor /mnt/nutshell $ sudo filefrag funtoo.img funtoo.1.img | grep
extents
funtoo.img: 2653 extents found
funtoo.1.img: 311 extents found
Thanks,
Andreas
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQIcBAEBAgAGBQJN9inZAAoJEJIcBJ3+XkgiADgP/1+B26+vvEhb2cFy64gCh9c1
eeJJXgZgQsMkq4ScTwmdgBkG49XtFRao+IAJLT8NEEYfWK2s/e7COK5KvjqHQP6T
Z64TKo/SKD3YaskszZEO30fM/A9pXcsDDRaCgOXJosCjRfl2vNyxvSMjnRRGEGGL
F4qI9sr9pkZrqbzwIrhPFBm1etkwMOOrXyqByg/VQoNxTts6xZ9hz0l42qOhrjXW
EZ1zLRrDqd0HTBPmrkntG4yACBW4/eJf0vPPn7cNRFf1a6ts9UTAgEOkobgP4tho
D+mGle5bPElyB72tcQ2jutk9+qr89VrUjrNHNHU3QAI9ZtvWLeHIS1P2PkiXk/s2
xQKL83V8QGoeK8BQTB2exMf7cBrgoVs4IfTcXaQyperFRFTYtjQ78J8p2iPvwTKY
6/4LkHkIEPJO3IZ81TFv1Vm5wefGqMWnpTRgvzLv52UlbNEkdcvdNM5IWGiIhFD6
cVQohZuHaTidhn2ancBVd3qE3oYMiBQknvKG39seUw8zTRixz7Ac+/uF7kcQSP6U
4RatjRADGN99Kt4ydwpZbIBiDQxttR+Js/sv8E8skqll96LeT+DVzMh2JRx+iy93
eatIlrTIgoPfi3Oo+NUXczMfamYfG7UcVhBUxDlQUTtKPAhPHmXvE9pkjqIJ5sxD
3mkSkEZ6ZXGujyIPXnfQ
=Yx0a
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2011-06-13 15:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-11 15:39 strange filefrag output on btrfs Andreas Philipp
2011-06-13 11:50 ` David Sterba
2011-06-13 15:16 ` Andreas Philipp [this message]
2011-06-14 2:54 ` Li Zefan
2011-06-14 7:11 ` Andreas Philipp
2011-06-14 7:52 ` Chris Samuel
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=4DF629DA.4050300@gmail.com \
--to=philipp.andreas@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).