DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=KjrA6SKZcnx/wdejY9Qx4kN7w6dEwQ4WXL0hkVvlCbpPmoolD0BGS
	1eRvnc0U7r8ZE4y4+PBpmoMrvu1P1GGc67C59XUxT+UAVZpXSJaC14obmvAkTlg2
	yPamPzOUT+HuV6haXgzhXJCAAbDf4bgoKFvA8hlNCl469QmaLI8SnU=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Date: Thu, 5 Mar 2015 18:03:49 +0100
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: bash.exe: *** fatal error - add_item ("\??\C:\cygwin", "/", ...) failed, errno 1
Message-ID: <20150305170349.GI3213@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <33B440E9970A984C93230FC4FA9B70ECCF1964 AT DALIFXMB1 DOT hbk DOT com> <33B440E9970A984C93230FC4FA9B70ECCF19A0 AT DALIFXMB1 DOT hbk DOT com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;	protocol="application/pgp-signature"; boundary="QWIFStbFpmlD00Pf"
Content-Disposition: inline
In-Reply-To: <33B440E9970A984C93230FC4FA9B70ECCF19A0@DALIFXMB1.hbk.com>
User-Agent: Mutt/1.5.23 (2014-03-12)

--QWIFStbFpmlD00Pf
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

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.
>=20
> 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. S=
tarting 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 th=
ere 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

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

--QWIFStbFpmlD00Pf
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBAgAGBQJU+Ix1AAoJEPU2Bp2uRE+gw+4P/0zm/KRuXB0MoSWw78Mtmps/
nj/ADC35NUE0hFngpY3c1LtgrEkisA24MJC+H/2VXLFeHu5I9wqMqmyoZfIvTk5O
GQn/MSuCG07BBIZpubxTB+Nxp4RaJJCXouBG5+xqU/iSIdUQXiz1Dw6xPjd4Vni6
gex9UaFt9TNnZlt4YraV1r89vbzs631QyhdBp9H3tITtW3t6xoBJVNY/1LfM0OsB
CnXUyyqpLYZguaJdC4CTEPHqpUs312Peg0M8CkefTNz09P9Ea7HjyJ+JLDl9ihGN
pXRVliHdB8fjDkWJYmi7QOdvJkv1WnDWGnrZ2nmJDhdezSpn8XsGlB+6HpuBc/KL
SNpJD7thFzDAO2u+B2uxaSapVHqszJaKXHSsPpOB996FiepPG/SzfiMF9t+XbueG
o/pZ8IVqQR696NiFy2o39tVjlExOmmBUw9CV6fyaWPYVW8E0MZaLAcy3Nd1p9Vzm
DgHAAjmJjYTl8Z7h1cZVJDeD/6FihIg/ewJ5eHO3vLF/6EBYzCGXqGWIxrYd61BA
+ix1B/MLKoPrSmZAJS1srCywi5HMkW9SMHQid7TQdSgWCtYX4JWfc1+urd61pzkX
Mybo4R+DY287Wb1mDJOWJJIDV1YkXdTewI+O+c4kRFnNVqXF4Nks4ShfQUvdaWzz
F49npONV5Y0Qb/Ix8Muk
=7+aP
-----END PGP SIGNATURE-----

--QWIFStbFpmlD00Pf--