Skip to contentSkip to conversation

mdadm -add doesn't start rebuilding array

DISCUSSION Sergiusz Brzeziński 4 participants 10 messages Aug 20, 2012 – Aug 21, 2012 1 message not in the archive MD RAID

lore
Share & tools
lore
#0 lore raw

Hi,

My system is Ubuntu 12.04, kernel 3.2.0-27. mdadm: 3.2.3

If I do:

# mdadm /dev/md0 -a /dev/sdc3

then nothing happen! No message on command line, no info in logs!

Man mdadm says:

-a, --add
hot-add listed devices. If a device appears to have recently been part of the array (possibly it failed or was removed) the device is re-added as describe
in the next point. If that fails or the device was never part of the
array, the device is added as a hot-spare. If the array is degraded, it will immediately start to rebuild data onto that spare.

But array doesn't wont to rebuild.

But not exactly. The bad info is, that sometimes it works and sometimes it doesn't.

And if I restart the system, the array SOMETIMES start rebuilding and somethimes doesn't!

There is no information what's up (comnand line or logs) so I don't know what to do.

I describe bellow the whole procedure:

1.
There ist a working Raid1 array:

# cat /proc/mdstat

Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4] [raid10] md0 : active raid1 sda3[2] sdb3[3]

      115999672 blocks super 1.0 [2/2] [UU]
      bitmap: 0/1 pages [0KB], 65536KB chunk
# mdadm --detail /dev/md0

/dev/md0:

        Version : 1.0

Creation Time : Wed Aug 1 15:45:56 2012
Raid Level : raid1
Array Size : 115999672 (110.63 GiB 118.78 GB)
Used Dev Size : 115999672 (110.63 GiB 118.78 GB)
Raid Devices : 2
Total Devices : 2
Persistence : Superblock is persistent

Intent Bitmap : Internal

Update Time : Mon Aug 20 11:10:00 2012
State : active
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0

Name : linux:0
UUID : b7407176:2e88c73d:2c85e940:05ff7e06
Events : 5897

Number Major Minor RaidDevice State
3 8 19 0 active sync /dev/sdb3
2 8 3 1 active sync /dev/sda3

2.
I remove (phisicaly) the "/dev/sdb" drive of the box (hot-swap)

# cat /proc/mdstat

Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4] [raid10] md0 : active raid1 sda3[2] sdb3[3](F)

      115999672 blocks super 1.0 [2/1] [_U]
      bitmap: 1/1 pages [4KB], 65536KB chunk
# mdadm --detail /dev/md0
/dev/md0:
        Version : 1.0
  Creation Time : Wed Aug  1 15:45:56 2012
     Raid Level : raid1
     Array Size : 115999672 (110.63 GiB 118.78 GB)
  Used Dev Size : 115999672 (110.63 GiB 118.78 GB)
   Raid Devices : 2
  Total Devices : 2
    Persistence : Superblock is persistent

Intent Bitmap : Internal

Update Time : Mon Aug 20 11:11:58 2012
State : active, degraded
Active Devices : 1
Working Devices : 1
Failed Devices : 1
Spare Devices : 0

Name : linux:0
UUID : b7407176:2e88c73d:2c85e940:05ff7e06
Events : 5908

Number Major Minor RaidDevice State
0 0 0 0 removed
2 8 3 1 active sync /dev/sda3

3 8 19 - faulty spare

3.
I insert the drive again - it become "/dev/sdc" instead of "/dev/sdb"

4.
And now I do the following to rebuild the array:

# mdadm /dev/md0 -a /dev/sdc3

mdadm: /dev/sdc3 reports being an active member for /dev/md0, but a --re-add fails.
mdadm: not performing --add as that would convert /dev/sdc3 in to a spare.
mdadm: To make this a spare, use "mdadm --zero-superblock /dev/sdc3" first.

I have never seen this messages before (on another systems). But this is not a problem. I do, what they suggest:

# mdadm --zero-superblock /dev/sdc3
# mdadm --examine /dev/sdc3
mdadm: No md superblock detected on /dev/sdc3.

5.
And now I try again rebuild the array:

# mdadm /dev/md0 -a /dev/sdc3

... and nothing happen! No message, no info. I repeat some times the command.

