Re: Running Apache Derby on 3.8 and BTRFS cause kernel oops

[Blair Zajac <blair@orcaware.com>]

On 02/28/2013 10:35 AM, Josef Bacik wrote:
> On Thu, Feb 28, 2013 at 11:31:15AM -0700, Daniel Kozák wrote:
>> Dne Thu, 28 Feb 2013 16:47:21 +0100 Josef Bacik <jbacik@fusionio.com>
>> napsal(a):
>>
>>> On Wed, Feb 27, 2013 at 03:59:35PM -0700, Blair Zajac wrote:
>>>> On 02/27/2013 02:08 PM, Josef Bacik wrote:
>>>>> On Wed, Feb 27, 2013 at 1:19 PM, Daniel Kozák <kozzi11@gmail.com>
>>>> wrote:
>>>>>>
>>>>>> [kozzi@KozziFX ~]$ mkdir derby
>>>>>> [kozzi@KozziFX ~]$ cd derby/
>>>>>> [kozzi@KozziFX derby]$ wget -c -q
>>>>>>
>>>> http://mirror.hosting90.cz/apache//db/derby/db-derby-10.9.1.0/db-derby-10.9.1.0-bin.zip
>>>>>> [kozzi@KozziFX derby]$ unzip -qq db-derby-10.9.1.0-bin.zip
>>>>>> [kozzi@KozziFX derby]$ cd db-derby-10.9.1.0-bin/
>>>>>> [kozzi@KozziFX db-derby-10.9.1.0-bin]$ DERBY_HOME=`pwd`
>>>>>> [kozzi@KozziFX db-derby-10.9.1.0-bin]$ java -jar
>>>>>> $DERBY_HOME/lib/derbyrun.jar server start &
>>>>>> [kozzi@KozziFX db-derby-10.9.1.0-bin]$ java -jar
>>>>>> $DERBY_HOME/lib/derbyrun.jar ij
>>>>>> verze ij 10.9
>>>>>> ij> CONNECT 'jdbc:derby://localhost:1527/seconddb;create=true';
>>>>>>
>>>>>> BTW. after this I must restart my PC, and after restart, my system
>>>> doesn't
>>>>>> boot anymore :-) (some more btrfs oops).
>>>>>> So I must use btrfs check --repair /dev/sdaX.
>>>>>>
>>>>>
>>>>> Sigh and of course I can't reproduce myself, even with importing a
>>>>> huge database into derby.  So you are just mounting with -o
>>>>> compress=lzo?  What about the mkfs, are you using raid or anything?
>>>>> Are you on a ssd?  Also when this happens is there any output above
>>>>> the --- [ cut here ] ---?  There should be something about length and
>>>>> such.  Thanks,
>>>>
>>>> I was able to reproduce on with 3.8 using Ubuntu 13.04 running in KVM
>>>> using the commands exactly as given, but it only after stopping and
>>>> starting the server again.
>>>>
>>>> I use the cloud image from here, boot of an Ubuntu CD-ROM ISO to change
>>>> from ext4 to btrfs, then installed openjdk.
>>>>
>>>> http://cloud-images.ubuntu.com/raring/current/raring-server-cloudimg-amd64-disk1.img
>>>>
>>>> I could make my image available for download later if you need it, in a
>>>> pre-failure state.  Let me know.
>>>>
>>>
>>> Yeah I still can't reproduce, can either of you send me your kernel
>>> config so I
>>> can see if it's something in my config that's causing problems?  Thanks,
>>>
>>> Josef
>>
>> Yes, here is it
>>
>
> Great I'll set this up on both of my boxes and see if I can reproduce.  In the
> meantime will you try btrfs-next?  I just pushed a tree-log fix that I don't
> think will fix your problem but since I don't know what your problem is yet it
> might, so I'd like to at least eliminate it.  Thanks,

I put a KVM image up at that you can try:

http://www-devel.orcaware.com/blair/btrfs/2013-02-28/

Download all three files, make a copy of 
raring-server-cloudimg-amd64-disk1.img since I can only reproduce from 
the initial state, run launch_image.sh, log in as ubuntu/ubuntu.  I had 
most luck getting the issue by running 'sync' and then BTRFS.sh. 
Without the 'sync' it doesn't fail as often.  If it doesn't fail the 
first time, stop the instance, restore the image from your copy and try 
again.  A 'while true; ./BTRFS.sh; done' loop doesn't fail if it doesn't 
fail the first time.  It can take up to 5 times before it locks up on me.

Blair