On the call, we talked briefly about trying to get some access to high
speed SSD's for btrfs testing. I did not see online prices for STEC
which is one high end part we mentioned, but I did see that Rocketdisk
has 2.5 & 3.5 inch S-ATA drives that claim 19,000 IOPS.
The affordable ones (say $
Ok, cool. If the torture suite is a bunch of scripts, that is probably
something I can help with. I don't know what's the contribute policy
for this project, but if contributors are welcome I would like to
start a wiki page to gather test suite ideas, and I'd start writing
scripts to execute the te
On Wed, 2008-07-16 at 15:41 +0800, Yan Zheng wrote:
> Hello,
>
> Yesterday, I realized the algorithm for nodatacow is broken, it can't
> reliably detect whether a given extent is referenced by only one
> snapshot.
I had to change around nodatacow back in May because it was definitely
broken in th
On Wed, Jul 16, 2008 at 12:06:00PM +0300, Ahmed Kamal wrote:
> Hi Team,
> I have been following the btrfs project since Chris announced it last
> year. I am happy to see v1.0 is planned in Q4. This is awesome, we can
> finally get something like ZFS on Linux. The project pace is nothing
> short of
On Sat, Jun 14, 2008 at 2:22 PM, Jeff Mahoney <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Miguel Sousa Filipe wrote:
>> Hi all!
>>
>> On Fri, Jun 13, 2008 at 9:09 PM, Jeff Mahoney <[EMAIL PROTECTED]> wrote:
>>> This patch converts the btrfs-progs build system f
Hi Team,
I have been following the btrfs project since Chris announced it last
year. I am happy to see v1.0 is planned in Q4. This is awesome, we can
finally get something like ZFS on Linux. The project pace is nothing
short of amazing. Thank you :)
I notice the plans contain "QA suite".
I would l
Hello,
Yesterday, I realized the algorithm for nodatacow is broken, it can't
reliably detect whether a given extent is referenced by only one
snapshot.
Let me use the attached picture to describe the issue.
Figure (1) shows the initial tree structure. there is only one fs tree A.
Figure (2) sho