I also try this:

# mdadm /dev/md0 -a -vv --force /dev/sdc3

... also nothing. Somethimes, if I repeat the command one by one, in logs appear the line:

Aug 20 11:30:52 serwer-linmot kernel: [ 1978.111282] md: export_rdev(sdc3)

... and nothing else

# mdadm --examine /dev/sdc3
/dev/sdc3:
          Magic : a92b4efc
        Version : 1.0
    Feature Map : 0x1
     Array UUID : b7407176:2e88c73d:2c85e940:05ff7e06
           Name : linux:0
  Creation Time : Wed Aug  1 15:45:56 2012
     Raid Level : raid1
   Raid Devices : 2

Avail Dev Size : 231999344 (110.63 GiB 118.78 GB)

     Array Size : 231999344 (110.63 GiB 118.78 GB)

Super Offset : 231999472 sectors
State : clean
Device UUID : f1a1f291:e10d85cc:b574c6d2:45fc0c5d

Internal Bitmap : -8 sectors from superblock
Update Time : Mon Aug 20 11:17:07 2012
Checksum : 71bcac04 - correct
Events : 0

Device Role : spare
Array State : .A ('A' == active, '.' == missing)

# mdadm --detail /dev/md0

/dev/md0:

        Version : 1.0

Creation Time : Wed Aug 1 15:45:56 2012
Raid Level : raid1
Array Size : 115999672 (110.63 GiB 118.78 GB)
Used Dev Size : 115999672 (110.63 GiB 118.78 GB)
Raid Devices : 2
Total Devices : 2
Persistence : Superblock is persistent

Intent Bitmap : Internal

Update Time : Mon Aug 20 11:18:43 2012
State : active, degraded
Active Devices : 1
Working Devices : 1
Failed Devices : 1
Spare Devices : 0

Name : linux:0
UUID : b7407176:2e88c73d:2c85e940:05ff7e06
Events : 5946

Number Major Minor RaidDevice State
0 0 0 0 removed
2 8 3 1 active sync /dev/sda3

3 8 19 - faulty spare

Can anyone help?

many thanks in advance

Sergiusz Brzeziński

--
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 206 lines · On Mon, 20 Aug 2012 11:36:10 +0200 Sergiusz Brzeziński…

Hi,

My system is Ubuntu 12.04, kernel 3.2.0-27. mdadm: 3.2.3

If I do:

# mdadm /dev/md0 -a /dev/sdc3

then nothing happen! No message on command line, no info in logs!

Man mdadm says:

-a, --add
hot-add listed devices. If a device appears to have recently been part of the array (possibly it failed or was removed) the device is re-added as describe
in the next point. If that fails or the device was never part of the
array, the device is added as a hot-spare. If the array is degraded, it will immediately start to rebuild data onto that spare.

But array doesn't wont to rebuild.

But not exactly. The bad info is, that sometimes it works and sometimes it doesn't.

And if I restart the system, the array SOMETIMES start rebuilding and somethimes doesn't!

There is no information what's up (comnand line or logs) so I don't know what to do.

I describe bellow the whole procedure:

1.
There ist a working Raid1 array:

# cat /proc/mdstat

Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4] [raid10]
md0 : active raid1 sda3[2] sdb3[3]

       115999672 blocks super 1.0 [2/2] [UU]
       bitmap: 0/1 pages [0KB], 65536KB chunk
# mdadm --detail /dev/md0

/dev/md0:

         Version : 1.0

Creation Time : Wed Aug 1 15:45:56 2012
Raid Level : raid1
Array Size : 115999672 (110.63 GiB 118.78 GB)
Used Dev Size : 115999672 (110.63 GiB 118.78 GB)
Raid Devices : 2
Total Devices : 2
Persistence : Superblock is persistent

Intent Bitmap : Internal

Update Time : Mon Aug 20 11:10:00 2012
State : active
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0

Name : linux:0
UUID : b7407176:2e88c73d:2c85e940:05ff7e06
Events : 5897

Number Major Minor RaidDevice State
3 8 19 0 active sync /dev/sdb3
2 8 3 1 active sync /dev/sda3

