All of lore.kernel.org
 help / color / mirror / Atom feed
From: Erich Focht <efocht@gmail.com>
To: lustre-devel@lists.lustre.org
Subject: [Lustre-devel] accessing object version from user space?
Date: Wed, 04 May 2011 18:36:36 +0200	[thread overview]
Message-ID: <4DC18094.6050007@gmail.com> (raw)
In-Reply-To: <AD1E6969-051D-41AA-BE5D-E89F114C0317@whamcloud.com>

On 05/03/2011 09:35 PM, Andreas Dilger wrote:
> On May 3, 2011, at 06:46, Erich Focht wrote:
>> is there a way to access the file objects version information (epoch, transno, whatever is used
>> for version based recovery) from user space? If yes, is that possible for lustre 1.8.x, too?
>> Looking for a way to check (quickly) whether a file has changed while copying it away...
> 
> Comparing the ctime at the start/end of the copy should be enough for that.

You mean ctime of Lustre file, or ctime of file objects on OSTs? Is there a nice way to access those?
Maybe I'm a bit paranoid, but what if a client loses connection to MDS while continuing to write to
OSTs? Just a thought...

Thanks & best regards,
Erich

  reply	other threads:[~2011-05-04 16:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-03 12:46 [Lustre-devel] accessing object version from user space? Erich Focht
2011-05-03 19:35 ` Andreas Dilger
2011-05-04 16:36   ` Erich Focht [this message]
2011-05-05 16:48     ` 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=4DC18094.6050007@gmail.com \
    --to=efocht@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.