From: John Hughes <john@calvaedi.com>
To: Trond Myklebust <Trond.Myklebust@netapp.com>
Cc: John Hughes <john@calva.com>,
linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Add "-e" option to rpc.gssd to allow error on ticket expiry. Try 2 with added man pages.
Date: Fri, 18 Nov 2011 23:57:34 +0100 [thread overview]
Message-ID: <4EC6E2DE.6050700@calvaedi.com> (raw)
In-Reply-To: <1321655886.10541.24.camel@lade.trondhjem.org>
On 11/18/2011 11:38 PM, Trond Myklebust wrote:
> The fact of the matter is that most application writers remain blithely
> oblivious of the need to fsync() as the ext4 people know all to well:
> see the attempts to impose the fully posix-compatible 'data=writeback'
> mode as the default and the catastrophe that occurred when
> 'data=ordered' semantics changed for the rename() syscall. Adding new
> failure modes needs to be done with care, or GNOME will crash and/or
> your word processor _will_ lose your last hour or so of work.
>
1. It's not a new failure mode. it's how things worked before 2.6.34
2. My ticket usualy expires in the middle of the night. I get back in
the morning and have to reboot the workstation because it's hung.
Anything left in the wordprocessor is lost.
Before this change I got back in the morning, the unlock screen popped
up, I entered my password and got a new ticket, everyone was happy.
prev parent reply other threads:[~2011-11-18 22:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-18 14:34 [PATCH] Add "-e" option to rpc.gssd to allow error on ticket expiry. Try 2 with added man pages John Hughes
2011-11-18 18:35 ` Trond Myklebust
2011-11-18 19:19 ` John Hughes
2011-11-18 20:33 ` Trond Myklebust
2011-11-18 20:47 ` Nick Bowler
2011-11-18 20:54 ` Trond Myklebust
2011-11-18 20:57 ` Jim Rees
2011-11-18 21:03 ` Trond Myklebust
2011-11-18 22:33 ` John Hughes
2011-11-18 22:37 ` Trond Myklebust
2011-11-18 22:46 ` John Hughes
2011-11-18 22:08 ` John Hughes
2011-11-18 22:38 ` Trond Myklebust
2011-11-18 22:57 ` John Hughes [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=4EC6E2DE.6050700@calvaedi.com \
--to=john@calvaedi.com \
--cc=Trond.Myklebust@netapp.com \
--cc=john@calva.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.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