zsh-workers
 help / color / mirror / code / Atom feed
From: Clint Adams <schizo@debian.org>
To: martin f krafft <madduck@debian.org>, 482525@bugs.debian.org
Cc: zsh-workers@sunsite.dk
Subject: Re: Bug#482525: failure to fcntl-lock history file, takes ages to create interactive session
Date: Fri, 23 May 2008 13:24:08 +0000	[thread overview]
Message-ID: <20080523132408.GA8806@scru.org> (raw)
In-Reply-To: <20080523094636.GA3814@piper.oerlikon.madduck.net>

On Fri, May 23, 2008 at 11:46:36AM +0200, martin f krafft wrote:
> When I log in to a machine where my ~ is NFS-mounted (lockd is in
> use), with hist_fcntl_lock set, it takes several minutes to get an
> interactive prompt. The reason is that the locking seems to fail,
> according to strace:
> 
>   open("/home/madduck/.var/zsh/history-diamond", O_RDWR|O_NOCTTY) = 3
>   fcntl64(3, F_SETLKW, {type=F_WRLCK, whence=SEEK_SET, start=0, len=0}) = -1 EIO (Input/output error)
>   rt_sigprocmask(SIG_BLOCK, [CHLD], [], 8) = 0
>   rt_sigaction(SIGCHLD, NULL, {0x80a88a0, [], SA_INTERRUPT}, 8) = 0
>   rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
>   nanosleep({1, 0}, {1, 0})         = 0 
> 
> This repeats a number of times before it finally moves on. Complete
> strace is attached. Search for "EIO".

Out of curiosity, does the same thing happen if you use -o nolock on the
client?


       reply	other threads:[~2008-05-23 13:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20080523094636.GA3814@piper.oerlikon.madduck.net>
2008-05-23 13:24 ` Clint Adams [this message]
2008-05-23 22:30   ` Vincent Lefevre
2008-05-24  2:56     ` Clint Adams
2008-05-27  8:32       ` martin f krafft

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=20080523132408.GA8806@scru.org \
    --to=schizo@debian.org \
    --cc=482525@bugs.debian.org \
    --cc=madduck@debian.org \
    --cc=zsh-workers@sunsite.dk \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).