On 2018-05-21 14:40, Roger Oberholtzer wrote:
On Mon, May 21, 2018 at 1:51 PM, Carlos E. R. <> wrote:
On 2018-05-21 13:14, Roger Oberholtzer wrote:
On Mon, May 21, 2018 at 12:57 PM, Roger Oberholtzer <> wrote:
As Dave mentions, maybe you should also format those disks to have the latest updates to the filesystem available. Or, perhaps better, create a test system with leap 15.0 and newly formatted xfs disks.
We use Leap 42.3 in production. So we want to stay with that here.
Yes, that a good reason. But Leap 15.0 has a newer kernel, might behave differently for this task. I would test it. And 42.3 will be EOL in few months.
We can try re-formatting the disks. I suspect it makes no difference as it is not a file system type thing. Meaning that ext4, xfs, etc do not implement this. It is the general file system stuff in the kernel that seems to manage this.
Then I would ask on the xfs thread. I don't remember if you did so when the original thread arose.
I asked when this first happened. We discovered that the same thing happened for all file system types. The memory cache is a general file system feature that, it seems, all file systems share.
Ah, then if they said that, there is little hope that a difference in the disk format would help. I wonder is there is a mount option that would help? A commit timeout? Nevertheless, the XFS people have been very active and have done changes to the filesystem. Now that I think, I do not know if it is possible to update the filesystem "online". -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)