[[ stupid mouse ]]
On Thu, Mar 16, 2017 at 10:01 AM, Warner Losh wrote:
> On Thu, Mar 16, 2017 at 6:06 AM, Pete French
> wrote:
>>> I don't like the delay and retry approach at all.
>>
>> Its not ideal, but it is what we do for UFS after all...
>>
>>> Imagine that you told the kernel that you w
On Thu, Mar 16, 2017 at 6:06 AM, Pete French wrote:
>> I don't like the delay and retry approach at all.
>
> Its not ideal, but it is what we do for UFS after all...
>
>> Imagine that you told the kernel that you want to mount your root from a ZFS
>> pool which is on a USB driver which you have al
> I don't like the delay and retry approach at all.
Its not ideal, but it is what we do for UFS after all...
> Imagine that you told the kernel that you want to mount your root from a ZFS
> pool which is on a USB driver which you have already thrown out. Should the
> kernel just keep waiting for
On 16/03/2017 13:18, Pete French wrote:
>
>> So, the kernel attempted to mount the root even before vmbus was attached
>> and,
>> thus, before storvsc appeared and informed the kernel that it might be
>> holding
>> the root.
>> How ZFS was supposed to know that vmbus is ever going to appear?
>>
So, the kernel attempted to mount the root even before vmbus was attached and,
thus, before storvsc appeared and informed the kernel that it might be holding
the root.
How ZFS was supposed to know that vmbus is ever going to appear?
To me this sounds more like a problem with the Hyper-V drivers.
Thanks - that is a better fix than my hack ;-)
On 03/15/17 20:12, Dimitry Andric wrote:
On 15 Mar 2017, at 13:42, Pete French wrote:
/usr/src/sys/modules/mlx4ib/../../ofed/drivers/infiniband/hw/mlx4/sysfs.c:90:22:
error:
format specifies type 'unsigned long long *' but the argument ha
On 2017-Mar-15, at 11:07 PM, Scott Bennett wrote:
> Mark Millard wrote:
>
>> [Something strange happened to the automatic CC: fill-in for my original
>> reply. Also I should have mentioned that for my test program if a
>> variant is made that does not fork the swapping works fine.]
>>
>> On 20
On 13/03/2017 21:07, Edward Tomasz Napierała wrote:
> Are you sure the above transcript is right? There are three reasons
> I'm asking. First, you'll see the "Root mount waiting" message,
> which means the root mount code is, well, waiting for storvsc, exactly
> as expected. Second - there is no
