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

raid - troche przydlugie



Witaj,

  W jaki sposob mozna sprawdzic stopien synchroznizacji na dyskach.
  Zrobilem sobie instalatorem partycie typu raid. WSzystko
  teoretyczeni jest podpiete:
  ----------------CUT--------------------
 cat /proc/mdstat
Personalities : [raid1]
read_ahead 1024 sectors
md1 : active raid1 scsi/host0/bus0/target0/lun0/part2[0] scsi/host0/bus0/target1/lun0/part2[1]
      4883648 blocks [1/1] [U]

md2 : active raid1 scsi/host0/bus0/target0/lun0/part3[0] scsi/host0/bus0/target1/lun0/part3[1]
      8008320 blocks [1/1] [U]

md3 : active raid1 scsi/host0/bus0/target0/lun0/part4[0] scsi/host0/bus0/target1/lun0/part4[1]
      1943744 blocks [1/1] [U]

md0 : active raid1 scsi/host0/bus0/target0/lun0/part1[0] scsi/host0/bus0/target1/lun0/part1[1]
      2931712 blocks [1/1] [U]
  ----------------CUT--------------------
  ALe jak jest jakis odczyt czy zapis to ewidentnie widac i z pracuje
  tylko jeden dysk. Jak to mozna sprawdzic czy to sie synchronizuje. W
  logach podczas startu mam:
   ----------------CUT--------------------
Aug 14 00:05:59 kernel: md: trying to hot-add scsi/host0/bus0/target1/lun0/part4 to md2 ...
Aug 14 00:05:59 kernel: md: export_rdev(scsi/host0/bus0/target1/lun0/part4)
Aug 14 00:06:02 kernel: md: trying to hot-add scsi/host0/bus0/target1/lun0/part3 to md2 ...
Aug 14 00:06:02 kernel: md: bind<scsi/host0/bus0/target1/lun0/part3,2>
Aug 14 00:06:02 kernel: md: updating md2 RAID superblock on device
Aug 14 00:06:02 kernel: md: scsi/host0/bus0/target1/lun0/part3 [events: 00000086]<6>(write) scsi/host0/bus0/target1/lun0/part3's sb offset: 8008320
Aug 14 00:06:02 kernel: md: scsi/host0/bus0/target0/lun0/part3 [events: 00000086]<6>(write) scsi/host0/bus0/target0/lun0/part3's sb offset: 8008320
Aug 14 00:06:02 kernel: md: recovery thread got woken up ...
Aug 14 00:06:02 kernel: md: recovery thread finished ...
Aug 14 00:11:58 kernel: md: trying to hot-add scsi/host0/bus0/target1/lun0/part1 to md0 ...
Aug 14 00:11:58 kernel: md: bind<scsi/host0/bus0/target1/lun0/part1,2>
Aug 14 00:11:58 kernel: md: updating md0 RAID superblock on device
Aug 14 00:11:58 kernel: md: scsi/host0/bus0/target1/lun0/part1 [events: 00000087]<6>(write) scsi/host0/bus0/target1/lun0/part1's sb offset: 2931712
Aug 14 00:11:58 kernel: md: scsi/host0/bus0/target0/lun0/part1 [events: 00000087]<6>(write) scsi/host0/bus0/target0/lun0/part1's sb offset: 2931712
Aug 14 00:11:58 kernel: md: recovery thread got woken up ...
Aug 14 00:11:58 kernel: md: recovery thread finished ...
Aug 14 00:12:19 kernel: md: trying to hot-add scsi/host0/bus0/target1/lun0/part4 to md3 ...
Aug 14 00:12:19 kernel: md: bind<scsi/host0/bus0/target1/lun0/part4,2>
Aug 14 00:12:19 kernel: md: updating md3 RAID superblock on device
Aug 14 00:12:19 kernel: md: scsi/host0/bus0/target1/lun0/part4 [events: 00000086]<6>(write) scsi/host0/bus0/target1/lun0/part4's sb offset: 1943744
Aug 14 00:12:19 kernel: md: scsi/host0/bus0/target0/lun0/part4 [events: 00000086]<6>(write) scsi/host0/bus0/target0/lun0/part4's sb offset: 1943744
Aug 14 00:12:19 kernel: md: recovery thread got woken up ...
Aug 14 00:12:19 kernel: md: recovery thread finished ...
Aug 14 00:15:44 kernel: md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
Aug 14 00:15:44 kernel: md: raid1 personality registered as nr 3
Aug 14 00:15:44 kernel: md: bind<scsi/host0/bus0/target1/lun0/part1,1>
Aug 14 00:15:44 kernel: md: bind<scsi/host0/bus0/target0/lun0/part1,2>
Aug 14 00:15:44 kernel: md: scsi/host0/bus0/target0/lun0/part1's event counter: 00000088
Aug 14 00:15:44 kernel: md: scsi/host0/bus0/target1/lun0/part1's event counter: 00000088
   ----------------CUT--------------------
   Dziwi mnie tylko cos takiego:
   ----------------CUT--------------------
 mdadm --detail -t /dev/md3
/dev/md3:
        Version : 00.90.00
  Creation Time : Wed Jun 21 00:35:07 2006
     Raid Level : raid1
     Array Size : 1943744 (1.85 GiB 1.99 GB)
    Device Size : 1943744 (1.85 GiB 1.99 GB)
   Raid Devices : 1
  Total Devices : 2
Preferred Minor : 3
    Persistence : Superblock is persistent

    Update Time : Mon Aug 14 00:15:41 2006
          State : active
 Active Devices : 1
Working Devices : 2
 Failed Devices : 0
  Spare Devices : 1

           UUID : 67c2d3e0:53470403:66c4ae0e:a62d9606
         Events : 0.136

    Number   Major   Minor   RaidDevice State
       0       8        4        0      active sync   /dev/sda4

       1       8       20        1      spare   /dev/sdb4
   ----------------CUT--------------------
   Active Devices powinno byc 2 a jest 1 o co tu chodzi???
   
   Macie moze jakies pomysly? Sorry za lamerie ale w dziedzinei raida
   to dopiero zaczynam.
-- 
Pozdrawiam,
 Artur



Reply to: