> 
> *to be able to boot the machine with one disk down
> set md:mirrored_root_flag=1
> 

Clairement si ce paramêtre n'est pas explicitement mis à 1 un disque
système
(partition root raidée en mirroir avec 2 disques ne peut pas rebooter si
l'un des deux disques est mort).

Ce que je trouve inquiétant c'est ce que dit la doc au sujet de ce
paramêtre (son
utilisation n'est pas supportée !!!!).

Aussi soit on l'utilise et Sun en cas de problème dira que ce n'est pas
supporté, soit on ne l'utilise pas et que faut-il faire alors si un
disque root en mirroir est HS ?

=====

md:mirrored_root_flag

Description 
        
        Overrides Solaris Volume Manager requirements for replica quorum
        and forces Solaris Volume Manager to start if any valid state
        database replicas are available.
        
        The default value is disabled, which requires that a majority of
        all replicas are available and synchronized before Solaris
        Volume Manager will start.
        
        
Data Type 
        
        Boolean values
        
        
Default 
        
        0 (disabled)
        
        
Range 
        
        0 (disabled) or 1 (enabled)
        
        
Dynamic? 
        
        No
        
        
Validation 
        
        None
        
        
When to Change 
        
        Use of this parameter is not supported.
        
        Some people using Solaris Volume Manager accept the risk of
        enabling this parameter if all three of the following conditions
        apply:
        
        
              * When root (/) or other system-critical file systems are
                mirrored
                
              * Only two disks or controllers are available
                
              * An unattended reboot of the system is required
                
        If this parameter is enabled, the system might boot with a stale
        replica that inaccurately represents the system state (including
        which mirror sides are good or in Maintenance state). This
        situation could result in data corruption or system corruption.
        
        Change this parameter only if system availability is more
        important than data consistency and integrity. Closely monitor
        the system for any failures. You can mitigate the risk by
        keeping the number of failed, Maintenance, or hot-swapped
        volumes as low as possible.
        
        For more information about state database replicas, see Chapter
        6, State Database (Overview),in Solaris Volume Manager
        Administration Guide.
        
        
Commitment Level 
        
        Unstable
        
        






-- 
Christian Pélissier
Office National d'Études et de Recherches Aérospatiales
BP 72 92322 Chatillon
Tel: 33 1 46 73 44 19, Fax: 33 1 46 73 41 50


_______________________________________________
Solaris_fr liste de diffusion en français pour Solaris, sur toutes architectures
[email protected]
http://x86.sun.com/mailman/listinfo/solaris_fr

Répondre à