It may be off topic - but for such large filesystems journal check IS a problem. You may look at for ex. ZFS, it doesn't have a need for any journal recovery or fsck on mount (but it may be slower on some performance use cases, please test everything before use).

12.06.2019, 08:30, "Indivar Nair" <[email protected]>:

Thanks, Gang

It is a very large file system - around 600TB.
Could this be why it takes around 5 - 10mins to do journal recovery?

What we do as a workaround is -
- Disable the filesystem resource on startup
- Manually mount it (wait for as long as it takes)
- Then umount it
- Enable filesystem resource

But this doesn't seem like the right approach.

We have tried repairing the Filesystem when a failover happens, but it
has never shown any major corruption.

Regards,


Indivar Nair



On Tue, Jun 11, 2019 at 10:18 AM Gang He <[email protected]> wrote:


 Hi Indivar,

 See my comments inline.

 >>> On 6/11/2019 at 12:10 pm, in message
 <CALuPYL3-+8DBTyd8rRONjY=y8aa64y7W+V=eanfjb+ez4rg...@mail.gmail.com>, Indivar
 Nair <[email protected]> wrote:
 > Hello ...,
 >
 > I have an Active-Passive cluster with two nodes hosting an XFS
 > Filesystem over a CLVM Volume.
 >
 > If a failover happens, the volume is mounted on the other node without
 > a recovery that usually happens to a volume that has not been cleanly
 > unmounted.
 > The FS journal is on the same volume.
 >
 > Now, when we fail it back (with a complete cluster shutdown and
 > restart) on to its original node, it undergoes the automatic recovery.
 >
 > 1.
 > Shouldn't it do an FS recovery during the failover to the other node?
 > Note: The FS journal is on the same volume.
 Usually, file system must do the log recovery during the file system is mounted.

 >
 > 2.
 > Also, the failback usually fails because the FS check takes a
 > considerable amount of time. How do I configure the mount not to fail
 > when an automatic FS check is going on?
 File system introduces a journal to avoiding take too long time for file system recovery.
 If the time is too long, maybe this is a file system problem, e.g. file system is damaged.
 Secondly, you can set the timeout value longer.

 Thanks
 Gang

 >
 > Any help/pointers would be highly appreciated.
 >
 > Thanks.
 >
 > Regards,
 >
 >
 > Indivar Nair
 > _______________________________________________
 > Manage your subscription:
 > https://lists.clusterlabs.org/mailman/listinfo/users
 >
 > ClusterLabs home: https://www.clusterlabs.org/

 _______________________________________________
 Manage your subscription:
 https://lists.clusterlabs.org/mailman/listinfo/users

 ClusterLabs home: https://www.clusterlabs.org/

_______________________________________________
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users

ClusterLabs home: https://www.clusterlabs.org/



____________________________________
Sincerely,
George Melikov

_______________________________________________
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users

ClusterLabs home: https://www.clusterlabs.org/

Reply via email to