Re: Caveat emptor: Beware of ZFS on HEAD

2017-07-17 Thread Chargen
Thumbs up, gentlemen!

Regards,
Edwin

-- 
Deze e-mail en de inhoud is vertrouwelijk en uitsluitend bestemd voor de
geadresseerde(n). Indien u niet de geadresseerde bent van deze e-mail
verzoeken wij u dit direct door te geven aan de verzender door middel van
een reply e-mail en de ontvangen e-mail uit uw systemen te verwijderen. Als
u geen geadresseerde bent, is het niet toegestaan om kennis te nemen van de
inhoud, deze te kopieren, te verspreiden, bekend te maken aan derden noch
anderszins te gebruiken.

The information contained in this e-mail is confidential and may be legally
privileged. It is intended solely for the addressee. If you are not the
intended recipient, any disclosure, copying, distribution or any action
taken or omitted to be taken in reliance on it, is prohibited and may be
unlawful. Please notify us immediately if you have received it in error by
reply e-mail and then delete this message from your system.

On Mon, Jul 17, 2017 at 8:35 AM, Andriy Gapon  wrote:

> On 12/07/2017 23:20, Peter Wemm wrote:
> > We mostly run HEAD in the freebsd.org cluster.  Sometime in the last
> few weeks
> > an ugly zfs problem has surfaced. If a redundant volume is degraded, zfs
> > panics on boot.  If a drive fails while running, or is manually put
> offline, zfs
> > panics the same way.
> >
> > I do not have a smoking gun, but I am suspicious of the June 28th commits
> > (starting at r320156) and their follow-ups. eg: r320452.
> >
> > https://bugs.freebsd.org/220691
> >
> > I believe single disk systems will *not* be affected by this - the panic
> only
> > happens when a raidz (and presumably mirror) degrades.  Your laptop etc
> should
> > be fine.
> >
> > I apologize for being vague - I do not know more. Folks running HEAD
> should
> > take appropritate precautions (eg: keeping a known-good kernel.old and
> modules
> > around).  This is always advisable when running HEAD anyway,
> particularly so
> > now.  For us, a kernel.old from June 18th worked fine.
> >
>
> My apologies for the bug.
> Everyone affected, could you please test the patch from the bug report?
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220691#c3
> Thank you!
>
> --
> Andriy Gapon
> ___
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
>
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


Re: Caveat emptor: Beware of ZFS on HEAD

2017-07-16 Thread Andriy Gapon
On 12/07/2017 23:20, Peter Wemm wrote:
> We mostly run HEAD in the freebsd.org cluster.  Sometime in the last few 
> weeks 
> an ugly zfs problem has surfaced. If a redundant volume is degraded, zfs 
> panics on boot.  If a drive fails while running, or is manually put offline, 
> zfs 
> panics the same way.
> 
> I do not have a smoking gun, but I am suspicious of the June 28th commits 
> (starting at r320156) and their follow-ups. eg: r320452.
> 
> https://bugs.freebsd.org/220691
> 
> I believe single disk systems will *not* be affected by this - the panic only 
> happens when a raidz (and presumably mirror) degrades.  Your laptop etc 
> should 
> be fine.
> 
> I apologize for being vague - I do not know more. Folks running HEAD should 
> take appropritate precautions (eg: keeping a known-good kernel.old and 
> modules 
> around).  This is always advisable when running HEAD anyway, particularly so 
> now.  For us, a kernel.old from June 18th worked fine.
> 

My apologies for the bug.
Everyone affected, could you please test the patch from the bug report?
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220691#c3
Thank you!

-- 
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


Caveat emptor: Beware of ZFS on HEAD

2017-07-12 Thread Peter Wemm
We mostly run HEAD in the freebsd.org cluster.  Sometime in the last few weeks 
an ugly zfs problem has surfaced. If a redundant volume is degraded, zfs 
panics on boot.  If a drive fails while running, or is manually put offline, 
zfs 
panics the same way.

I do not have a smoking gun, but I am suspicious of the June 28th commits 
(starting at r320156) and their follow-ups. eg: r320452.

https://bugs.freebsd.org/220691

I believe single disk systems will *not* be affected by this - the panic only 
happens when a raidz (and presumably mirror) degrades.  Your laptop etc should 
be fine.

I apologize for being vague - I do not know more. Folks running HEAD should 
take appropritate precautions (eg: keeping a known-good kernel.old and modules 
around).  This is always advisable when running HEAD anyway, particularly so 
now.  For us, a kernel.old from June 18th worked fine.

-- 
Peter Wemm - pe...@wemm.org; pe...@freebsd.org; pe...@yahoo-inc.com; KI6FJV
UTF-8: for when a ' or ... just won\342\200\231t do\342\200\246

signature.asc
Description: This is a digitally signed message part.