You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The kdump plugin for ServiceReport currently flags no problems, even if the target filesystem that kdump will write to is undersized or has insufficient free space to save a dump. For example, I have an LPAR with 62TB of memory with a 34GB root filesystem, with only 2GB left free space, and ServiceReport does not flag this as a problem. I think this would be a useful enhancement, particularly for users with large amounts of RAM, as the default filesystem size is likely to be too small in these cases.
The text was updated successfully, but these errors were encountered:
The kdump plugin for ServiceReport currently flags no problems, even if the target filesystem that kdump will write to is undersized or has insufficient free space to save a dump. For example, I have an LPAR with 62TB of memory with a 34GB root filesystem, with only 2GB left free space, and ServiceReport does not flag this as a problem. I think this would be a useful enhancement, particularly for users with large amounts of RAM, as the default filesystem size is likely to be too small in these cases.
The text was updated successfully, but these errors were encountered: