From: Alex Zhuravlev <Alex.Zhuravlev@Sun.COM>
To: lustre-devel@lists.lustre.org
Subject: [Lustre-devel] SOM questions
Date: Tue, 12 Jan 2010 06:42:38 +0300 [thread overview]
Message-ID: <4B4BEFAE.7030907@sun.com> (raw)
In-Reply-To: <AC682480-691F-46C8-906D-8818A1C8FC18@Sun.COM>
On 1/12/10 12:59 AM, Vitaly Fertman wrote:
> what do you mean stable? If you mean they are not going to change,
> this is exactly what OST doesn't know because it doesn't know if file
> is opened.
let me rephrase it: stable means there is no pending (cached) IO on
the clients and all locally cached (on OST) changes are committed to disk.
> could you clarify how you can block IO from "lost" clients without
> writing some id (VBR id?) to OST objects and not waiting for this
> change to commit before updating MDS with new attributes?
this is related but different issue discussed in "SOM safety" :) we
consider at least 3 options for that.
thanks, Alex
prev parent reply other threads:[~2010-01-12 3:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-05 18:01 [Lustre-devel] SOM questions Eric Barton
2010-01-06 16:51 ` Aleksandr Guzovskiy
2010-01-11 14:10 ` Vitaly Fertman
2010-01-11 15:47 ` Alex Zhuravlev
2010-01-11 16:44 ` Alex Zhuravlev
2010-01-11 21:59 ` Vitaly Fertman
2010-01-12 3:42 ` Alex Zhuravlev [this message]
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=4B4BEFAE.7030907@sun.com \
--to=alex.zhuravlev@sun.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.