2.
I remove (phisicaly) the "/dev/sdb" drive of the box (hot-swap)

# cat /proc/mdstat

Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4] [raid10]
md0 : active raid1 sda3[2] sdb3[3](F)

       115999672 blocks super 1.0 [2/1] [_U]
       bitmap: 1/1 pages [4KB], 65536KB chunk
# mdadm --detail /dev/md0
/dev/md0:
         Version : 1.0
   Creation Time : Wed Aug  1 15:45:56 2012
      Raid Level : raid1
      Array Size : 115999672 (110.63 GiB 118.78 GB)
   Used Dev Size : 115999672 (110.63 GiB 118.78 GB)
    Raid Devices : 2
   Total Devices : 2
     Persistence : Superblock is persistent

Intent Bitmap : Internal

Update Time : Mon Aug 20 11:11:58 2012
State : active, degraded
Active Devices : 1
Working Devices : 1
Failed Devices : 1
Spare Devices : 0

Name : linux:0
UUID : b7407176:2e88c73d:2c85e940:05ff7e06
Events : 5908

Number Major Minor RaidDevice State
0 0 0 0 removed
2 8 3 1 active sync /dev/sda3

3 8 19 - faulty spare

3.
I insert the drive again - it become "/dev/sdc" instead of "/dev/sdb"

4.
And now I do the following to rebuild the array:

# mdadm /dev/md0 -a /dev/sdc3

mdadm: /dev/sdc3 reports being an active member for /dev/md0, but a --re-add fails.
mdadm: not performing --add as that would convert /dev/sdc3 in to a spare.
mdadm: To make this a spare, use "mdadm --zero-superblock /dev/sdc3" first.

I have never seen this messages before (on another systems). But this is not a problem. I do, what they suggest:

# mdadm --zero-superblock /dev/sdc3
# mdadm --examine /dev/sdc3
mdadm: No md superblock detected on /dev/sdc3.

5.
And now I try again rebuild the array:

# mdadm /dev/md0 -a /dev/sdc3

... and nothing happen! No message, no info. I repeat some times the command.

I also try this:

# mdadm /dev/md0 -a -vv --force /dev/sdc3

... also nothing. Somethimes, if I repeat the command one by one, in logs appear the line:

Aug 20 11:30:52 serwer-linmot kernel: [ 1978.111282] md: export_rdev(sdc3)

... and nothing else

# mdadm --examine /dev/sdc3
/dev/sdc3:
           Magic : a92b4efc
         Version : 1.0
     Feature Map : 0x1
      Array UUID : b7407176:2e88c73d:2c85e940:05ff7e06
            Name : linux:0
   Creation Time : Wed Aug  1 15:45:56 2012
      Raid Level : raid1
    Raid Devices : 2

Avail Dev Size : 231999344 (110.63 GiB 118.78 GB)

      Array Size : 231999344 (110.63 GiB 118.78 GB)
    Super Offset : 231999472 sectors
           State : clean
     Device UUID : f1a1f291:e10d85cc:b574c6d2:45fc0c5d

Internal Bitmap : -8 sectors from superblock
Update Time : Mon Aug 20 11:17:07 2012
Checksum : 71bcac04 - correct
Events : 0

Device Role : spare
Array State : .A ('A' == active, '.' == missing)

# mdadm --detail /dev/md0

/dev/md0:

         Version : 1.0

Creation Time : Wed Aug 1 15:45:56 2012
Raid Level : raid1
Array Size : 115999672 (110.63 GiB 118.78 GB)
Used Dev Size : 115999672 (110.63 GiB 118.78 GB)
Raid Devices : 2
Total Devices : 2
Persistence : Superblock is persistent

Intent Bitmap : Internal

Update Time : Mon Aug 20 11:18:43 2012
State : active, degraded
Active Devices : 1
Working Devices : 1
Failed Devices : 1
Spare Devices : 0

Name : linux:0
UUID : b7407176:2e88c73d:2c85e940:05ff7e06
Events : 5946

Quoted 9 lines

Number Major Minor RaidDevice State
0 0 0 0 removed
2 8 3 1 active sync /dev/sda3

3 8 19 - faulty spare

Can anyone help?

