* bash.exe: *** fatal error - add_item ("\??\C:\cygwin", "/", ...) failed, errno 1
[not found] <33B440E9970A984C93230FC4FA9B70ECCF1964@DALIFXMB1.hbk.com>
@ 2015-03-05 17:03 ` Vladimir Sakharuk
2015-03-05 18:42 ` Corinna Vinschen
0 siblings, 1 reply; 6+ messages in thread
From: Vladimir Sakharuk @ 2015-03-05 17:03 UTC (permalink / raw)
To: 'cygwin@cygwin.com'
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?)
Thank you for suggestions.
Running on
cygwin 6.1
windows server 2008 R2 Ent
2 [main] bash 12840 C:\cygwin\bin\bash.exe: *** fatal error - add_item ("\??\C:\cygwin", "/", ...) failed, errno 1
Stack trace:
Frame Function Args
002868A8 6102F97B (002868A8, 00000000, 00000000, 00000000)
00286B98 6102F97B (6119FE20, 00008000, 00000000, 611A1C8F)
00287BC8 6100652C (611DF498, 00287BF4, 00000000, 60FE000C)
00287BE8 61006568 (611DF498, 00289C10, 00000001, 0003000A)
0028AC28 610917E4 (60FE000C, 20000C08, 0028ACF8, 61083290)
0028AC58 610D40FF (004C46B0, 01D05699, 004657E0, 612729D4)
208979 [main] bash 12840 exception::handle: Exception: STATUS_ACCESS_VIOLATION
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: bash.exe: *** fatal error - add_item ("\??\C:\cygwin", "/", ...) failed, errno 1
2015-03-05 17:03 ` bash.exe: *** fatal error - add_item ("\??\C:\cygwin", "/", ...) failed, errno 1 Vladimir Sakharuk
@ 2015-03-05 18:42 ` Corinna Vinschen
2015-03-05 21:54 ` Vladimir Sakharuk
0 siblings, 1 reply; 6+ messages in thread
From: Corinna Vinschen @ 2015-03-05 18:42 UTC (permalink / raw)
To: cygwin
[-- Attachment #1: Type: text/plain, Size: 1509 bytes --]
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
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* RE: bash.exe: *** fatal error - add_item ("\??\C:\cygwin", "/", ...) failed, errno 1
2015-03-05 18:42 ` Corinna Vinschen
@ 2015-03-05 21:54 ` Vladimir Sakharuk
2015-03-09 9:26 ` Corinna Vinschen
0 siblings, 1 reply; 6+ messages in thread
From: Vladimir Sakharuk @ 2015-03-05 21:54 UTC (permalink / raw)
To: 'cygwin@cygwin.com'
That was helpful! I have stopped trying rebase combinations and looking for something else...
Thank you.
-----Original Message-----
From: cygwin-owner@cygwin.com [mailto:cygwin-owner@cygwin.com] On Behalf Of Corinna Vinschen
Sent: Thursday, March 05, 2015 12:04 PM
To: cygwin@cygwin.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
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: bash.exe: *** fatal error - add_item ("\??\C:\cygwin", "/", ...) failed, errno 1
2015-03-05 21:54 ` Vladimir Sakharuk
@ 2015-03-09 9:26 ` Corinna Vinschen
2015-03-09 17:11 ` Vladimir Sakharuk
0 siblings, 1 reply; 6+ messages in thread
From: Corinna Vinschen @ 2015-03-09 9:26 UTC (permalink / raw)
To: cygwin
[-- Attachment #1: Type: text/plain, Size: 2529 bytes --]
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@cygwin.com [mailto:cygwin-owner@cygwin.com] On Behalf Of Corinna Vinschen
> Sent: Thursday, March 05, 2015 12:04 PM
> To: cygwin@cygwin.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
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* RE: bash.exe: *** fatal error - add_item ("\??\C:\cygwin", "/", ...) failed, errno 1
2015-03-09 9:26 ` Corinna Vinschen
@ 2015-03-09 17:11 ` Vladimir Sakharuk
2015-03-09 19:48 ` Corinna Vinschen
0 siblings, 1 reply; 6+ messages in thread
From: Vladimir Sakharuk @ 2015-03-09 17:11 UTC (permalink / raw)
To: cygwin
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@cygwin.com [mailto:cygwin-owner@cygwin.com] On Behalf Of Corinna Vinschen
Sent: Monday, March 09, 2015 5:18 AM
To: cygwin@cygwin.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@cygwin.com [mailto:cygwin-owner@cygwin.com] On
> Behalf Of Corinna Vinschen
> Sent: Thursday, March 05, 2015 12:04 PM
> To: cygwin@cygwin.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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: bash.exe: *** fatal error - add_item ("\??\C:\cygwin", "/", ...) failed, errno 1
2015-03-09 17:11 ` Vladimir Sakharuk
@ 2015-03-09 19:48 ` Corinna Vinschen
0 siblings, 0 replies; 6+ messages in thread
From: Corinna Vinschen @ 2015-03-09 19:48 UTC (permalink / raw)
To: cygwin
[-- Attachment #1: Type: text/plain, Size: 3186 bytes --]
On Mar 9 16:12, Vladimir Sakharuk wrote:
> > -----Original Message-----
> > From: cygwin-owner@cygwin.com [mailto:cygwin-owner@cygwin.com] On
> > Behalf Of Corinna Vinschen
> > Sent: Thursday, March 05, 2015 12:04 PM
> > To: cygwin@cygwin.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.
>
> -----Original Message-----
> From: cygwin-owner@cygwin.com [mailto:cygwin-owner@cygwin.com] On Behalf Of Corinna Vinschen
> Sent: Monday, March 09, 2015 5:18 AM
> To: cygwin@cygwin.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.
> One difference is that we are running(starting) up to 32 simultaneous
> instances of bash.exe/Cygwin on 32 core box.
Shouldn't make a difference since that's what the Interlocked operations
are meant for.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2015-03-09 19:29 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <33B440E9970A984C93230FC4FA9B70ECCF1964@DALIFXMB1.hbk.com>
2015-03-05 17:03 ` bash.exe: *** fatal error - add_item ("\??\C:\cygwin", "/", ...) failed, errno 1 Vladimir Sakharuk
2015-03-05 18:42 ` Corinna Vinschen
2015-03-05 21:54 ` Vladimir Sakharuk
2015-03-09 9:26 ` Corinna Vinschen
2015-03-09 17:11 ` Vladimir Sakharuk
2015-03-09 19:48 ` Corinna Vinschen
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 read-only IMAP folder(s) and NNTP newsgroup(s).