https://jira.whamcloud.com This file is an XML representation of an issue en-us 9.4.14 940014 05-12-2023 https://jira.whamcloud.com/browse/LU-14860 Lustre <p>While the code in <tt>access_log_size_store()</tt> appears to allow <tt>size=0</tt> to be used to disable the OAL on a system, this actually fails with <tt>-EBUSY</tt>. Setting it to any valid size after it has been created fails with <tt>-EEXIST</tt>. It should be possible to (at least) disable the OAL after it was enabled without an unmount/remount, accepting that any entries in the log will be lost.</p> LU-14860

setting obdfilter.*.access_log_size=0 fails

Bug Minor Open Unresolved WC Triage Andreas Dilger Fri, 16 Jul 2021 23:50:47 +0000 Tue, 20 Jul 2021 08:53:59 +0000 0 3 <p>This was designed in to make it faster. Under the original implementation there were no shared locks between readers and writers. I guess it could be done under the semaphore we added but what is the use case?</p> <p>I enabled OAL on to see if I could use it for tracking hot object IO on the OSTs with a user script instead of via lamigo, but wasn't able to turn OAL off afterward. I think having a simple way to aggregate data from OAL for this would be useful for debugging but it should be possible to turn it off again once that is finished.</p> Related LU-13238 Development Rank 1|i01zi7: Rank (Obsolete) 9223372036854775807 Severity