[LOG4J2-2012] No compression when using a separate drive in Linux

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.7
• Fix Version/s: 2.9.0
• Component/s: Core

Environment

Unix

• Assignee: Unassigned
• Reporter: Benjamin Jaton
• Created: 14/Aug/17 22:50
• Updated: 31/Jan/20 23:37
• Resolved: 24/Aug/17 05:52

Description

When setting up the filePattern of a RollingFileAppender pointing to a different FS than the fileName, the file gets moved but not compressed:

In this example, /usr/local and /archives are not on the same FS:

2017-08-11 14:34:33,632 pool-8-thread-1 TRACE DefaultRolloverStrategy.purge() took 15.0 milliseconds 
2017-08-11 14:34:33,643 pool-8-thread-1 DEBUG RollingFileManager executing synchronous FileRenameAction[/usr/local/app/logs/app.log to /archives/logs/app-2017-08-11_14-34-33.log, renameEmptyFiles=false] 
2017-08-11 14:34:33,646 pool-8-thread-1 ERROR Unable to move file /usr/local/app/logs/app.log to /archives/logs/app-2017-08-11_14-34-33.log: java.nio.file.AtomicMoveNotSupportedException /usr/local/app/logs/app.log -> /archives/logs/app-2017-08-11_14-34-33.log: Invalid cross-device link 
2017-08-11 14:34:33,736 pool-8-thread-1 TRACE Renamed file /usr/local/app/logs/app.log to /archives/logs/app-2017-08-11_14-34-33.log using copy and delete

Also reported here:
https://stackoverflow.com/questions/43179979/log4j2-rollingfileappender-invalid-cross-device-link

Issue Links

• is duplicated by: LOG4J2-1726 RollingFile appender doesn't gzip and rolling log archives
• is related to: LOG4J2-2769 AtomicMoveNotSupportedException shouldn't be logged as ERROR
• relates to: LOG4J2-2016 Mark FileRenameAction as successful when using alternative ways to move files
• links to: GitHub Pull Request #107