Hi,
Ran into a problem stress testing my btrfs truncate conversion attempt...
Unfortunately it was an existing btrfs problem. Fortunately I think I
was able to fix it.
Thanks,
Nick
--
btrfs: fix inode rbtree corruption
Node may not be inserted over existing node. This causes inode tree
corrupti
Hi Chris,
Don't know if this is a known issue, but I have btrfs (after my previous
inode_tree fixup patch) failing fsx-linux in Linus's current git tree.
This makes it a bit hard for me to test my btrfs truncate conversion patch
unfortunately, though it does seem pretty stable so I will probably
On Tue, Aug 18, 2009 at 07:26:41PM +0200, Nick Piggin wrote:
> Hi Chris,
>
> Don't know if this is a known issue, but I have btrfs (after my previous
> inode_tree fixup patch) failing fsx-linux in Linus's current git tree.
>
> This makes it a bit hard for me to test my btrfs truncate conversion p
2009/8/19 Nick Piggin :
> Hi,
>
> Ran into a problem stress testing my btrfs truncate conversion attempt...
> Unfortunately it was an existing btrfs problem. Fortunately I think I
> was able to fix it.
>
> Thanks,
> Nick
>
> --
> btrfs: fix inode rbtree corruption
>
> Node may not be inserted over
On Wed, Aug 19 2009, Yan, Zheng wrote:
> 2009/8/19 Nick Piggin :
> > Hi,
> >
> > Ran into a problem stress testing my btrfs truncate conversion attempt...
> > Unfortunately it was an existing btrfs problem. Fortunately I think I
> > was able to fix it.
> >
> > Thanks,
> > Nick
> >
> > --
> > btrfs
On Mon, Aug 17 2009, Mark Lord wrote:
> Kay Sievers wrote:
>> On Mon, Aug 17, 2009 at 22:47, Mark Lord wrote:
>>> Chris / list,
>>>
>>> stat(2) seems to return invalid major/minor device info
>>> for btrfs filesystems.
>>>
>>> Why? Is this a bug?
>>
>> This is not invalid and not a bug. It's a sup