DGS (General)shoichi.oshino - 13:49 Friday 31 January 2025 (32530)
Print this reportExchange k1tw0 SSDI exchanged k1tw0 SSD for the new one. The data recorded on the previous SSD is currently being copied to the NFS server.
Comments to this report:
takahiro.yamamoto - 3:15 Thursday 06 February 2025 (32597)
Print this reportMiyoki-san asked me about that trend data older than 7 days was unavailable on ndscope.
What the original post in this thread means is that we cannot get the minute trend for the relevant period (from Aug16 to Jan31) via k1nds0 until the copy process is completed. What we can do on the user side is to use k1nds1 instead of k1nds0. diaggui allows you to select the NDS server in the GUI window. ndscope allows you to specify the NDS with the option "--nds k1nds1:8088".
It's better to do one of following things on the admin side in order to avoid unnecessary trouble on user's activities. - add the disk region of the copy source to the "old_raw_minute_trend_dirs" parameter defined in daqdrc for k1nds until finishing the copy process. - change Primary NDS server by "NDSSERVER" environmental variable defined in client-user-env.sh until finishing the copy process.
A former one is better solution because some user's scripts explicitly gives k1nds0 or k1nds1 for the load balancing of NDS.
shoichi.oshino - 15:00 Friday 07 February 2025 (32615)
Print this reportI finished copying minute trend data to NFS server. I restarted the DAQ on k1nds0 to reflect this setting.