X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:subject:date:message-id:references
	:in-reply-to:content-type:content-transfer-encoding
	:mime-version; q=dns; s=default; b=P5UCxe3fKgygbFKvCRUpZwzNv+U6/
	zYGKHv4hxEsnMXjZyTZ38bnhuxXYpeaTxFJbuLIF01Ps9aHIKzGYPwaDIgpL6VlL
	IBtGDAmerfCRtZEsi56rYTZyR8IsFKxUZXaejfRYDdRpemqMvcamcoaFATBVuz7Q
	AtfvPmHJq5nVyg=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:subject:date:message-id:references
	:in-reply-to:content-type:content-transfer-encoding
	:mime-version; s=default; bh=iZDPG2/6zTN4vmEhGQDeUkO7nnE=; b=ZQQ
	4ES2BwRlCBdH0A0r66qUgdRq0iUntOek4iIirfK2KMP9Ww5c3wwwqgYCtR48Q90w
	3bgoH2knMFScFcjNAZNxq9ytXdCme2b01E65qHD52i0MTdR5nO7zRQT6ObTFvZSA
	3hhRZdc7+CXF+LClGMTR2d9U0di8OF2BVp0f7Tus=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=2.7 required=5.0 tests=AWL,BAYES_40,CYGWIN_OWNER_BODY,MIME_BASE64_BLANKS,RCVD_IN_DNSWL_NONE,SPF_HELO_PASS,SPF_PASS autolearn=no version=3.3.2
X-HELO: na01-bl2-obe.outbound.protection.outlook.com
From: Vladimir Sakharuk <vsakharuk AT hbk DOT com>
To: "cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com>
Subject: RE: bash.exe: *** fatal error - add_item ("\??\C:\cygwin", "/", ...) failed, errno 1
Date: Mon, 9 Mar 2015 16:12:32 +0000
Message-ID: <33B440E9970A984C93230FC4FA9B70ECCF42AE@DALIFXMB1.hbk.com>
References: <33B440E9970A984C93230FC4FA9B70ECCF1964 AT DALIFXMB1 DOT hbk DOT com> <33B440E9970A984C93230FC4FA9B70ECCF19A0 AT DALIFXMB1 DOT hbk DOT com> <20150305170349 DOT GI3213 AT calimero DOT vinschen DOT de> <33B440E9970A984C93230FC4FA9B70ECCF225E AT DALIFXMB1 DOT hbk DOT com> <20150309091806 DOT GC28200 AT calimero DOT vinschen DOT de>
In-Reply-To: <20150309091806.GC28200@calimero.vinschen.de>
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
X-EOPAttributedMessage: 0
Received-SPF: TempError (protection.outlook.com: error in processing during lookup of hbk.com: DNS Timeout)
Authentication-Results: spf=temperror (sender IP is 216.52.181.200) smtp.mailfrom=vsakharuk AT hbk DOT com; cygwin.com; dkim=none (message not signed) header.d=none;
X-Forefront-Antispam-Report:	CIP:216.52.181.200;CTRY:US;IPV:NLI;EFV:NLI;BMV:1;SFV:NSPM;SFS:(10009020)(6009001)(13464003)(189002)(199003)(53754006)(51704005)(377454003)(24454002)(23676002)(19580405001)(6806004)(33656002)(93886004)(450100001)(2351001)(2501003)(102836002)(107886001)(50466002)(62966003)(55846006)(53416004)(19580395003)(92566002)(54356999)(77096005)(25786006)(106466001)(110136001)(77156002)(76176999)(2950100001)(2656002)(87936001)(86362001)(50986999)(2920100001)(46102003)(460985005);DIR:OUT;SFP:1101;SCL:1;SRVR:CY1PR0801MB0826;H:mailhostd.hbk.com;FPR:;SPF:TempError;MLV:sfv;MX:3;A:1;LANG:en;
X-OriginatorOrg: hbk.com
X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:CY1PR0801MB0826;
X-Microsoft-Antispam-PRVS:	<CY1PR0801MB0826606F08627A3805850666BE1B0 AT CY1PR0801MB0826 DOT namprd08 DOT prod DOT outlook DOT com>
X-Exchange-Antispam-Report-Test: UriScan:;
X-Exchange-Antispam-Report-CFA-Test:	BCL:0;PCL:0;RULEID:(601004)(5002009)(5005006);SRVR:CY1PR0801MB0826;BCL:0;PCL:0;RULEID:;SRVR:CY1PR0801MB0826;
X-Forefront-PRVS: 05102978A2
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 09 Mar 2015 16:12:34.3936 (UTC)
X-MS-Exchange-CrossTenant-Id: 56ddf89f-f56a-4580-a618-b3ec65cf64c4
X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=56ddf89f-f56a-4580-a618-b3ec65cf64c4;Ip=[216.52.181.200];Helo=[mailhostd.hbk.com]
X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY1PR0801MB0826
X-IsSubscribed: yes
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by delorie.com id t29GD4Cc016527

One difference is that we are running(starting) up to 32 simultaneous instances of bash.exe/Cygwin on 32 core box.

-----Original Message-----
From: cygwin-owner AT cygwin DOT com [mailto:cygwin-owner AT cygwin DOT com] On Behalf Of Corinna Vinschen
Sent: Monday, March 09, 2015 5:18 AM
To: cygwin AT cygwin DOT com
Subject: Re: bash.exe: *** fatal error - add_item ("\??\C:\cygwin", "/", ...) failed, errno 1

On Mar  5 21:30, Vladimir Sakharuk wrote:
> That was helpful! I have stopped trying rebase combinations and 
> looking for something else...

It wasn't all that helpful I think.  My description of what happens was rather off.  Actually the fact if a process has created or just opened the shared mem region isn't checked at this point in time.
Rather, a spinlock is used to generate exclusive access to the shared mem region at initilization time.
This spinlock implementation, basically using the InterlockedExchange call at its code, has served us well in the past, but something in your cluster setup appears to break it, though I can't imagine how.


Corinna


> 
> Thank you.
> 
> -----Original Message-----
> From: cygwin-owner AT cygwin DOT com [mailto:cygwin-owner AT cygwin DOT com] On 
> Behalf Of Corinna Vinschen
> Sent: Thursday, March 05, 2015 12:04 PM
> To: cygwin AT cygwin DOT com
> Subject: Re: bash.exe: *** fatal error - add_item ("\??\C:\cygwin", 
> "/", ...) failed, errno 1
> 
> On Mar  5 15:40, Vladimir Sakharuk wrote:
> > Hi All,
> > I have found similar issues, but did not find solution that worked for me. Looking for help.
> > 
> > I am trying to run applications on windows cluster.
> > I am getting random crashes like bellow.
> > However most of the times it works. I assume around 1% of starts fails. Starting it is again usually succeed.
> > I suspected that it was forking issue, but cygwin's rebase did not help.
> > I did rebase after server reboot with no Cygwin apps running. (BTW, 
> > Is there any way to check if rebase successful?)
> 
> That's not a rebase problem.  It's apparently a concurrency problem of sorts.  While pulling up the per-user shared memory region, two or more processes are trying to set up the same mount points.
> 
> This is not supposed to happen.  Only the first process actually
> *creating* the per-user shared memory is supposed to create the mount points.  The OS tells a process if it created or just opened a shared memory region, but for some reason both processes seem to think they created the shmem region and one of them then stumbles of the EPERM condition trying to create the root mount point twice.
> 
> > Thank you for suggestions.
> 
> I don't have a sugggestion, in fact.  Again, this error condition was supposed to be impossible, but somehow it isn't in your cluster setup.

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat