From mboxrd@z Thu Jan 1 00:00:00 1970 From: Molle Bestefich Subject: Re: Re: grub 0.96 bug Date: Tue, 22 Mar 2005 21:11:46 +0100 Message-ID: <62b0912f0503221211c21d0ec@mail.gmail.com> References: <62b0912f05031606396a3a47db@mail.gmail.com> <62b0912f050319145547c4a7db@mail.gmail.com> <20050320163001.GB643@percy.comedia.it> <62b0912f05032019262c009465@mail.gmail.com> <62b0912f0503202121607bd38a@mail.gmail.com> <62b0912f05032104052e78fd60@mail.gmail.com> <62b0912f050321065558fc956@mail.gmail.com> <423F0F74.3030007@gmx.at> <62b0912f050321235348c20525@mail.gmail.com> <42407227.2020402@gmx.at> Reply-To: Molle Bestefich , device-mapper development Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit In-Reply-To: <42407227.2020402@gmx.at> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dm-devel-bounces@redhat.com Errors-To: dm-devel-bounces@redhat.com To: Wilfried Weissmann Cc: bug-grub@gnu.org, dm-devel@redhat.com, ataraid-list@redhat.com List-Id: dm-devel.ids >> 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. One step ahead of me, you are. I was just thinking of doing autodetection of HPT magic in GRUB. The autodetection has a plus side too, though. It can detect other stuff that should not be touched (Windows/Veritas dynamic partition information comes to mind?) and not touch sectors based on what is actually there on a particular system. Would perhaps save the implementor the pain of choosing once there's just too many reserved sectors and the stage1.5 loader wont fit. I think I've read that the stage1.5 loader is not really necessary in some cases, think I'll go doc-hunting. >> 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. Right. And perhaps a user-definable flag to turn the protection on or off :-). Is it possible without adding new code to dm-mod?