CC our file system people Jeff to this loop.
>From my view, I feel the file system recovery time usually depends on file
>system journal size, not file system size.
Hello Jeff, do you think XFS will take 5 ~ 10 mins during the mounting after a
uncleanly switch.
Thanks
Gang
>>> On 6/12/2019 at
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"
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
Hi Indivar,
See my comments inline.
>>> On 6/11/2019 at 12:10 pm, in message
, Indivar
Nair 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
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.
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.
