| 2010-03-22 10:11:54 |
Rainer Schöpf |
bug |
|
|
added bug |
| 2011-04-14 11:44:31 |
krims0n |
bug |
|
|
added subscriber krims0n |
| 2011-04-14 19:36:08 |
Andres Rodriguez |
heartbeat (Ubuntu): status |
New |
Invalid |
|
| 2011-04-14 19:36:18 |
Andres Rodriguez |
bug task added |
|
cluster-agents (Ubuntu) |
|
| 2011-04-14 19:55:35 |
Andres Rodriguez |
cluster-agents (Ubuntu): status |
New |
Confirmed |
|
| 2011-04-14 19:55:38 |
Andres Rodriguez |
cluster-agents (Ubuntu): importance |
Undecided |
Low |
|
| 2011-04-18 18:05:23 |
Andres Rodriguez |
description |
Binary package hint: heartbeat-common
Package heartbeat-common 2.99.2+sles11r9-5ubuntu1 in karmic contains a critical bug:
The script
/usr/lib/ocf/resource.d/heartbeat/Filesystem
contains a list of filesystem types for which fsck is not run. This list does not include ext4, although it does include ext3. |
Binary package hint: heartbeat-common
Package heartbeat-common 2.99.2+sles11r9-5ubuntu1 in karmic contains a critical bug:
The script
/usr/lib/ocf/resource.d/heartbeat/Filesystem
contains a list of filesystem types for which fsck is not run. This list does not include ext4, although it does include ext3.
=======
SRU Justification
IMPACT:
This bug affects users running DRBD clusters with ext4 filesystem on top. Every time that a cluster node tries to perform a takeover on a DRBD resource with ext4 filesystem, it will run fsck, which can cause the takeover to take much longer than expected. In Clustered scenarios, this might affect the availability. For this reason, some filesystems avoid this step, including ext3. Unfortunately, ext4 is not yet listed in the version for Maverick.
REPRODUCE:
1. Install a two node DRBD cluster with Pacemaker. Format the DRBD block device with ext4.
2. Once they are configured and running in Master/Slave, perform a hard takeover by switching off the Master node.
3. In the Slave node, check syslog, where the following output will appear:
lrmd: [2623]: info: RA output: (res_fs:start:stdout) fsck from util-linux-ng 2.17.2
HOW FIXED:
The fix is simple, and consists on adding ext4|ext4dev to the list of filesystems for which to avoid performing fsck.
PATCH:
Attached. Uploaded to maverick-proposed for review there.
REGRESSION POTENTIAL:
Minimal. I've tested this thoroughly.
======= |
|
| 2011-04-18 18:05:49 |
Andres Rodriguez |
nominated for series |
|
Ubuntu Maverick |
|
| 2011-04-18 18:05:49 |
Andres Rodriguez |
bug task added |
|
cluster-agents (Ubuntu Maverick) |
|
| 2011-04-18 18:05:49 |
Andres Rodriguez |
bug task added |
|
heartbeat (Ubuntu Maverick) |
|
| 2011-04-18 18:05:56 |
Andres Rodriguez |
cluster-agents (Ubuntu): status |
Confirmed |
Fix Released |
|
| 2011-04-18 18:06:00 |
Andres Rodriguez |
cluster-agents (Ubuntu Maverick): status |
New |
Confirmed |
|
| 2011-04-18 18:06:03 |
Andres Rodriguez |
cluster-agents (Ubuntu Maverick): importance |
Undecided |
Medium |
|
| 2011-04-18 18:06:08 |
Andres Rodriguez |
heartbeat (Ubuntu Maverick): status |
New |
Invalid |
|
| 2011-04-18 18:06:41 |
Andres Rodriguez |
description |
Binary package hint: heartbeat-common
Package heartbeat-common 2.99.2+sles11r9-5ubuntu1 in karmic contains a critical bug:
The script
/usr/lib/ocf/resource.d/heartbeat/Filesystem
contains a list of filesystem types for which fsck is not run. This list does not include ext4, although it does include ext3.
=======
SRU Justification
IMPACT:
This bug affects users running DRBD clusters with ext4 filesystem on top. Every time that a cluster node tries to perform a takeover on a DRBD resource with ext4 filesystem, it will run fsck, which can cause the takeover to take much longer than expected. In Clustered scenarios, this might affect the availability. For this reason, some filesystems avoid this step, including ext3. Unfortunately, ext4 is not yet listed in the version for Maverick.
REPRODUCE:
1. Install a two node DRBD cluster with Pacemaker. Format the DRBD block device with ext4.
2. Once they are configured and running in Master/Slave, perform a hard takeover by switching off the Master node.
3. In the Slave node, check syslog, where the following output will appear:
lrmd: [2623]: info: RA output: (res_fs:start:stdout) fsck from util-linux-ng 2.17.2
HOW FIXED:
The fix is simple, and consists on adding ext4|ext4dev to the list of filesystems for which to avoid performing fsck.
PATCH:
Attached. Uploaded to maverick-proposed for review there.
REGRESSION POTENTIAL:
Minimal. I've tested this thoroughly.
======= |
Binary package hint: heartbeat-common
Package heartbeat-common 2.99.2+sles11r9-5ubuntu1 in karmic contains a critical bug:
The script
/usr/lib/ocf/resource.d/heartbeat/Filesystem
contains a list of filesystem types for which fsck is not run. This list does not include ext4, although it does include ext3.
=======
SRU Justification
IMPACT:
This bug affects users running DRBD clusters with ext4 filesystem on top. Every time that a cluster node tries to perform a takeover on a DRBD resource with ext4 filesystem, it will run fsck, which can cause the takeover to take much longer than expected. In Clustered scenarios, this might affect the availability. For this reason, some filesystems avoid this step, including ext3. Unfortunately, ext4 is not yet listed in the version for Maverick.
REPRODUCE:
1. Install a two node DRBD cluster with Pacemaker. Format the DRBD block device with ext4.
2. Once they are configured and running in Master/Slave, perform a hard takeover by switching off the Master node.
3. In the Slave node, check syslog, where the following output will appear:
lrmd: [2623]: info: RA output: (res_fs:start:stdout) fsck from util-linux-ng 2.17.2
HOW FIXED:
The fix is simple, and consists on adding ext4|ext4dev to the list of filesystems for which to avoid performing fsck. This has been fixed upstream (and in Natty) and it is the same approach.
PATCH:
Attached. Uploaded to maverick-proposed for review there.
REGRESSION POTENTIAL:
Minimal. I've tested this thoroughly.
======= |
|
| 2011-04-18 18:07:40 |
Andres Rodriguez |
cluster-agents (Ubuntu): importance |
Low |
Undecided |
|
| 2011-04-18 18:08:24 |
Andres Rodriguez |
attachment added |
|
cluster-agents.debdiff https://bugs.launchpad.net/ubuntu/+source/cluster-agents/+bug/544051/+attachment/2062195/+files/cluster-agents.debdiff |
|
| 2011-04-18 18:10:43 |
Andres Rodriguez |
bug |
|
|
added subscriber Andres Rodriguez |
| 2011-04-18 18:10:54 |
Andres Rodriguez |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2011-04-19 07:21:27 |
Martin Pitt |
cluster-agents (Ubuntu Maverick): status |
Confirmed |
Fix Committed |
|
| 2011-04-19 07:21:31 |
Martin Pitt |
bug |
|
|
added subscriber SRU Verification |
| 2011-04-19 07:21:35 |
Martin Pitt |
tags |
|
verification-needed |
|
| 2011-04-19 08:12:22 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/maverick-proposed/cluster-agents |
|
| 2014-12-03 08:13:27 |
Rolf Leggewie |
cluster-agents (Ubuntu Maverick): status |
Fix Committed |
Won't Fix |
|
