Hi all,
we made a funny observation at our site.
During the night one of our nvme drives in our beegfs died. Our smart monitoring discovered that correctly and report the incident.
On the node we can confirm with `blkid` and even the beegfs-storage journal that we lost one device.
Our workflow for such cases is to inform the users which files are affected by running `beegfs-ctl find --targetid=X ...` and generate a list of files that are potentially lost.
My question is how to get the affected targetid?
I thought the easy way for this is to use `beegfs-ctl --listtargets --state`.
Unfortunately for `beegfs-ctl --listtargets --state` the state for all targets is reported as 'GOOD', which is obviously wrong.
Is this an issue with `beegfs-ctl --listtargets`? Do I holding it wrong? Or is there another way to get that targetid? Best would be a way that could be scripted.
Best,
Sebastian
--
Sebastian Oeste, M.Sc.
Computer Scientist
Technische Universität Dresden
Zentrum für Informationsdienste und Hochleistungsrechnen (ZIH)
Tel.
+49 (0)351 463-32405
E-Mail:
sebasti...@tu-dresden.de