From: Mikhail Pershin <Mikhail.Pershin@Sun.COM>
To: lustre-devel@lists.lustre.org
Subject: [Lustre-devel] [RFC] "lctl readonly" modification proposal
Date: Thu, 21 Aug 2008 14:03:44 +0400 [thread overview]
Message-ID: <op.uf8d8iklatmt0c@goga> (raw)
In-Reply-To: <200808211324.09313.alexander.zarochentsev@sun.com>
On Thu, 21 Aug 2008 13:24:08 +0400, Alexander Zarochentsev
<Alexander.Zarochentsev@sun.com> wrote:
> On 20 August 2008 23:42:39 Mikhail Pershin wrote:
>> Also to be sure that all before barrier is on disk, many test cases
>> about recovery rely on the fact that operations before barrier are on
>> disk. This is important with HARD failure case especially, without
>> sync before barrier the operations before barrier may be lost and
>> affect the tests. I agree that syncless variant of barrier is needed
>> but we also need barrier with sync depending on test case.
>
> You don't need lctl readonly to do a sync, the replay_barrier function
> from test-framework.sh adds a sync explicitly
You are right, it is safe in that case.
--
Mikhail Pershin
Staff Engineer
Lustre Group
Sun Microsystems, Inc.
next prev parent reply other threads:[~2008-08-21 10:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-20 11:23 [Lustre-devel] [RFC] "lctl readonly" modification proposal Alexander Zarochentsev
2008-08-20 17:39 ` Peter Braam
2008-08-20 19:29 ` Andreas Dilger
2008-08-22 15:45 ` Alexander Zarochentsev
2008-08-24 2:02 ` Andreas Dilger
2008-08-28 17:11 ` Nathaniel Rutman
2008-08-28 20:25 ` Andreas Dilger
2008-08-29 18:46 ` Nathaniel Rutman
2008-08-20 19:42 ` Mikhail Pershin
2008-08-20 19:59 ` Peter Braam
2008-08-21 9:24 ` Alexander Zarochentsev
2008-08-21 10:03 ` Mikhail Pershin [this message]
2008-08-21 10:43 ` 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=op.uf8d8iklatmt0c@goga \
--to=mikhail.pershin@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