30 messages in org.freebsd.freebsd-currentRe: A tool for remapping bad sectors ...| From | Sent On | Attachments |
|---|---|---|
| Eugeny N Dzhurinsky | Mar 8, 2010 2:26 am | |
| Alexander Motin | Mar 8, 2010 2:31 am | |
| Eugene Dzhurinsky | Mar 8, 2010 2:52 am | |
| Eugene Dzhurinsky | Mar 8, 2010 2:54 am | |
| Eugene Dzhurinsky | Mar 8, 2010 3:08 am | |
| Miroslav Lachman | Mar 8, 2010 3:21 am | |
| Wes Morgan | Mar 8, 2010 3:46 am | |
| Eugene Dzhurinsky | Mar 8, 2010 3:50 am | |
| Miroslav Lachman | Mar 8, 2010 5:28 am | |
| Alex Keda | Mar 8, 2010 12:14 pm | |
| Ulrich Spörlein | Mar 11, 2010 5:47 am | |
| Dag-Erling Smørgrav | Mar 11, 2010 7:20 am | |
| Svein Skogen (Listmail Account) | Mar 11, 2010 7:23 am | |
| Miroslav Lachman | Mar 13, 2010 12:44 pm | |
| Dag-Erling Smørgrav | Mar 13, 2010 1:24 pm | |
| Miroslav Lachman | Mar 14, 2010 1:54 am | |
| Gary Jennejohn | Mar 14, 2010 4:38 am | |
| Miroslav Lachman | Mar 14, 2010 9:18 am | |
| Gary Jennejohn | Mar 14, 2010 10:47 am | |
| Dag-Erling Smørgrav | Mar 17, 2010 3:58 am | |
| Miroslav Lachman | Mar 17, 2010 4:35 am | |
| Miroslav Lachman | Mar 17, 2010 4:41 am | |
| Dag-Erling Smørgrav | Mar 17, 2010 4:59 am | |
| Gary Jennejohn | Mar 17, 2010 5:05 am | |
| Miroslav Lachman | Mar 18, 2010 3:29 am | |
| Miroslav Lachman | Mar 18, 2010 3:32 am | |
| Dag-Erling Smørgrav | Mar 18, 2010 4:10 am | |
| Pieter de Goeje | Mar 18, 2010 4:33 am | |
| Miroslav Lachman | Mar 18, 2010 4:45 am | |
| Dag-Erling Smørgrav | Mar 18, 2010 5:17 am |
| Subject: | Re: A tool for remapping bad sectors in CURRENT? | |
|---|---|---|
| From: | Miroslav Lachman (000....@quip.cz) | |
| Date: | Mar 13, 2010 12:44:48 pm | |
| List: | org.freebsd.freebsd-current | |
Dag-Erling Smørgrav wrote:
Miroslav Lachman<000....@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 am using gmirror on low-end servers, so rewriting some sectors on one disk drive is useless and in this case I prefer resync of the whole gmirror (but it is log run - about 10 hours on busy server)
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.
It is not about "different", it is about "I need to know the affected file" to know what actions should be taken. If it is some logfile, I can delete it and then rewrite the sector. If it is some "normal" unchanged file, I can restore it from backup, if it is database file, I must take some special action. For example, stop DB engine, try to repair/fix the DB file, dump & restore etc. So the first step is to find "what file is affected", then take some action AND rewrite the sector by dd to reallocate the sector. (or replace the drive)
So... can somebody with enough knowledge write some docs / script how to find the affected file based on LBA read error from messages / SMART log?
Miroslav Lachman
_______________________________________________ free...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "free...@freebsd.org"