Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
On a server which is used to back up (using virtsync) VM images to a volume
running XFS, we encountered a problematic error:
kernel: XFS: possible memory allocation deadlock in kmem_alloc
This appears to be related to block size and fragmentation. Using the xfs_fsr
utility to 'defragment' the file system has resolved the issue. On this system
which is performing incremental updates to large sparse files fragmentation is
an issue and it looks like periodic defrag runs will be needed going forward.
In our use of Informix we preallocate the chunk files and allow but do not
encounter automatic chunk extension. It is my hope that there would be minimal
fragmentation on the XFS file system that the Informix instance would be
hosted on.
This leads to the question though - for anyone using Informix cooked files on
XFS, has any maintenance been required? We are intending to use Informix on
XFS on systems that will be in the field for the next several years, so we are
looking to identify any maintenance considerations in advance.
Any info is appreciated!
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.