Hi Leo,

We can't reproduce this issue. You launched a lot of different application, and 
we can't make such configuration. Can you simplify your configuration to help us 
make similar configuration on our table?

-- 
Respectfully,
Oleg

> 
> Hi,
> 
> It is impossible for me to set trace at level 7 because of it generates a 
lot of information.
> 
> I am not using the sentence you are asking about.
> 
> 
> 
> > From: community-noreply@qnx.com
> > To: post90569@community.qnx.com
> > Subject: RE: Fsys down
> > Date: Tue, 13 Dec 2011 07:55:50 -0500
> > 
> > Hi Leo,
> > 
> > Please, send us trace log while trace level is set to 7.
> > 
> > Are you trying to use EFsys.ram instead of Fsys to create RAM disk? E.g.:
> > 
> > # Efsys.ram -m 0,4M,/ramdisk,/dev/ramimage &
> > 
> > -- 
> > Respectfully,
> > Oleg
> > 
> > > 
> > > We have an alert process running on our systems.
> > > It reports free disk space and fsys down over qnet.
> > > it runs sin -n"node" |grep Fsys.
> > > 
> > > 
> > > > From: community-noreply@qnx.com
> > > > To: post90494@community.qnx.com
> > > > Subject: RE: Fsys down
> > > > Date: Thu, 8 Dec 2011 23:45:45 -0500
> > > > 
> > > > Hi Leo,
> > > > 
> > > > I find nothing unusual in your logs except a lot of running processes.
> > > > 
> > > > Please, answer how you identify that Fsys is crashed? Is node with 
crashed 
> > > > Fsys available by network?
> > > > 
> > > > Additionally send us the following output:
> > > > 
> > > > # prefix > prefix.txt
> > > > 
> > > > -- 
> > > > Respectfully,
> > > > Oleg
> > > > 
> > > > > 
> > > > > Hi,
> > > > > 
> > > > > the two issues does not occurs in same nodes.
> > > > > 
> > > > > i pass you the information you asked.
> > > > > 
> > > > > 
> > > > > 
> > > > > > From: community-noreply@qnx.com
> > > > > > To: post90468@community.qnx.com
> > > > > > Subject: Re: Fsys down
> > > > > > Date: Wed, 7 Dec 2011 11:32:47 -0500
> > > > > > 
> > > > > > Hi Leo,
> > > > > > 
> > > > > > Does the issue with Net occur on the same nodes?
> > > > > > 
> > > > > > Please, send us output of following commands:
> > > > > > 
> > > > > > # sin ir > sin_it.txt
> > > > > > # sin ar > sin_ar.txt
> > > > > > # sin ver > sin_ver.txt
> > > > > > # show_pci -vvv > show_pci.txt
> > > > > > # sin ti > sin_ti.txt
> > > > > > # sin in> sin_in.txt
> > > > > > 
> > > > > > How do you identify that Fsys is crashed? Is node with crashed 
Fsys 
> > > > available 
> > > > > > via network?
> > > > > > 
> > > > > > -- 
> > > > > > Respectfully,
> > > > > > Oleg
> > > > > > 
> > > > > > > It occurs on several nodes.
> > > > > > > 
> > > > > > > especially those who use more disk.
> > > > > > > 
> > > > > > > 
> > > > > > > 
> > > > > > >...