Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 24 Feb 2018 14:34:20 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-bugs@FreeBSD.org
Subject:   [Bug 226170] gstat does not detect new devices (/dev/gpt/* & /dev/label/*)
Message-ID:  <bug-226170-8@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226170

            Bug ID: 226170
           Summary: gstat does not detect new devices (/dev/gpt/* &
                    /dev/label/*)
           Product: Base System
           Version: 11.0-RELEASE
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: bin
          Assignee: freebsd-bugs@FreeBSD.org
          Reporter: ben.rubson@gmail.com

Hi,

I automatically run gstat upon system startup to feed a performance reporting
tool.
Here is the command launched :
# gstat -B -d -o -s -I30s -f"label/|gpt/"

Some seconds/minutes after system startup, I add some iSCSI disks needed for
production :
# iscsictl -Aa

Unfortunately, gstat does not detect these new disks. Reproductible for each
newly added disk.
I need to restart it so that it will correctly show them.

Actually, as you can see, I filter on "label/|gpt/", to only work on /dev/label
and /dev/gpt devices, to have nicely named devices in my reports.

After some tests, I found that gstat automatically correctly detects the new
/dev/da* devices, but does not detect /dev/gpt/* and /dev/label/* devices.

Another test, let's remove all iSCSI disks :
# iscsictl -Ra
As expected, gstat automatically removes them from its output.
Let's add them again :
# iscsictl -Aa
gstat now automatically correctly shows /dev/gpt/* and /dev/label/* in its
output. Strange behavior !

Thank you very much for your support !

Ben

-- 
You are receiving this mail because:
You are the assignee for the bug.


Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-226170-8>