Hp StorageWorks Scalable File Share Manuel d'utilisateur Page 282

  • Télécharger
  • Ajouter à mon manuel
  • Imprimer
  • Page
    / 362
  • Table des matières
  • DEPANNAGE
  • MARQUE LIVRES
  • Noté. / 5. Basé sur avis des utilisateurs
Vue de la page 281
Troubleshooting9–58
Number Major Minor RaidDevice State
0 105 96 0 active sync /dev/cciss/c1d6
1 105 32 -1 faulty /dev/cciss/c1d2
# cat /proc/mdstat
Personalities : [linear] [raid0] [raid1] [raid5] [multipath]
read_ahead 1024 sectors
md0 : active raid1 cciss/c1d2[1](F) cciss/c1d6[0]
10485504 blocks [2/1] [U_]
unused devices: <none>
If you have stopped and restarted the file system or rebooted the south2 server, the status may
indicate that the failed component is missing, instead of failed. In this case, the mdadm command
shows a different status, as shown in this example:
# mdadm --detail /dev/md0/dev/md0:
.
.
.
State : clean, degraded
.
.
.
Number Major Minor RaidDevice State
0 105 96 0 active sync /dev/cciss/c1d6
1 0 0 -1 removed
Whether the component is failed or missing does not matter; proceed with the remaining steps.
6. In the example in the previous step, the /dev/cciss/c1d2 component is shown to have failed,
while the /dev/cciss/c1d6 component is operational. You can determine which LUN the
/dev/cciss/c1d2 component is associated with by entering the command shown in the following
example:
# ls -l /dev/hpls | grep c1d2$
lrwxrwxrwx 1 root root 9 May 4 01:49 /dev/hpls/dev22a -> /dev/cciss/c1d2
lrwxrwxrwx 1 root root 17 Nov 4 17:23 /dev/hpls/dev22a1
-> /dev/cciss/c1d2p1
In this example, LUN 22 (/dev/hpls/dev22a) is the failed mirror component.
7. Remove the failed mirror component and then add it again, as shown in the following example:
# mdadm --remove /dev/md0 /dev/cciss/c1d2
mdadm: hot removed /dev/cciss/c1d2
# mdadm --add /dev/md0 /dev/cciss/c1d2
mdadm: hot added /dev/cciss/c1d2
NOTE: The mdadm --remove command may fail if the failed mirror component has already
been removed. This is normal and you can proceed to run the mdadm --add command.
8. At this point, the RAID device will recover and start to resynchronize the device. You can check the
status and progress of the resynchronization of the device using the mdadm command, as shown in
the following example:
# mdadm --detail /dev/md0
/dev/md0:
.
.
.
State : clean, degraded, recovering
.
.
.
Rebuild Status : 26% complete
.
.
.
Number Major Minor RaidDevice State
0 105 96 0 active sync /dev/cciss/c1d6
1 0 0 -1 removed
2 105 32 0 spare /dev/cciss/c1d2
Vue de la page 281
1 2 ... 277 278 279 280 281 282 283 284 285 286 287 ... 361 362

Commentaires sur ces manuels

Pas de commentaire