Re: Re: grub 0.96 bug

[Wilfried Weissmann <Wilfried.Weissmann@gmx.at>]

Molle Bestefich wrote:
> Wilfried Weissmann wrote:
> 
>>>It must be severely broken; since if it just sticked to writing to the
>>>device I pointed it at (hpt37x_ehgjaggaf) which is a RAID0 "virtual
>>>disk" / whatever, it should never be able to overwrite metadata out on
>>>the physical disk.
>>
>>HPT desided to make the metadata accessable from the virtual disk. Just
>>look at sector 9 of a working array and enjoy the show...
> 
> 
> That's an awful decision.

It is, isn't it?

>>Grub is fine. At least the version that I am using. You have to do some
>>tricks to get grub running on the old hpt controllers (I think the new
>>ones are better, but I cannot tell for sure).
>>
>>Just copy the stage 1.5 reiserfs module to sector 16 instead of sector 8
>>which is the grub default that destroys the metadata in case of a hpt.
>>[explanation snipped]
> 
> 
> Thanks for the explanation!
> There should be an option in the GRUB configuration to do this, so
> that the RAID won't get overwritten the next time I do a grub-install,
> I think.

That would make my life a lot easier! On the other hand, the most 
straight forward thing to do would be to move the stage 1.5 to another 
default sector. So you can not forget to set any option that ruins your 
array if missing. Also there is no need to add some autodetection code 
for hpt controllers then.

> 
> Or even better, dmraid could protect the metadata blocks by some magic
> flag to dm-mod.
> This isn't possible as is, is it?

One can make any I/O to this block fail. But I would like something like 
discarding any writes and only perform reads. "dd" backups would still 
work then.

Greetings,
Wilfried