Re: mdctl issues

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

 



Neil,

I have tried the following:

# mdctl -a /dev/md1 /dev/sdb2
# dmesg
trying to hot-add [dev 00:00] to md1 ...
blkdev_open() failed: -19
md: could not lock [dev 00:00], zero-size? Marking faulty.
md: error, md_import_device() returned -22
device sdb2 already used in a RAID array!

# cat /proc/mdstat
Personalities : [raid1]
read_ahead 1024 sectors
md1 : active raid1 sdb2[0] sda2[0] 14133568 blocks [2/1] [U_]
unused devices: <none>

Both disks are identical.  I used 'dd' to duplicate the drives while they were unmounted.  The 'mdctl -C' command you gave me appeared to work fine.

Regards
Tim

>>> Neil Brown <neilb@cse.unsw.edu.au> 02/08/02 01:35PM >>>
On Thursday February 7, Tim.Kent@centrixsystems.com.au wrote:
> Here is the output you requested:

Thanks.
There is something quite sick in that superblock.
The superblock has lots of redundancy in it and it isn't always kept
consistant.

I would recommend that you remake that array with:

 mdctl -C /dev/md1 -l 1 -n 2 /dev/sda2 missing
 mdctl -a /dev/md1 /dev/sdb2

NeilBrown

-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux