Applications mmapping large files from AFS file systems may experience unexpected Segmentation faults or corruption
(Doc ID 2146427.1)
Last updated on FEBRUARY 05, 2019
Applies to:Solaris Operating System - Version 10 3/05 and later
Information in this document applies to any platform.
Must be using AFS file system ( https://www.openafs.org/ )
and not have the following two AFS fixes:
change 12291 - "SOLARIS: support mmap() over 4GiB"
change 12292 - "SOLARIS: corrupted content of mmap'd files over 4GiB"
This document details a hard to diagnose issue which is/was a problem with a 3rd party file system, AFS ( https://www.openafs.org/ ) it is not relevant to native file systems.
Process which mmaps large files such as a debugger ( for example mdb ) may encounter a SIGSEGV when the files reside on an AFS file system but not when the files reside on ZFS or other file system. Solaris' version of cp uses mmap to copy files and copying files may cause the content to become corrupted while using gnu cp or other process to copy the file does not.
The common factor will be the source for the mmapped file will be AFS filesystem and the same activity will work when the file is not on an AFS file system
N/A or moving the files to an AFS file system
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!