I cannot see why that would happen.
It seems to be failing somewhere in bind_rdev_to_array, but I don't know where.
Can you run
strace -o /tmp/strace mdadm /dev/md0 --add /dev/sdc3
and post the output ... or at last the tail end of the output. There should be an ioctl which fails and I need to know what the error was (EEXIST, EINVAL, ENOSPC are the likely ones). But don't just post that line, include at least the last 100 lines.

NeilBrown

A message that is not in the archive (sent off-list or not yet received): [email protected]

#3 lore raw
Quoted 232 lines · On Tue, 21 Aug 2012 08:45:50 +0200 Sergiusz Brzeziński…

W dniu 21.08.2012 00:30, NeilBrown pisze:

Quoted 229 lines
Quoted 206 lines · On Mon, 20 Aug 2012 11:36:10 +0200 Sergiusz Brzeziński…

Hi,

My system is Ubuntu 12.04, kernel 3.2.0-27. mdadm: 3.2.3

If I do:

# mdadm /dev/md0 -a /dev/sdc3

then nothing happen! No message on command line, no info in logs!

Man mdadm says:

-a, --add
hot-add listed devices. If a device appears to have recently been part of the array (possibly it failed or was removed) the device is re-added as describe
in the next point. If that fails or the device was never part of the
array, the device is added as a hot-spare. If the array is degraded, it will immediately start to rebuild data onto that spare.

But array doesn't wont to rebuild.

But not exactly. The bad info is, that sometimes it works and sometimes it doesn't.

And if I restart the system, the array SOMETIMES start rebuilding and somethimes doesn't!

There is no information what's up (comnand line or logs) so I don't know what to do.

I describe bellow the whole procedure:

1.
There ist a working Raid1 array:

# cat /proc/mdstat

Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4] [raid10]
md0 : active raid1 sda3[2] sdb3[3]

        115999672 blocks super 1.0 [2/2] [UU]
        bitmap: 0/1 pages [0KB], 65536KB chunk
# mdadm --detail /dev/md0

/dev/md0:
Version : 1.0
Creation Time : Wed Aug 1 15:45:56 2012
Raid Level : raid1
Array Size : 115999672 (110.63 GiB 118.78 GB)
Used Dev Size : 115999672 (110.63 GiB 118.78 GB)
Raid Devices : 2
Total Devices : 2
Persistence : Superblock is persistent

Intent Bitmap : Internal

Update Time : Mon Aug 20 11:10:00 2012
State : active
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0

Name : linux:0
UUID : b7407176:2e88c73d:2c85e940:05ff7e06
Events : 5897

Number Major Minor RaidDevice State
3 8 19 0 active sync /dev/sdb3
2 8 3 1 active sync /dev/sda3

2.
I remove (phisicaly) the "/dev/sdb" drive of the box (hot-swap)

# cat /proc/mdstat

Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4] [raid10]
md0 : active raid1 sda3[2] sdb3[3](F)

        115999672 blocks super 1.0 [2/1] [_U]
        bitmap: 1/1 pages [4KB], 65536KB chunk
# mdadm --detail /dev/md0
/dev/md0:
          Version : 1.0
    Creation Time : Wed Aug  1 15:45:56 2012
       Raid Level : raid1
       Array Size : 115999672 (110.63 GiB 118.78 GB)
    Used Dev Size : 115999672 (110.63 GiB 118.78 GB)
     Raid Devices : 2
    Total Devices : 2
      Persistence : Superblock is persistent

Intent Bitmap : Internal

Update Time : Mon Aug 20 11:11:58 2012
State : active, degraded
Active Devices : 1
Working Devices : 1
Failed Devices : 1
Spare Devices : 0

Name : linux:0
UUID : b7407176:2e88c73d:2c85e940:05ff7e06
Events : 5908

Number Major Minor RaidDevice State
0 0 0 0 removed
2 8 3 1 active sync /dev/sda3

3 8 19 - faulty spare

3.
I insert the drive again - it become "/dev/sdc" instead of "/dev/sdb"

4.
And now I do the following to rebuild the array:

# mdadm /dev/md0 -a /dev/sdc3

