On Wed, Oct 7, 2009 at 4:40 PM, Chris Mason wrote:
> Ok great. Please let us know if you're able to trigger it again.
Thanks for your help. I'll build a new kernel and let you know if it
happens again.
Stefan
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body
On Wed, Oct 07, 2009 at 04:35:37PM +0100, Stefan Hajnoczi wrote:
> On Wed, Oct 7, 2009 at 4:25 PM, Chris Mason wrote:
> > This oops means that we're trying to insert an extent that already
> > exists. I think it is related to the bug in the file clone ioctl that
> > Sage recently fixed. The fix
On Wed, Oct 7, 2009 at 4:25 PM, Chris Mason wrote:
> This oops means that we're trying to insert an extent that already
> exists. I think it is related to the bug in the file clone ioctl that
> Sage recently fixed. The fix is in the master branch of the
> btrfs-unstable tree.
Thanks for explain
On Wed, Oct 07, 2009 at 11:34:54AM +0100, Stefan Hajnoczi wrote:
> I am testing btrfs on Linux 2.6.31.1 and am repeatedly hitting the
> following issue in the btrfs-endio-wri thread:
>
> [ cut here ]
> kernel BUG at fs/btrfs/file.c:528!
> invalid opcode: [#1] PREEMPT S
I am testing btrfs on Linux 2.6.31.1 and am repeatedly hitting the
following issue in the btrfs-endio-wri thread:
[ cut here ]
kernel BUG at fs/btrfs/file.c:528!
invalid opcode: [#1] PREEMPT SMP
last sysfs file: /sys/block/dm-0/range
CPU 0
Modules linked in: nls_utf8 h
