bcache dirty_data not exist

This document (7024194) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Linux Enterprise Server 12 Service Pack 1 (SLES 12 SP1)
SUSE Linux Enterprise Server for SAP Applications Service Pack 1

Situation

The /var/log/message contains following message:

/sys/fs/bcache/bcache<ID>/dirty_data: No such file or directory

This happen after patching SLES 12 SP1 server to use newer kernel.

Resolution

The location is usually called from custom created scripts with a specific purpose in mind (non SUSE provided scripts).

dirty_data is now moved to /sys/block/bcache<ID>/bcache/dirty_data

To properly resolve the problem, the script would need to be modified to point to the right location specified above.

Cause

dirty_data have been removed in kernel-3.12.74-60.64.82 and this is an upstream change, dirty_data is removed from struct gc_stat.

The dirty data file is moved to /sys/block/bcache<ID>/bcache/dirty_data, the new location is used to count dirty data for specific backing device. The previous global dirty data number can be calculated by adding all the per-backing-device dirty_data numbers.

Disclaimer

This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.

Document ID:7024194
Creation Date: 22-Oct-2019
Modified Date:03-Mar-2020
- SUSE Linux Enterprise Server
- SUSE Linux Enterprise Server for SAP Applications

< Back to Support Search

For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]suse.com