Am 02.11.2007 um 10:22 schrieb Neil Brown:
On Friday November 2, ralf@xxxxxxxx wrote:
I have a 5 disk version 1.0 superblock RAID5 which had an internal
bitmap that has been reported to have a size of 299 pages in /proc/
mdstat. For whatever reason I removed this bitmap (mdadm --grow --
bitmap=none) and recreated it afterwards (mdadm --grow --
bitmap=internal). Now it has a reported size of 10 pages.
Do I have a problem?
Not a big problem, but possibly a small problem.
Can you send
mdadm -E /dev/sdg1
as well?
Sure:
# mdadm -E /dev/sdg1
/dev/sdg1:
Magic : a92b4efc
Version : 01
Feature Map : 0x1
Array UUID : e1a335a8:fc0f0626:d70687a6:5d9a9c19
Name : 1
Creation Time : Wed Oct 31 14:30:55 2007
Raid Level : raid5
Raid Devices : 5
Used Dev Size : 625137008 (298.09 GiB 320.07 GB)
Array Size : 2500547584 (1192.35 GiB 1280.28 GB)
Used Size : 625136896 (298.09 GiB 320.07 GB)
Super Offset : 625137264 sectors
State : clean
Device UUID : 95afade2:f2ab8e83:b0c764a0:4732827d
Internal Bitmap : 2 sectors from superblock
Update Time : Fri Nov 2 07:46:38 2007
Checksum : 4ee307b3 - correct
Events : 408088
Layout : left-symmetric
Chunk Size : 128K
Array Slot : 3 (0, 1, failed, 2, 3, 4)
Array State : uuUuu 1 failed
This time I'm getting nervous - Array State failed doesn't sound good!
Regards
Ralf
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
