From: Andreas Dilger <adilger@sun.com>
To: lustre-devel@lists.lustre.org
Subject: [Lustre-devel] [RFC] "lctl readonly" modification proposal
Date: Thu, 28 Aug 2008 14:25:41 -0600 [thread overview]
Message-ID: <20080828202541.GR3392@webber.adilger.int> (raw)
In-Reply-To: <48B6DC27.5020308@sun.com>
On Aug 28, 2008 10:11 -0700, Nathaniel Rutman wrote:
> Andreas Dilger wrote:
> >>> I'd be thrilled if this was fixed so a normal shutdown did not do a
> >>> "force" unmount and set the device read-only, because that would also
> >>> avoid leaving the journal needing recovery.
>
> umount does either force or failover shutdown; failover sets readonly
> but force does not. Test-framework regularly does both. Andreas, if
> you want to avoid journal recovery, use umount -f.
Well, issue is that with normal mount/unmount the filesystem is always
dirty and needs journal recovery. Also, for the DMU, where we will
likely not have "read-only" support we need to be able to just block
all client transactions and flush everything to disk, doing a normal
shutdown.
Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.
next prev parent reply other threads:[~2008-08-28 20:25 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 [this message]
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
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=20080828202541.GR3392@webber.adilger.int \
--to=adilger@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.