Just wondering how do I measure the compression used in btrfs?
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
There seems to be some issue over changing the names of the device
that a btrfs filesystem lives on:
# lvcreate scratch -n fstest -L 2G
Logical volume fstest created
# mkfs -t btrfs /dev/scratch/fstest
WARNING! - Btrfs v0.18-ge3b0f66 IS EXPERIMENTAL
WARNING! - see
I am continuing to do runs to provide more data on the random write
issues with btrfs. I have just posted 2 sets of runs here:
http://btrfs.boxacle.net/repository/raid/longrun/
these are on a pull of the btrfs-unstable experimental branch from 4/3.
These are 100 minute runs of the 128 thread
On Mon, Apr 06, 2009 at 05:01:11PM -0500, Steven Pratt wrote:
I am continuing to do runs to provide more data on the random write
issues with btrfs. I have just posted 2 sets of runs here:
http://btrfs.boxacle.net/repository/raid/longrun/
these are on a pull of the btrfs-unstable
On Mon, Apr 06, 2009 at 06:19:58PM -0400, Josef Bacik wrote:
On Mon, Apr 06, 2009 at 05:01:11PM -0500, Steven Pratt wrote:
I am continuing to do runs to provide more data on the random write
issues with btrfs. I have just posted 2 sets of runs here:
On Mon, 2009-04-06 at 17:01 -0500, Steven Pratt wrote:
I am continuing to do runs to provide more data on the random write
issues with btrfs. I have just posted 2 sets of runs here:
http://btrfs.boxacle.net/repository/raid/longrun/
these are on a pull of the btrfs-unstable experimental