Stay organized with collections
Save and categorize content based on your preferences.
Version information
Google Cloud Managed Lustre is based on Lustre 2.14, but includes additional
features.
Sensitive information in the jobid_var parameter
The Lustre client software can track I/O statistics by "jobid" if the
jobid_var Lustre configuration parameter is set (e.g.
lctl get_param jobid_var). By default, this is disabled.
If you choose to enable this client-side feature, avoid including potentially
sensitive information in this field, as the data is categorized as
resource fields data, and not as Customer data.
For example, setting jobid_var to procname_uid will send the name of the
writing process and its UID from the client to the server. If the process name
is potentially sensitive to your organization, consider using a different
setting. See https://doc.lustre.org/lustre_manual.xhtml#jobstats for
detailed instructions for configuring jobstats on Lustre clients.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-04 UTC."],[],[],null,["# Lustre commands\n\nVersion information\n-------------------\n\nGoogle Cloud Managed Lustre is based on Lustre 2.14, but includes additional\nfeatures.\n\nSensitive information in the `jobid_var` parameter\n--------------------------------------------------\n\nThe Lustre client software can track I/O statistics by \"jobid\" if the\n`jobid_var` Lustre configuration parameter is set (e.g.\n`lctl get_param jobid_var`). By default, this is disabled.\n\nIf you choose to enable this client-side feature, avoid including potentially\nsensitive information in this field, as the data is categorized as\n[resource fields data](/terms/service-terms), and not as Customer data.\n\nFor example, setting `jobid_var` to `procname_uid` will send the name of the\nwriting process and its UID from the client to the server. If the process name\nis potentially sensitive to your organization, consider using a different\nsetting. See \u003chttps://doc.lustre.org/lustre_manual.xhtml#jobstats\u003e for\ndetailed instructions for configuring jobstats on Lustre clients.\n\nUnsupported Lustre features\n---------------------------\n\nThe following Lustre features are not supported:\n\n- Client-side data compression\n- Persistent client caching\n- Unsigned or open-source Lustre clients\n\nUnsupported Lustre commands\n---------------------------\n\nThe following Lustre commands are not supported:\n\n- `lfs changelog`\n- `lfs migrate`\n- `lfs setquota`\n- `lfs quotachown`, `quotaoff`, `quotaon`\n- `lctl network up`/`down`\n- `lctl conf_param \u003cdevice\u003e \u003cparams\u003e`\n- `lctl deactivate`\n- `lctl abort_recovery`\n- `lctl debug` commands\n- `lctl debug_daemon`\n- `lctl debug_kernel [file] [raw]`\n- `lctl debug_file`\n- `lctl clear`\n- `lctl mark`\n- `lctl filter`\n- `lctl show`\n- `lctl debug_list`\n- `lctl modules`"]]
