Skip to page contentSkip to chat
ServiceNow support
    • Community
      Ask questions, give advice, and connect with fellow ServiceNow professionals.
      Developer
      Build, test, and deploy applications
      Documentation
      Find detailed information about ServiceNow products, apps, features, and releases.
      Impact
      Accelerate ROI and amplify your expertise.
      Learning
      Build skills with instructor-led and online training.
      Partner
      Grow your business with promotions, news, and marketing tools
      ServiceNow
      Learn about ServiceNow products & solutions.
      Store
      Download certified apps and integrations that complement ServiceNow.
      Support
      Manage your instances, access self-help, and get technical support.
Linux Server pattern calculate the total diskspace of a Linux Server with Multipath SAN drive incorrectly - Known Error
  • >
  • Knowledge Base
  • >
  • Known Error (Knowledge Base)
  • >
  • Linux Server pattern calculate the total diskspace of a Linux Server with Multipath SAN drive incorrectly
KB0819796

Linux Server pattern calculate the total diskspace of a Linux Server with Multipath SAN drive incorrectly


1141 Views Last updated : Feb 10, 2025 public Copy Permalink
KB Summary by Now Assist

Description

When running discovery, the total diskspace of Linux Server CI will be calculated using Linux Server pattern.
This pattern is not able to calculate the correct value if the Linux Server host has Multipath SAN drive.
If we revert to Linux Identity and Linux Storage probes (legacy discovery way), the total diskspace value will be correct.

Steps to Reproduce

  1. Get a Linux Server host with Multipath SAN drive.
  2. Run discovery using Linux Server pattern and observe the diskspace column of the created CI. This will be bigger than reality.
  3. Disable the pattern and enable both Linux Identity and Linux Storage probes in Linux classifier.
  4. Run discovery one more time using probes.
  5. The diskspace of the CI created on step 2 will be updated to different value (normally lower). This is the correct result that reflect reality.

Workaround

Upgrade to the latest Visibility Content plugin - the minimum version, 6.20.0


Related Problem: PRB1392676

The world works with ServiceNow.

Sign in for more! There's more content available only to authenticated users Sign in for more!
Did this KB article help you?
Did this KB article help you?

How would you rate your Now Support digital experience?

*

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

What can we improve? Please select all that apply.

What are we doing well? Please select all that apply.

Tell us more

*

Do you expect a response from this feedback?

  • Terms and conditions
  • Privacy statement
  • GDPR
  • Cookie policy
  • © 2025 ServiceNow. All rights reserved.