lustre-devel-lustre.org archive mirror
 help / color / mirror / Atom feed
From: Sudheendra Sampath <sudheendra.sampath@gmail.com>
To: lustre-devel@lists.lustre.org
Subject: [lustre-devel] Getting client UUID from transaction code (osd_trans_create) - osd-zfs
Date: Tue, 19 Jan 2021 11:40:18 -0800	[thread overview]
Message-ID: <CABnqofyTN6Cr8JaMgeoke5TWG9j0JL_vMq03YPd8sYuRHXfqcw@mail.gmail.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 284 bytes --]

Hi,

When I have multiple 'remote' clients writing data, I am trying to find a
way to recognize which client data I am writing to the underlying storage.

Appreciate if anyone in this list can point me in the right direction to
access remote client UUID.

Thanks,

Sudheendra Sampath

[-- Attachment #1.2: Type: text/html, Size: 478 bytes --]

[-- Attachment #2: Type: text/plain, Size: 165 bytes --]

_______________________________________________
lustre-devel mailing list
lustre-devel@lists.lustre.org
http://lists.lustre.org/listinfo.cgi/lustre-devel-lustre.org

             reply	other threads:[~2021-01-19 19:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-19 19:40 Sudheendra Sampath [this message]
2021-01-23 11:32 ` [lustre-devel] Getting client UUID from transaction code (osd_trans_create) - osd-zfs Andreas Dilger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CABnqofyTN6Cr8JaMgeoke5TWG9j0JL_vMq03YPd8sYuRHXfqcw@mail.gmail.com \
    --to=sudheendra.sampath@gmail.com \
    --cc=lustre-devel@lists.lustre.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).