Date: Wed, 02 Jul 2014 08:14:30 +1000 From: Dewayne Geraghty <dewayne.geraghty@heuristicsystems.com.au> To: trasz@freebsd.org Cc: freebsd-stable@freebsd.org Subject: Re: 10/stable panic: softdep_deallocate_dependencies: dangling deps Message-ID: <53B332C6.6070007@heuristicsystems.com.au> In-Reply-To: <20140701184749.GA8617@brick.home> References: <021AFCAD-7B0B-47FB-AAFF-8F7085C7E1A6@gmail.com> <op.xia61kp0kndu52@ronaldradial.radialsg.local> <F84286C1-EB0F-4049-A567-1BB0E0FD19AE@gmail.com> <20140701184749.GA8617@brick.home>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2/07/2014 4:47 AM, Edward Tomasz Napierała wrote: > Soft updates cannot gracefully handle IO errors. It _will_ panic. > You can either prevent errors from happening by using redundancy > (ie. mirroring), or disable soft updates. That's how it works, > sorry. > > In theory it would be possible to prevent this from happening; > panic here is actually to terminate the system before it corrupts > data, and in situations like this one, where the disk is no longer > accessible, it's not possible to corrupt anything. IIRC I've > actually added a workaround for that a while ago, but, as you can > see, it's not enough, and I don't understand soft updates well > enough to fix it properly. > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" Thank-you for clarifying what we should expect with io failure. FreeBSD has been so reliable I'm sure that many (self included) have forgotten that this is the last "safe" option. Kind regards, Dewayne
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?53B332C6.6070007>