md: syncing RAID array
Salve a tutti,
sono abbastanza perplesso dalle prove fatte ultimamente con il raid
software. In pratica ho creato un raid 1 usando 2 dischi ide, ma non
capisco perchè ogni tanto debian si metta a risincronizzare i dati degli
array... Infatti, oltre a essere lunga la cosa (circa un ora) mi
decadono le prestazioni in i/o sui dischi !
Ecco cosa fa, all'incirca una volta al dì
tux:~# cat /proc/mdstat
Personalities : [raid1]
md4 : active raid1 hda6[0] hdd6[1]
6875712 blocks [2/2] [UU]
md3 : active raid1 hda5[0] hdd5[1]
107715712 blocks [2/2] [UU]
[================>....] resync = 81.0% (87348800/107715712)
finish=0.1min speed=2048764K/sec
md2 : active raid1 hda3[0] hdd3[1]
1461824 blocks [2/2] [UU]
md0 : active raid1 hda1[0] hdd1[1]
96256 blocks [2/2] [UU]
md1 : active raid1 hda2[0] hdd2[1]
3903680 blocks [2/2] [UU]
unused devices: <none>
La partizione md3 è più di 100gb.. Ho paura che a furia di
sincronizzarsi prima o poi un disco possa rompersi.
Ecco cosa mi dice il file messages:
Nov 7 22:22:00 ctrlaltcanc kernel: device-mapper: 4.5.0-ioctl
(2005-10-04) initialised: dm-devel@redhat.com
Nov 7 22:22:00 ctrlaltcanc kernel: md: md0 stopped.
Nov 7 22:22:00 ctrlaltcanc kernel: md: bind<hdd1>
Nov 7 22:22:00 ctrlaltcanc kernel: md: bind<hda1>
Nov 7 22:22:00 ctrlaltcanc kernel: raid1: raid set md0 active with 2
out of 2 mirrors
Nov 7 22:22:00 ctrlaltcanc kernel: md: md2 stopped.
Nov 7 22:22:00 ctrlaltcanc kernel: md: bind<hdd3>
Nov 7 22:22:00 ctrlaltcanc kernel: md: bind<hda3>
Nov 7 22:22:00 ctrlaltcanc kernel: raid1: raid set md2 active with 2
out of 2 mirrors
Nov 7 22:22:00 ctrlaltcanc kernel: md: md3 stopped.
Nov 7 22:22:00 ctrlaltcanc kernel: md: bind<hdd5>
Nov 7 22:22:00 ctrlaltcanc kernel: md: bind<hda5>
Nov 7 22:22:00 ctrlaltcanc kernel: raid1: raid set md3 active with 2
out of 2 mirrors
Nov 7 22:22:00 ctrlaltcanc kernel: md: syncing RAID array md3
Nov 7 22:22:00 ctrlaltcanc kernel: md: minimum _guaranteed_
reconstruction speed: 1000 KB/sec/disc.
Nov 7 22:22:00 ctrlaltcanc kernel: md: using maximum available idle IO
bandwidth (but not more than 200000 KB/sec) for reconstruction.
Nov 7 22:22:00 ctrlaltcanc kernel: md: using 128k window, over a total
of 107715712 blocks.
Nov 7 22:22:00 ctrlaltcanc kernel: md: resuming recovery of md3 from
checkpoint.
Nov 7 22:22:00 ctrlaltcanc kernel: md: md4 stopped.
Nov 7 22:22:00 ctrlaltcanc kernel: md: bind<hdd6>
Nov 7 22:22:00 ctrlaltcanc kernel: md: bind<hda6>
Nov 7 22:22:00 ctrlaltcanc kernel: raid1: raid set md4 active with 2
out of 2 mirrors
Nov 7 22:22:00 ctrlaltcanc kernel: kjournald starting. Commit interval
5 seconds
Nov 7 22:22:00 ctrlaltcanc kernel: EXT3 FS on md0, internal journal
Nov 7 22:22:00 ctrlaltcanc kernel: EXT3-fs: mounted filesystem with
ordered data mode.
Nov 7 22:22:00 ctrlaltcanc kernel: kjournald starting. Commit interval
5 seconds
Nov 7 22:22:00 ctrlaltcanc kernel: EXT3 FS on md3, internal journal
Nov 7 22:22:00 ctrlaltcanc kernel: EXT3-fs: mounted filesystem with
ordered data mode.
Nov 7 22:22:00 ctrlaltcanc kernel: kjournald starting. Commit interval
5 seconds
Nov 7 22:22:00 ctrlaltcanc kernel: EXT3 FS on md4, internal journal
Nov 7 22:22:00 ctrlaltcanc kernel: EXT3-fs: mounted filesystem with
ordered data mode.
Nov 7 22:22:00 ctrlaltcanc kernel: Adding 1461816k swap on /dev/md2.
Priority:-1 extents:1 across:1461816k
Ciao,
Hal
Reply to: