Skip to contentSkip to conversation

invalid bitmap file superblock: bad magic

DISCUSSION Arkadiusz Miśkiewicz 3 participants 7 messages Mar 8, 2012 MD RAID

lore
Share & tools
lore
#0 lore raw

Hello.

I'm trying to create internal bitmap on freshly created raid1 array on 3.2.6 kernel.

What's going on and how to fix this problem?

[root@setebos ~]# mdadm /dev/md3 --grow --bitmap=internal
mdadm: failed to set internal bitmap. [root@setebos ~]# dmesg|tail -n 16

[10455.564598] mdadm: sending ioctl 1261 to a partition!
[10455.564601] mdadm: sending ioctl 1261 to a partition!
[10455.566566] mdadm: sending ioctl 1261 to a partition!
[10455.566570] mdadm: sending ioctl 1261 to a partition!
[10455.568480] md3: invalid bitmap file superblock: bad magic
[10455.568483] md3: bitmap file superblock:
[10455.568485]          magic: 00000000
[10455.568487]        version: 0
[10455.568489]           uuid: 00000000.00000000.00000000.00000000
[10455.568491]         events: 0
[10455.568492] events cleared: 0
[10455.568494]          state: 00000000
[10455.568495]      chunksize: 0 B
[10455.568497]   daemon sleep: 0s
[10455.568498]      sync size: 0 KB
[10455.568499] max write behind: 0
[root@setebos ~]# mdadm --detail /dev/md3
/dev/md3:
        Version : 1.2

Creation Time : Thu Mar 8 13:54:16 2012
Raid Level : raid1
Array Size : 931760807 (888.60 GiB 954.12 GB)
Used Dev Size : 931760807 (888.60 GiB 954.12 GB)
Raid Devices : 2
Total Devices : 2
Persistence : Superblock is persistent

Update Time : Thu Mar 8 18:46:11 2012
State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0

Name : rescue:3
UUID : 390e347b:c63b1a0e:1ff4f4a5:bc51f5c6
Events : 24

Number Major Minor RaidDevice State
0 8 4 0 active sync /dev/sda4
1 8 20 1 active sync /dev/sdb4
[root@setebos ~]# cat /proc/mdstat
Personalities : [raid1]
md3 : active raid1 sda4[0] sdb4[1]

      931760807 blocks super 1.2 [2/2] [UU]

md1 : active raid1 sda2[0] sdb2[1]

      995904 blocks [2/2] [UU]

md0 : active raid1 sda1[0] sdb1[1]

      3999117 blocks super 1.2 [2/2] [UU]

md2 : active raid1 sda3[0] sdb3[1]

      40000754 blocks super 1.2 [2/2] [UU]
      bitmap: 1/1 pages [4KB], 65536KB chunk

unused devices: <none>
[root@setebos ~]#

Signature · 6 lines
Arkadiusz Miśkiewicz        PLD/Linux Team
arekm / maven.pl            http://ftp.pld-linux.org/
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
#1 lore raw
Quoted 6 lines · Arkadiusz Miśkiewicz

I'm trying to create internal bitmap on freshly created raid1 array on 3.2.6 kernel.

What's going on and how to fix this problem?

[root@setebos ~]# mdadm /dev/md3 --grow --bitmap=internal

Wrong syntax, try:
mdadm --grow /dev/md3 --bitmap=internal

Signature · 5 lines
Kai Stian Olstad
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
#2 lore raw
Quoted 6 lines · Kai Stian Olstad

On Thu, Mar 8, 2012 at 5:11 PM, Arkadiusz Miśkiewicz

Quoted 3 lines · <[email protected]> wrote:

I'm trying to create internal bitmap on freshly created raid1 array on 3.2.6 kernel.

Quoted 6 lines
Quoted 3 lines

What's going on and how to fix this problem?

[root@setebos ~]# mdadm /dev/md3 --grow --bitmap=internal

Wrong syntax, try:
mdadm --grow /dev/md3 --bitmap=internal

Doesn't change anything. The same problem.

Signature · 6 lines
Arkadiusz Miśkiewicz        PLD/Linux Team
arekm / maven.pl            http://ftp.pld-linux.org/
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
#3 lore raw
In reply to Arkadiusz Miśkiewicz
Quoted 6 lines · Arkadiusz Miśkiewicz

Hello.

I'm trying to create internal bitmap on freshly created raid1 array on 3.2.6 kernel.

What's going on and how to fix this problem?

Ehm, I just had to wait ew hours and:

[14558.245586] md3: invalid bitmap file superblock: bad magic
[14558.245589] md3: bitmap file superblock:
[14558.245591]          magic: 00000000
[14558.245593]        version: 0
[14558.245594]           uuid: 00000000.00000000.00000000.00000000
[14558.245596]         events: 0
[14558.245598] events cleared: 0
[14558.245599]          state: 00000000
[14558.245601]      chunksize: 0 B
[14558.245602]   daemon sleep: 0s
[14558.245604]      sync size: 0 KB
[14558.245605] max write behind: 0
[17724.265492] mdadm: sending ioctl 1261 to a partition!
[17724.265495] mdadm: sending ioctl 1261 to a partition!
[17724.271631] mdadm: sending ioctl 1261 to a partition!
[17724.271635] mdadm: sending ioctl 1261 to a partition!
[17724.279829] md3: bitmap file is out of date (0 < 24) -- forcing full 
recovery
[17724.279833] created bitmap (7 pages) for device md3

worked... weird.

Quoted 62 lines

[root@setebos ~]# mdadm /dev/md3 --grow --bitmap=internal
mdadm: failed to set internal bitmap. [root@setebos ~]# dmesg|tail -n 16

[10455.564598] mdadm: sending ioctl 1261 to a partition!
[10455.564601] mdadm: sending ioctl 1261 to a partition!
[10455.566566] mdadm: sending ioctl 1261 to a partition!
[10455.566570] mdadm: sending ioctl 1261 to a partition!
[10455.568480] md3: invalid bitmap file superblock: bad magic
[10455.568483] md3: bitmap file superblock:
[10455.568485]          magic: 00000000
[10455.568487]        version: 0
[10455.568489]           uuid: 00000000.00000000.00000000.00000000
[10455.568491]         events: 0
[10455.568492] events cleared: 0
[10455.568494]          state: 00000000
[10455.568495]      chunksize: 0 B
[10455.568497]   daemon sleep: 0s
[10455.568498]      sync size: 0 KB
[10455.568499] max write behind: 0
[root@setebos ~]# mdadm --detail /dev/md3
/dev/md3:
        Version : 1.2

Creation Time : Thu Mar 8 13:54:16 2012
Raid Level : raid1
Array Size : 931760807 (888.60 GiB 954.12 GB)
Used Dev Size : 931760807 (888.60 GiB 954.12 GB)
Raid Devices : 2
Total Devices : 2
Persistence : Superblock is persistent

Update Time : Thu Mar 8 18:46:11 2012
State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0

Name : rescue:3
UUID : 390e347b:c63b1a0e:1ff4f4a5:bc51f5c6
Events : 24

Number Major Minor RaidDevice State
0 8 4 0 active sync /dev/sda4
1 8 20 1 active sync /dev/sdb4
[root@setebos ~]# cat /proc/mdstat
Personalities : [raid1]
md3 : active raid1 sda4[0] sdb4[1]

      931760807 blocks super 1.2 [2/2] [UU]

md1 : active raid1 sda2[0] sdb2[1]

      995904 blocks [2/2] [UU]

md0 : active raid1 sda1[0] sdb1[1]

      3999117 blocks super 1.2 [2/2] [UU]

md2 : active raid1 sda3[0] sdb3[1]

      40000754 blocks super 1.2 [2/2] [UU]
      bitmap: 1/1 pages [4KB], 65536KB chunk

unused devices: <none>
[root@setebos ~]#

Signature · 6 lines
Arkadiusz Miśkiewicz        PLD/Linux Team
arekm / maven.pl            http://ftp.pld-linux.org/
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
#4 lore raw
In reply to Arkadiusz Miśkiewicz
Quoted 6 lines · On Thu, 8 Mar 2012 17:11:17 +0100 Arkadiusz Miśkiewicz…

Hello.

I'm trying to create internal bitmap on freshly created raid1 array on 3.2.6 kernel.

What's going on and how to fix this problem?

There is a bug in the latest mdadm which causes this. It is fixed in git, or use a slightly older mdadm.

I notice a subsequent email where it magically started working. I cannot explain that - something must have happened to trigger it.

NeilBrown

Quoted 64 lines

[root@setebos ~]# mdadm /dev/md3 --grow --bitmap=internal
mdadm: failed to set internal bitmap. [root@setebos ~]# dmesg|tail -n 16

[10455.564598] mdadm: sending ioctl 1261 to a partition!
[10455.564601] mdadm: sending ioctl 1261 to a partition!
[10455.566566] mdadm: sending ioctl 1261 to a partition!
[10455.566570] mdadm: sending ioctl 1261 to a partition!
[10455.568480] md3: invalid bitmap file superblock: bad magic
[10455.568483] md3: bitmap file superblock:
[10455.568485]          magic: 00000000
[10455.568487]        version: 0
[10455.568489]           uuid: 00000000.00000000.00000000.00000000
[10455.568491]         events: 0
[10455.568492] events cleared: 0
[10455.568494]          state: 00000000
[10455.568495]      chunksize: 0 B
[10455.568497]   daemon sleep: 0s
[10455.568498]      sync size: 0 KB
[10455.568499] max write behind: 0
[root@setebos ~]# mdadm --detail /dev/md3
/dev/md3:
        Version : 1.2

Creation Time : Thu Mar 8 13:54:16 2012
Raid Level : raid1
Array Size : 931760807 (888.60 GiB 954.12 GB)
Used Dev Size : 931760807 (888.60 GiB 954.12 GB)
Raid Devices : 2
Total Devices : 2
Persistence : Superblock is persistent

Update Time : Thu Mar 8 18:46:11 2012
State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0

Name : rescue:3
UUID : 390e347b:c63b1a0e:1ff4f4a5:bc51f5c6
Events : 24

Number Major Minor RaidDevice State
0 8 4 0 active sync /dev/sda4
1 8 20 1 active sync /dev/sdb4
[root@setebos ~]# cat /proc/mdstat
Personalities : [raid1]
md3 : active raid1 sda4[0] sdb4[1]

      931760807 blocks super 1.2 [2/2] [UU]

md1 : active raid1 sda2[0] sdb2[1]

      995904 blocks [2/2] [UU]

md0 : active raid1 sda1[0] sdb1[1]

      3999117 blocks super 1.2 [2/2] [UU]

md2 : active raid1 sda3[0] sdb3[1]

      40000754 blocks super 1.2 [2/2] [UU]
      bitmap: 1/1 pages [4KB], 65536KB chunk

unused devices: <none>
[root@setebos ~]#

#5 lore raw
Quoted 5 lines · NeilBrown

On Thu, 8 Mar 2012 17:11:17 +0100 Arkadiusz Miśkiewicz

Quoted 2 lines · <[email protected]> wrote:

Hello.

Quoted 7 lines
Quoted 4 lines

I'm trying to create internal bitmap on freshly created raid1 array on 3.2.6 kernel.

What's going on and how to fix this problem?

There is a bug in the latest mdadm which causes this. It is fixed in git,

Which commit is that?

Signature · 6 lines
Arkadiusz Miśkiewicz        PLD/Linux Team
arekm / maven.pl            http://ftp.pld-linux.org/
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
#6 lore raw
Quoted 9 lines · On Thu, 8 Mar 2012 21:24:21 +0100 Arkadiusz Miśkiewicz…
Quoted 8 lines · NeilBrown

On Thu, 8 Mar 2012 17:11:17 +0100 Arkadiusz Miśkiewicz

Quoted 5 lines · <[email protected]> wrote:

Hello.

I'm trying to create internal bitmap on freshly created raid1 array on 3.2.6 kernel.

Quoted 7 lines
Quoted 4 lines
Quoted 1 line

What's going on and how to fix this problem?

There is a bug in the latest mdadm which causes this. It is fixed in git,

Which commit is that?

This commit fixes it.

http://neil.brown.name/git?p=mdadm;a=commitdiff;h=6ef89052d85b8137b8a7100f761d896ae6f61001

NeilBrown