Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 17 Mar 2011 18:00:39 +0100
From:      Olivier Smedts <olivier@gid0.org>
To:        Freddie Cash <fjwcash@gmail.com>
Cc:        FreeBSD-Current <freebsd-current@freebsd.org>
Subject:   Re: ZFS import panic with r219703
Message-ID:  <AANLkTi=6yCUEZGHLtOVUbHrieqd62LE51-Bs9UKLF1zQ@mail.gmail.com>
In-Reply-To: <AANLkTikdCNXH7KujZ6UqEzL%2B-ABF8vyFKL8yfzhr6sAz@mail.gmail.com>
References:  <AANLkTikEBAXz6LO3JOJq7ro0_MRcSUBZa2Fq0WdcJxsQ@mail.gmail.com> <AANLkTikwOhLe4=1b-zc4XCMHeL=ANvApyww%2BjG5gykC5@mail.gmail.com> <AANLkTikdCNXH7KujZ6UqEzL%2B-ABF8vyFKL8yfzhr6sAz@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
2011/3/17 Freddie Cash <fjwcash@gmail.com>:
> On Thu, Mar 17, 2011 at 9:24 AM, Freddie Cash <fjwcash@gmail.com> wrote:
>> On Wed, Mar 16, 2011 at 4:03 PM, Freddie Cash <fjwcash@gmail.com> wrote:
>>> Anytime I try to import my pool built using 24x HAST devices, I get
>>> the following message, and the system reboots:
>>>
>>> panic: solaris assert: dmu_free_range(os, smo->smo_object, 0, -1ULL,
>>> tx) =3D=3D 0, file:
>>> /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/s=
pace_map.c,
>>> line: 484
>>>
>>> Everything runs nicely if I don't import the pool.
>>>
>>> Doing a "zpool import" shows that one of the HAST devices is FAULTED
>>> "corrupted data".
>>>
>>> Haven't tried anything to remove/replace the faulted device, just
>>> wanted to see if anyone knew what the above error meant.
>>>
>>> Pool was created using r219523 and successfully copied over 1 TB of
>>> data from another ZFS system. =A0Had some issues with gptboot this
>>> morning and the system locking up and rebooting a bunch, and now the
>>> pool won't import.
>>
>> Hrm, it looks like the "pool roll-back on import" feature is working.
>>
>> # zpool import -F -d /dev/hast storage
>>
>> The above command imported the pool successfully. =A0No dmu_free_range()
>> errors. =A0No solaris assert. =A0No kernel panic. =A0Will try hammering =
on
>> the system a bit to see if that sticks or whether the space_map errors
>> show up again.
>
> Damn, of course that would be too easy. =A0:( =A0Adding or removing any
> data from the pool still causes it to panic with the dmu_free_range()
> assertion.

Does resilvering help after the forced import ?

>
> --
> Freddie Cash
> fjwcash@gmail.com
> _______________________________________________
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org=
"
>


--=20
Olivier Smedts=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=A0 _
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 =A0 ASCII ribbon campaign ( )
e-mail: olivier@gid0.org=A0 =A0 =A0 =A0 - against HTML email & vCards=A0 X
www: http://www.gid0.org=A0 =A0 - against proprietary attachments / \

=A0 "Il y a seulement 10 sortes de gens dans le monde :
=A0 ceux qui comprennent le binaire,
=A0 et ceux qui ne le comprennent pas."



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTi=6yCUEZGHLtOVUbHrieqd62LE51-Bs9UKLF1zQ>