[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#505111: Proposed (naive) patch for mdadm RAID auto-assembly in rescue mode



On Sat, Nov 29, 2008 at 08:41:00PM +0100, Christian Perrier wrote:
> Comments from IRC after I posted this proposal:
> […]
> 20:22 < fjp> That's all crap IMO.
> 20:23 < Ryan52> fjp, what is?
> 20:23 < fjp> What needs to happen is addition of sanity checks that
>              the generated /tmp/mdadm.conf is sane.
> 20:23 < fjp> And only if it isn't we should prevent mounting.
> 20:24 < fjp> What you're proposing now is dropping functionality without providing an alternative.
> 20:24 < fjp> And any alternative is going to mean added strings...
> 20:24 < bubulle> yes, this is what I call a "naive" proposal
> 20:26 < fjp> Although rather nasty, the real problem here is basically
>              that the system was extremely dirty with loads of old no
>              longer valid raid IDs lying around.
> 20:27 < fjp> Given that Martin is the mdadm maintainer, the chance
>              that he'd run into this is a huge factor
>              larger than that anybody else will.
> 20:28 < Ryan52> okay, well, I can't help with that (at least this weekend..)
> 20:29 < bubulle> fjp: so, actually, your advice would be to ignore
>                  that issue for lenny (which is anyway what we
>                  will have to do), add it to the errata, and defer a
>                  clean fix for squeeze?
> 20:29 < bubulle> such as proposing the user to auto-assemble the RAID arrays or
>                  not, or whatever solution that adds user interaction

One of the main usage for the installer rescue mode for now is to easily
fix a broken bootloader configuration or other packages which might
prevent the system from booting.  The auto-assembly of RAID arrays
easily allow such usage for systems using RAID.

I did not had in mind that auto-assembly could result in some cases in
data loss.  But I also think for Lenny we should stick with the current
behaviour and document the issue as an erratum.  A proper fix would
require new strings…

Please note that this could also happen when starting partman during
normal installations (and this bug should probably be cloned to track
this other side of the problem).

Cheers,
-- 
Jérémy Bobbio                        .''`. 
lunar@debian.org                    : :Ⓐ  :  # apt-get install anarchism
                                    `. `'` 
                                      `-   

Attachment: signature.asc
Description: Digital signature


Reply to: