dangerous situation with shutdown process
Nicolas Rachinsky
list at rachinsky.de
Sat Jul 16 14:15:44 GMT 2005
* Matthias Buelow <mkb at incubus.de> [2005-07-16 16:07 +0200]:
> Nicolas Rachinsky wrote:
>
> >> >The track which is corrupted could contain data that wasn't written
> >> >to in months. How would the journal help?
> >>
> >> I don't understand this question.
> >
> >The track destroyed could contain sectors which are in no way related
> >to the sectors the OS is writing to.
>
> And in what way is that related to the existence or nonexistence
> of write barriers and a journal?
You wrote before:
| If track corruption occurs after the journal is written, it doesn't
| matter, since at boot the journal will be replayed and all operations
| will be performed once more.
> If you pound the disk with a hammer, it will most likely break,
> no matter what strategy you're using.
> That you cannot eliminate _all_ sources of error with a strategy
> doesn't mean that you shouldn't implement it to minimize the number
> of errors that could happen.
I'm not argumenting for or against write barriesrs or a journal.
Nicolas
More information about the freebsd-stable
mailing list