mdadm: /dev/sdc3 reports being an active member for /dev/md0, but a --re-add fails.
mdadm: not performing --add as that would convert /dev/sdc3 in to a spare.
mdadm: To make this a spare, use "mdadm --zero-superblock /dev/sdc3" first.

I have never seen this messages before (on another systems). But this is not a problem. I do, what they suggest:

# mdadm --zero-superblock /dev/sdc3
# mdadm --examine /dev/sdc3
mdadm: No md superblock detected on /dev/sdc3.

5.
And now I try again rebuild the array:

# mdadm /dev/md0 -a /dev/sdc3

... and nothing happen! No message, no info. I repeat some times the command.

I also try this:

# mdadm /dev/md0 -a -vv --force /dev/sdc3

... also nothing. Somethimes, if I repeat the command one by one, in logs appear the line:

Aug 20 11:30:52 serwer-linmot kernel: [ 1978.111282] md: export_rdev(sdc3)

... and nothing else

# mdadm --examine /dev/sdc3
/dev/sdc3:
            Magic : a92b4efc
          Version : 1.0
      Feature Map : 0x1
       Array UUID : b7407176:2e88c73d:2c85e940:05ff7e06
             Name : linux:0
    Creation Time : Wed Aug  1 15:45:56 2012
       Raid Level : raid1
     Raid Devices : 2
   Avail Dev Size : 231999344 (110.63 GiB 118.78 GB)
       Array Size : 231999344 (110.63 GiB 118.78 GB)
     Super Offset : 231999472 sectors
            State : clean
      Device UUID : f1a1f291:e10d85cc:b574c6d2:45fc0c5d

Internal Bitmap : -8 sectors from superblock
Update Time : Mon Aug 20 11:17:07 2012
Checksum : 71bcac04 - correct
Events : 0

Device Role : spare
Array State : .A ('A' == active, '.' == missing)

# mdadm --detail /dev/md0

/dev/md0:
Version : 1.0
Creation Time : Wed Aug 1 15:45:56 2012
Raid Level : raid1
Array Size : 115999672 (110.63 GiB 118.78 GB)
Used Dev Size : 115999672 (110.63 GiB 118.78 GB)
Raid Devices : 2
Total Devices : 2
Persistence : Superblock is persistent

Intent Bitmap : Internal

Update Time : Mon Aug 20 11:18:43 2012
State : active, degraded
Active Devices : 1
Working Devices : 1
Failed Devices : 1
Spare Devices : 0

Name : linux:0
UUID : b7407176:2e88c73d:2c85e940:05ff7e06
Events : 5946

Quoted 9 lines

Number Major Minor RaidDevice State
0 0 0 0 removed
2 8 3 1 active sync /dev/sda3

3 8 19 - faulty spare

Can anyone help?

I cannot see why that would happen.
It seems to be failing somewhere in bind_rdev_to_array, but I don't know where.
Can you run
strace -o /tmp/strace mdadm /dev/md0 --add /dev/sdc3
and post the output ... or at last the tail end of the output. There should be an ioctl which fails and I need to know what the error was (EEXIST, EINVAL, ENOSPC are the likely ones). But don't just post that line, include at least the last 100 lines.

Quoted 9 lines
Quoted 1 line

NeilBrown

Hi,

Thank You for help. The complete strace output is in attachement.

Sergiusz

lseek(4, 118783725568, SEEK_SET) = 118783725568
ioctl(4, BLKSSZGET, 0x7fff73de3fec) = 0
write(4, "bitm\4\0\0\0\267@qv.\210\307=,\205\351@\5\377~\6\303-\0\0\0\0\0\0"..., 512) = -1 EINVAL (Invalid argument)

Oh, I remember now. That bug.
Fixed by commit 6ef89052d85b8137b8a7100f which is in 3.2.4.

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

NeilBrown

#4 lore raw
Quoted 19 lines · NeilBrown
Quoted 11 lines · On Tue, 21 Aug 2012 08:45:50 +0200 Sergiusz Brzeziński…

W dniu 21.08.2012 00:30, NeilBrown pisze:

Quoted 7 lines
Quoted 4 lines · On Mon, 20 Aug 2012 11:36:10 +0200 Sergiusz Brzeziński…

Hi,

My system is Ubuntu 12.04, kernel 3.2.0-27. mdadm: 3.2.3

