Hi,
all reported issues are fixed with the updated branch, thanks!
david
--
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
On Tue, Nov 01, 2011 at 08:56:15PM -0400, Chris Mason wrote:
> > xfstests/083 and 089 cause the following warnings. I've seen them before
> > when
> > testing josef/for-chris and josef/master branches (reported on irc).
>
> Ok, just a status update on my end. Josef and I have the block group
> w
On 11/01/2011 06:55 PM, Chris Mason wrote:
> On Tue, Nov 01, 2011 at 05:22:20PM +0800, Liu Bo wrote:
>> Hi,
>>
>> On 11/01/2011 10:49 AM, Chris Mason wrote:
>>> Hi everyone,
>>>
>>> I've pushed out a new integration branch, but it is not for general use.
>>>
>>> I'm still going through and hammeri
On Tue, Nov 01, 2011 at 11:11:10AM +0100, David Sterba wrote:
> Hi,
>
> On Mon, Oct 31, 2011 at 10:49:57PM -0400, Chris Mason wrote:
> > I've pushed out a new integration branch, but it is not for general use.
>
> Thank you!
>
> xfstests/083 and 089 cause the following warnings. I've seen them b
On Tue, Nov 01, 2011 at 11:36:37AM +0100, David Sterba wrote:
> xfstests/214
>
> [ 3142.654774] [ cut here ]
> [ 3142.656017] kernel BUG at fs/btrfs/tree-log.c:3106!
> [ 3142.656017] invalid opcode: [#1] SMP
> [ 3142.656017] CPU 0
> [ 3142.656017] Modules linked in: lo
On Tue, Nov 01, 2011 at 06:56:50AM -0400, Chris Mason wrote:
> On Tue, Nov 01, 2011 at 11:36:37AM +0100, David Sterba wrote:
> > xfstests/214
> >
> > [ 3142.654774] [ cut here ]
> > [ 3142.656017] kernel BUG at fs/btrfs/tree-log.c:3106!
>
> What kind of hardware are you ru
this time I'm not quite sure which xfstest triggered it, but there was
209 35s ... [11:20:19] [11:20:53] [failed, exit status 1] - output mismatch
(see 209.out.bad)
--- 209.out 2011-02-11 11:42:31.0 +0100
+++ 209.out.bad 2011-11-01 11:20:53.0 +0100
@@ -1,2 +1,2 @@
QA outp
On Tue, Nov 01, 2011 at 11:36:37AM +0100, David Sterba wrote:
> xfstests/214
>
> [ 3142.654774] [ cut here ]
> [ 3142.656017] kernel BUG at fs/btrfs/tree-log.c:3106!
What kind of hardware are you running this on? I'm passing 214 here.
-chris
--
To unsubscribe from this l
On Tue, Nov 01, 2011 at 05:22:20PM +0800, Liu Bo wrote:
> Hi,
>
> On 11/01/2011 10:49 AM, Chris Mason wrote:
> > Hi everyone,
> >
> > I've pushed out a new integration branch, but it is not for general use.
> >
> > I'm still going through and hammering on the new logging code code to
> > make s
xfstests/214
[ 3142.654774] [ cut here ]
[ 3142.656017] kernel BUG at fs/btrfs/tree-log.c:3106!
[ 3142.656017] invalid opcode: [#1] SMP
[ 3142.656017] CPU 0
[ 3142.656017] Modules linked in: loop btrfs aoe
[ 3142.656017]
[ 3142.656017] Pid: 27328, comm: xfs_io Tainted:
Hi,
On Mon, Oct 31, 2011 at 10:49:57PM -0400, Chris Mason wrote:
> I've pushed out a new integration branch, but it is not for general use.
Thank you!
xfstests/083 and 089 cause the following warnings. I've seen them before when
testing josef/for-chris and josef/master branches (reported on irc)
Hi,
On 11/01/2011 10:49 AM, Chris Mason wrote:
> Hi everyone,
>
> I've pushed out a new integration branch, but it is not for general use.
>
> I'm still going through and hammering on the new logging code code to
> make sure it is properly backwards compatible with older kernels and
> that it h
Hi everyone,
I've pushed out a new integration branch, but it is not for general use.
I'm still going through and hammering on the new logging code code to
make sure it is properly backwards compatible with older kernels and
that it hasn't introduced any new bugs.
*** Please do not use this code
13 matches
Mail list logo
