ZFS on root booting broken somewhere after r270020

Adam McDougall mcdouga9 at egr.msu.edu
Thu Sep 11 03:23:19 UTC 2014


On 09/10/2014 23:15, Kimmo Paasiala wrote:
> 
>> On 11.9.2014, at 4.25, Steven Hartland <killing at multiplay.co.uk> wrote:
>>
>> ----- Original Message ----- From: "Kimmo Paasiala" <kpaasial at icloud.com>
>>
>> snip...
>>
>>> Just a thought. Is my problem related to the use of GPT labeled partitions
>>> in my pool configuration? Your testing shows just "raw" devices like ada0p3 etc.
>>
>> That "should" have no impact on anything, we disable gptids and diskid's as we
>> don't like them adding an extra layer for lookups when admins are working with
>> the machines.
>>
>>   Regards
>>   Steve
> 
> I recreated the pool on the second disk as another single disk pool, performed zfs send -R … | zfs receive -F …
> 
> It works now just fine with the kernel that didn’t work with old pool so there must have been something seriously broken with the old pool. I also noticed the old pool kept repeatedly restarting the resilver operations when I tried to expand it into a mirror.
> 
> Case closed for now.
> 
> -Kimmo
> 
> 

Were you running a newer kernel with an older format zpool?  I heard
ixsystems had customers doing that and ran into corruption when they
tried to modify the zpool in some way (expand? I don't remember).
http://www.bsdnow.tv/episodes/2014_07_09-zfs_war_stories



More information about the freebsd-stable mailing list