lseek(4, 118783725568, SEEK_SET) = 118783725568
ioctl(4, BLKSSZGET, 0x7fff73de3fec) = 0
write(4, "bitm\4\0\0\0\267@qv.\210\307=,\205\351@\5\377~\6\303-\0\0\0\0\0\0"..., 512) = -1 EINVAL (Invalid argument)

Quoted 8 lines

Oh, I remember now. That bug.
Fixed by commit 6ef89052d85b8137b8a7100f which is in 3.2.4.

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

NeilBrown

Ubuntu 12.04 has 3.2.5-1ubuntu0.2 in updates pocket. Please update your system and see if that helps?

Signature · 6 lines
Regards,
Dmitrijs.
--
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
#5 lore raw

Hi,

Yes! After ugrading to 3.2.5 it started working.

Sorry, I didn't first check if there is a newer version of mdadm. We would not waste time for this problem.

thank You

Sergiusz

W dniu 21.08.2012 10:25, Dmitrijs Ledkovs pisze:

Quoted 23 lines · NeilBrown
Quoted 22 lines
Quoted 11 lines · On Tue, 21 Aug 2012 08:45:50 +0200 Sergiusz Brzeziński…

W dniu 21.08.2012 00:30, NeilBrown pisze:

Quoted 7 lines
Quoted 4 lines · On Mon, 20 Aug 2012 11:36:10 +0200 Sergiusz Brzeziński…

Hi,

My system is Ubuntu 12.04, kernel 3.2.0-27. mdadm: 3.2.3

lseek(4, 118783725568, SEEK_SET) = 118783725568
ioctl(4, BLKSSZGET, 0x7fff73de3fec) = 0
write(4, "bitm\4\0\0\0\267@qv.\210\307=,\205\351@\5\377~\6\303-\0\0\0\0\0\0"..., 512) = -1 EINVAL (Invalid argument)

Oh, I remember now. That bug.
Fixed by commit 6ef89052d85b8137b8a7100f which is in 3.2.4.

Quoted 9 lines
Quoted 5 lines

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

NeilBrown

Ubuntu 12.04 has 3.2.5-1ubuntu0.2 in updates pocket. Please update your system and see if that helps?

--
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 5 lines · Sergiusz Brzeziński

Hi,

Yes! After ugrading to 3.2.5 it started working.

Sorry, I didn't first check if there is a newer version of mdadm. We would not waste time for this problem.

It's still in proposed-updates, right? I entered information in the ubuntu bugzilla regarding these problems and asked for the 3.2.5 to be pushed out, but I haven't seen any more activity after that (this was a few weeks ago, I was hit by the exact same bug a while ago).

Signature · 1 line
Mikael Abrahamsson    email: [email protected]
#7 lore raw

W dniu 21.08.2012 12:19, Mikael Abrahamsson pisze:

Quoted 6 lines · Sergiusz Brzeziński
Quoted 5 lines

Hi,

Yes! After ugrading to 3.2.5 it started working.

Quoted 8 lines
Quoted 2 lines

Sorry, I didn't first check if there is a newer version of mdadm. We would not waste time for this problem.

It's still in proposed-updates, right? I entered information in the ubuntu bugzilla regarding these problems and asked for the 3.2.5 to be pushed out, but I haven't seen any more activity after that (this was a few weeks ago, I was hit by the exact same bug a while ago).

Hi,

I just installed it from synaptics. Don't know from which source :) In packet properties there is an information about available versions:
"3.2.5-1ubuntu0.2 (precise-updates)"

Sergiusz
--
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

#8 lore raw
In reply to Mikael Abrahamsson
Quoted 6 lines · Mikael Abrahamsson
Quoted 4 lines · Sergiusz Brzeziński

Hi,

Yes! After ugrading to 3.2.5 it started working.

Quoted 8 lines
Quoted 2 lines

Sorry, I didn't first check if there is a newer version of mdadm. We would not waste time for this problem.

It's still in proposed-updates, right? I entered information in the ubuntu bugzilla regarding these problems and asked for the 3.2.5 to be pushed out, but I haven't seen any more activity after that (this was a few weeks ago, I was hit by the exact same bug a while ago).

