Salut!

Am intampinat urmatoarea problema pe Slackware 14.1 (kernel 3.10.17 x64, 
mdadm 3.2.6)
Se da un array RAID1 construit din sdb si sdc. La un moment dat sdb este 
inlocuit (hot) si se declanseaza un rebuild. Problema este ca daca se da 
reboot la calculator inainte de terminarea rebuildului, acesta nu mai 
este finalizat iar matricea apare clean (fara degraded/recovering). 
Evident datele sunt aiurea (corupte, sdb era hdd nou).

Nu reusesc sa gasesc nimic relevant cu exceptia unui bug mai vechi 
raportat in Fedora in 2012:
https://bugzilla.redhat.com/show_bug.cgi?id=817039
Sugestia acolo a fost update la mdadm; al meu este deja mai nou si 
oricum mdadm este user-space, nu cred ca aici e problema. Pentru orice 
eventualitate am pus mdadm 3.3.4 dar problema persista.

Am testat si cu partitii tip 0xfd, si pe un alt sistem tot Slackware 
14.1 dar cu kernel x86; se intampla la fel.

Tot ce tine de RAID este facut strict din Linux, nu am folosit eventuale 
facilitati de software-RAID ale placilor de baza.

E vreo optiune care imi scapa sau este un bug pe undeva. In ultima 
varianta, in afara de kernel (si de mdadm pe care l-am actualizat) mai 
poate fi si alta componenta care sa afecteze functionarea RAID-ului?

In fine, are cineva la indemana un sistem cu care sa testeze? Pasii ar fi:
root@nxen:~# mdadm -C /dev/md127 --level=1 --raid-devices=2 /dev/sdb1 
/dev/sdc1
dupa ce e in stare clean (fara resyncing)
root@nxen:~# mdadm --manage /dev/md127 --fail /dev/sdc1
mdadm: set /dev/sdc1 faulty in /dev/md127
root@nxen:~# mdadm --manage /dev/md127 --remove failed
mdadm: hot removed 8:33 from /dev/md127
root@nxen:~# mdadm --manage /dev/md127 -a /dev/sdc1
mdadm: added /dev/sdc1
si incepe reconstructia:
root@nxen:~# mdadm --detail /dev/md127
root@nxen:~#  mdadm --detail /dev/md127
/dev/md127:
         Version : 1.2
   Creation Time : Wed Sep 30 14:48:05 2015
      Raid Level : raid1
      Array Size : 20955136 (19.98 GiB 21.46 GB)
   Used Dev Size : 20955136 (19.98 GiB 21.46 GB)
    Raid Devices : 2
   Total Devices : 2
     Persistence : Superblock is persistent

     Update Time : Wed Sep 30 14:55:52 2015
           State : active, degraded, recovering
  Active Devices : 1
Working Devices : 2
  Failed Devices : 0
   Spare Devices : 1

  Rebuild Status : 1% complete

            Name : nxen:127  (local to host nxen)
            UUID : 7589d8f8:0d8b5716:06e07bfa:28407522
          Events : 23

     Number   Major   Minor   RaidDevice State
        0       8       17        0      active sync   /dev/sdb1
        2       8       33        1      spare rebuilding   /dev/sdc1
se da reboot si la verificare este totul "ca nou"
root@nxen:~# mdadm --detail /dev/md127
/dev/md127:
         Version : 1.2
   Creation Time : Wed Sep 30 14:48:05 2015
      Raid Level : raid1
      Array Size : 20955136 (19.98 GiB 21.46 GB)
   Used Dev Size : 20955136 (19.98 GiB 21.46 GB)
    Raid Devices : 2
   Total Devices : 2
     Persistence : Superblock is persistent

     Update Time : Wed Sep 30 14:56:35 2015
           State : clean
  Active Devices : 2
Working Devices : 2
  Failed Devices : 0
   Spare Devices : 0

            Name : nxen:127  (local to host nxen)
            UUID : 7589d8f8:0d8b5716:06e07bfa:28407522
          Events : 26

     Number   Major   Minor   RaidDevice State
        0       8       17        0      active sync   /dev/sdb1
        2       8       33        1      active sync   /dev/sdc1


Multumesc,
Mihai Gaitos
_______________________________________________
RLUG mailing list
RLUG@lists.lug.ro
http://lists.lug.ro/mailman/listinfo/rlug

Raspunde prin e-mail lui