## 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](https://cloud.google.com/terms/service-terms), 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.

## Unsupported Lustre features

The following Lustre features are not supported:

- Client-side data compression
- Persistent client caching
- Unsigned or open-source Lustre clients

## Unsupported Lustre commands

The following Lustre commands are not supported:

- `lfs changelog`
- `lctl network up`/`down`
- `lctl conf_param <device> <params>`
- `lctl deactivate`
- `lctl abort_recovery`
- `lctl debug` commands
- `lctl debug_daemon`
- `lctl debug_kernel [file] [raw]`
- `lctl debug_file`
- `lctl clear`
- `lctl mark`
- `lctl filter`
- `lctl show`
- `lctl debug_list`
- `lctl modules`