Date: Thu, 11 Mar 2010 16:21:13 +0100 From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@des.no> To: Miroslav Lachman <000.fbsd@quip.cz> Cc: freebsd-current@freebsd.org Subject: Re: A tool for remapping bad sectors in CURRENT? Message-ID: <861vfq995i.fsf@ds4.des.no> In-Reply-To: <4B94FBA6.5090107@quip.cz> (Miroslav Lachman's message of "Mon, 08 Mar 2010 14:29:10 %2B0100") References: <20100308102918.GA5485@localhost> <4B94DDC8.5080008@quip.cz> <20100308115052.GA31896@office.redwerk.com> <4B94FBA6.5090107@quip.cz>
next in thread | previous in thread | raw e-mail | index | archive | help
Miroslav Lachman <000.fbsd@quip.cz> writes: > Yes, rewriting by dd or any other way works for reallocating or > clearing pending sectors counter, but in server environment In a server environment, you'd be a fool not to have some sort of redundancy set up. > I need to know the affected file, as it can be for example database > file and then it is a big problem! Rewriting the sector inside InnoDB > ib_data file can cause DB crash, data loss etc. How is that different from *not* rewriting the sector? If there's a bad sector somewhere in your data, your database is still going to crash. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?861vfq995i.fsf>