-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 14.06.2011 04:54, Li Zefan wrote:
Andreas Philipp wrote:
-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
On 14/06/11 12:54, Li Zefan wrote:
There are two ways to calc the extent number, depending
on whether verbose option is turned on or not.
To me that's very counter intuitive!
Maybe another way to do that is to name those two values
differently and in verbose mode report them both so people
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
-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
Andreas Philipp wrote:
-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.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
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 |
