Sorry, that was my misunderstanding.
Applying the journals is executed automatically
when the volume is mounted.
fsck is not needed for that purpose.
Kazuki Ohara wrote:
Hi all,
I am using heartbeat-1.2.3.
I have a question about the Filesystem script.
Is there any reason why Filesystem script does not execute fsck to evaluate
shared storage (DRBD or SAN) formatted by ext3 whether storage is
corrupted or
not before standby server mounting it when active server have
encountered some
failure.
Because, some kind of failure may break the metadata of the ext3, and
running
fsck is the only way to apply the ext3 journals before the stanby server
mounts
it.
Why the script doesn't run fsck?
Is there a reason for not using fsck when fail over happens?
Best regards,
Kazuki Ohara
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
--
Kazuki Ohara
Sony Computer Entertainment Inc.
Distributed OS Development Dept.
Japan
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
