maverick has seen the end of its life and is no longer receiving any
updates. Marking the maverick task for this ticket as "Won't Fix".

** Changed in: cluster-agents (Ubuntu Maverick)
       Status: Fix Committed => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to heartbeat in Ubuntu.
https://bugs.launchpad.net/bugs/544051

Title:
  Filesystem start runs fsck on ext4 filesystem

Status in cluster-agents package in Ubuntu:
  Fix Released
Status in heartbeat package in Ubuntu:
  Invalid
Status in cluster-agents source package in Maverick:
  Won't Fix
Status in heartbeat source package in Maverick:
  Invalid

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

  =======

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cluster-agents/+bug/544051/+subscriptions

_______________________________________________
Mailing list: https://launchpad.net/~ubuntu-ha
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~ubuntu-ha
More help   : https://help.launchpad.net/ListHelp

Reply via email to