On 27/08/2012 21:18, Joseph Glanville wrote:
> On 28 August 2012 06:15, Jonathan Tripathy <jonnyt@xxxxxxxxxxx>
wrote:
>> On 27/08/2012 21:07, Jonathan Tripathy wrote:
>>> On 27/08/2012 21:00, Jonathan Tripathy wrote:
>>>>
>>>>> 2) The windows setup didn't complain that it couldn't install
on
>>>>> the LV, but once I clicked 'next', the Dom0 crashed and the
server
>>>>> rebooted. A lot of output was displayed on screen but quickly
>>>>> vanished as the system rebooted. I'm trying to see if the
output
>>>>> was saved anywhere. Any ideas why this could of happened
and/or
where the output might be saved?
>>>>>
>>>>>
>>>> I'd also like to add that after the server came back up, the md
>>>> raid array started rebuilding. I wondering if that's just a
>>>> coincidence (due to the forced reboot), or a sign of something
>>>> wrong with the md integration with bcache?
>>>>
>>>> I'm going to see if Windows installs natively on the md array
(it's
>>>> RAID
>>>> 10 btw) and post back here.
>>>
>>> Ok, so trying to install Windows directly onto the spindles
causes
>>> the same thing to happen. I'm going to try and boot up into the
>>> non-bcache kernel (The default ubuntu one) and see if it works
>>> there. If it fails there, then this is clearly a xen and/or
mdraid issue...
>>>
>>> Thanks
>>>
>>>
>> Ok, so booting into the default Ubuntu kernel, the windows
>> installation seems to progress just fine.
>>
>> Does this mean there is something wrong with the mdraid code in
the
>> bcache kernel?
>>
>> Actually, I'm not telling the whole story. The kernel I'm using
is
>> the
>> bcache-3.2 tree (from evilpriate.org) with changes merged in from
>> kernel.org's 3.2.27 tree. There were no merge conflicts when I
did
>> the git merge.
>>
>> What do you think I should do?
>>
>>
>> Thanks
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe
>> linux-bcache" in the body of a message to
majordomo@xxxxxxxxxxxxxxx
>> More majordomo info at
http://vger.kernel.org/majordomo-info.html
> I would recommend booting with the raw bcache-3.2 branch before
> applying the stable patches (even though they should be fine) and
> trying to catch the panic.
> This is easiest done with a serial port and setting it to the
kernel
> console on the kernel command line in grub.
>
> Joseph.
Hi There,
I can confirm that the problem occurs even when using the raw
bcache-3.2
branch from evilpirate.org. Just to clarify, I am trying to install
Windows
Server 2008 in a Xen HVM DomU, onto an LV which is on top of a
MDRAID 10
array. Using the bcache-3.2 kernel, the system reboots (after
panicing) as soon as I click 'next' after selecting the drive to
install windows
onto. Using the standard Ubuntu kernel everything works as normal.
This
leads me to believe that there is an issue with the mdraid code
inside the
bcache-3.2 tree. I'd like to stress that I wasn't doing any bcaching
during this
test.
