Algorithm for nodatacow is broken

2008-07-16 Thread Yan Zheng
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)

QA suite plans

2008-07-16 Thread Ahmed Kamal
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

Re: QA suite plans

2008-07-16 Thread Josef Bacik
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

Re: Algorithm for nodatacow is broken

2008-07-16 Thread Chris Mason
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 the