From: Aleksandr Guzovskiy <Aleksandr.Guzovskiy@Sun.COM>
To: lustre-devel@lists.lustre.org
Subject: [Lustre-devel] SOM questions
Date: Wed, 06 Jan 2010 11:51:48 -0500 [thread overview]
Message-ID: <4B44BFA4.3070603@sun.com> (raw)
In-Reply-To: <078f01ca8e31$22ff9f80$68fede80$@com>
Eric Barton wrote:
> Vitaly,
>
> 1. Clients must replay opens on the MDS if "done writing" is still
> pending to notify the new MDS that this file is volatile. Does it
> matter whether the client already sent "close" to the previous MDS
> instance? Does it have to send "close" again?
>
> 2. I assume "done writing" is only sent after stripe updates have been
> committed, not just executed so that cached SOM attributes are not
> dependent on the client still being around to participate in
> recovery if an OST fails. Is this correct?
And this has the interaction with async data commit feature I brought up
during SC09 meetings i.e. client can't assume anymore OST IO is
synchronous.
-Alex
>
next prev parent reply other threads:[~2010-01-06 16:51 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 [this message]
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
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=4B44BFA4.3070603@sun.com \
--to=aleksandr.guzovskiy@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox