[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: Close sometime takes a long time

To: Howard Chu <hyc@symas.com>
Subject: Re: Close sometime takes a long time
From: Hallvard Breien Furuseth <h.b.furuseth@usit.uio.no>
Date: Mon, 19 May 2014 17:46:50 +0200
Cc: Venkat Murty <venkat.murty@gmail.com>, openldap-technical@openldap.org
In-reply-to: <537A233E.4040905@symas.com>
References: <8458E72C-0C88-4830-9C82-01D6DC0F2005@gmail.com> <537A1CA5.8030003@usit.uio.no> <537A233E.4040905@symas.com>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0

On 05/19/2014 05:29 PM, Howard Chu wrote:

It seems he's talking specifically about the close(2) syscall taking a long time. Someone would have to peek inside the MacOSX kernel source code to answer that question.


Right... Though I can think of one non-kernel possibility:

Previous process wrote something and got killed - maybe while
fsyncing the changes.  Then rapidly open and closed another mdb
env - and close(sync descriptor) waits for the old changes to be
synced in order to decide whether to return success or failure.

--
Hallvard

Follow-Ups:
- Re: Close sometime takes a long time
  - From: Howard Chu <hyc@symas.com>

References:
- Close sometime takes a long time
  - From: Venkat Murty <venkat.murty@gmail.com>
- Re: Close sometime takes a long time
  - From: Hallvard Breien Furuseth <h.b.furuseth@usit.uio.no>
- Re: Close sometime takes a long time
  - From: Howard Chu <hyc@symas.com>

Prev by Date: Re: Close sometime takes a long time
Next by Date: Re: Close sometime takes a long time
Index(es):
- Chronological
- Thread