On Monday 07 August 2006 18:20, lonely wolf wrote:
> in mod normal dupa mdadm -a /dev/hdg2 ar trebui ca la --detail sa obtii
> cam asa ceva (testat acum 30 de sec):[EMAIL PROTECTED] ~]# mdadm /dev/md0 -f
> /dev/hdj1 -r /dev/hdj1
> mdadm: set /dev/hdj1 faulty in /dev/md0
> mdadm: hot removed /dev/hdj1
mdadm /dev/md1 --fail /dev/hdg2
mdadm: set device faulty failed for /dev/hdg2: No such device
fdisk -l /dev/hdg
Disk /dev/hdg: 300.0 GB, 300069052416 bytes
255 heads, 63 sectors/track, 36481 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hdg1 1 33 265041 fd Linux raid autodetect
/dev/hdg2 34 36479 292752495 fd Linux raid autodetect
Computerul este proaspat reboot-at. Ma gandesc ca --fail si --remove nu mai
are rost sa dau, daca /dev/hdg2 este deja "removed".
Daca dau cu --add, asa arata:
mdadm /dev/md1 --add /dev/hdg2
mdadm: hot added /dev/hdg2
mail:~ # mdadm --detail /dev/md1
/dev/md1:
Version : 00.90.00
Creation Time : Fri Mar 3 20:07:00 2006
Raid Level : raid1
Array Size : 292752384 (279.19 GiB 299.78 GB)
Device Size : 292752384 (279.19 GiB 299.78 GB)
Raid Devices : 2
Total Devices : 2
Preferred Minor : 1
Persistence : Superblock is persistent
Update Time : Mon Aug 7 18:34:07 2006
State : dirty, no-errors
Active Devices : 1
Working Devices : 2
Failed Devices : 0
Spare Devices : 1
Rebuild Status : 0% complete
Number Major Minor RaidDevice State
0 33 2 0 active sync /dev/hde2
1 0 0 -1 removed
2 34 2 1 spare /dev/hdg2
UUID : 9d55bd81:f84e3196:46450709:76f3da45
Events : 0.6836788
Ce-i aia dirty, no-errors?
_______________________________________________
RLUG mailing list
[email protected]
http://lists.lug.ro/mailman/listinfo/rlug
