Hi,
Test case: set up a cluster drbd, create an ext4 cluster filesystem on a
drbd device. Perform a hard takeover by switching off the active node.
The fsck command is run every time when the Filesystem is started, e.g.
even when a takeover to another cluster node occurs. This can take a
long time and must not happen.
In particular, the comment in lines 424/425 of the script reads
# NOTE: Some filesystem types don't need this step... Please modify
# accordingly
It is line 435 that needs to be changed to include ext4 (and eventually
other journaling filesystems like btrfs)
--
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:
Confirmed
Status in “heartbeat” package in Ubuntu:
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.
_______________________________________________
Mailing list: https://launchpad.net/~ubuntu-ha
Post to : [email protected]
Unsubscribe : https://launchpad.net/~ubuntu-ha
More help : https://help.launchpad.net/ListHelp