https://launchpad.net/ubuntu/+source/mdadm/+publishinghistory

Says it was copied from proposed pocket into updates on

2012-08-13 21:03:40 BST

Ubuntu does not use bugzilla. Can you give me a URL where you logged such request?

Run apt-get update and/or use a more up to date mirror?

Signature · 6 lines
Regards,
Dmitrijs.
--
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
#9 lore raw

W dniu 21.08.2012 12:55, Dmitrijs Ledkovs pisze:

Quoted 18 lines · Mikael Abrahamsson
Quoted 6 lines · Sergiusz Brzeziński
Quoted 5 lines

Hi,

Yes! After ugrading to 3.2.5 it started working.

Quoted 8 lines
Quoted 2 lines

Sorry, I didn't first check if there is a newer version of mdadm. We would not waste time for this problem.

It's still in proposed-updates, right? I entered information in the ubuntu bugzilla regarding these problems and asked for the 3.2.5 to be pushed out, but I haven't seen any more activity after that (this was a few weeks ago, I was hit by the exact same bug a while ago).

https://launchpad.net/ubuntu/+source/mdadm/+publishinghistory

Quoted 9 lines

Says it was copied from proposed pocket into updates on

2012-08-13 21:03:40 BST

Ubuntu does not use bugzilla. Can you give me a URL where you logged such request?

Run apt-get update and/or use a more up to date mirror?

I used synaptics (gui front-end) to install the package.

And in my /etc/apt/sources.list is:

deb http://pl.archive.ubuntu.com/ubuntu/ precise main restricted
deb-src http://pl.archive.ubuntu.com/ubuntu/ precise main restricted
deb http://pl.archive.ubuntu.com/ubuntu/ precise-updates main restricted
deb-src http://pl.archive.ubuntu.com/ubuntu/ precise-updates main restricted
deb http://pl.archive.ubuntu.com/ubuntu/ precise universe
deb-src http://pl.archive.ubuntu.com/ubuntu/ precise universe
deb http://pl.archive.ubuntu.com/ubuntu/ precise-updates universe
deb-src http://pl.archive.ubuntu.com/ubuntu/ precise-updates universe
deb http://pl.archive.ubuntu.com/ubuntu/ precise multiverse
deb-src http://pl.archive.ubuntu.com/ubuntu/ precise multiverse
deb http://pl.archive.ubuntu.com/ubuntu/ precise-updates multiverse
deb-src http://pl.archive.ubuntu.com/ubuntu/ precise-updates multiverse
deb http://pl.archive.ubuntu.com/ubuntu/ precise-backports main restricted universe multiverse deb-src http://pl.archive.ubuntu.com/ubuntu/ precise-backports main restricted universe multiverse deb http://security.ubuntu.com/ubuntu precise-security main restricted
deb-src http://security.ubuntu.com/ubuntu precise-security main restricted
deb http://security.ubuntu.com/ubuntu precise-security universe
deb-src http://security.ubuntu.com/ubuntu precise-security universe
deb http://security.ubuntu.com/ubuntu precise-security multiverse
deb-src http://security.ubuntu.com/ubuntu precise-security multiverse
deb http://extras.ubuntu.com/ubuntu precise main
deb-src http://extras.ubuntu.com/ubuntu precise main
deb http://pl.archive.ubuntu.com/ubuntu/ precise-proposed restricted main multiverse universe

Sergiusz

--
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

#10 lore raw
In reply to Dmitrijs Ledkovs
Quoted 7 lines · Dmitrijs Ledkovs

https://launchpad.net/ubuntu/+source/mdadm/+publishinghistory

Says it was copied from proposed pocket into updates on

2012-08-13 21:03:40 BST

Ubuntu does not use bugzilla. Can you give me a URL where you logged such request?

I meant launchpad, not bugzilla.

Quoted 1 line

Run apt-get update and/or use a more up to date mirror?

I installed it directly from proposed-updates at the time (downloaded and did dpkg -i), but thinking of it I think I got another version via regular apt-get dist-upgrade a while back, so that's probably after it was released into updates on the 13:th. Thanks for the info!

Signature · 1 line
Mikael Abrahamsson    email: [email protected]