Fsys RAM disk problems

I have a problem using a RAM disk in QNX, I search on “deja” to find this:

Marc Desjardine <MDesjardine@DELETE_THIS_PARTaptpower.com> wrote in message
news:9693gi$ou0$1@inn.qnx.com

I am using Fsys to create a RAM disk while a system is running. To do
this
I use the command “Fsys -NFsysRAM -c0 -r3M &” to start up another instance
of Fsys for the RAM disk. This works most of the time, but sometimes it
crashes the shell or other running processes, they die with SIGSEGV
signals.
Does anyone know why this isn’t working all the time? I am using Fsys
from
4.23A and switching to another version is not possible.

I have exactly the same problem, except I run QNX4.25D, here is a sin ver

PROGRAM NAME VERSION DATE
sys/Proc32 Proc 4.25J Sep 09 1999
sys/Proc32 Slib16 4.23G Oct 04 1996
sys/Slib32 Slib32 4.24B Aug 12 1997
/bin/Fsys Fsys32 4.24V Feb 18 2000
/bin/Fsys Floppy 4.24B Aug 19 1997
/bin/Fsys.eide eide 4.25A Feb 09 2000
//2/bin/Dev32 Dev32 4.23G Oct 04 1996
//2/bin/Dev32.ansi Dev32.ansi 4.23H Nov 21 1996
//2/bin/Dev32.ser Dev32.ser 4.23I Jun 27 1997
//2/bin/Dev32.rckt Dev32.rckt 4.24F Jun 03 1999
//2/bin/Dev32.par Dev.par 4.26 Feb 24 2000
//2/bin/Dev32.pty Dev32.pty 4.23G Oct 04 1996
//2/bin/Pipe Pipe 4.23A Feb 26 1996
//2/bin/cron cron 4.23B Oct 30 1997
//2/usr/bin/lpsrvr lpsrvr 4.24A Jun 26 1997
//2/bin/Fatfsys Fatfsys 4.26A Mar 27 2000
//2/bin/Net Net 4.25C Aug 30 1999
//2/bin/Net.ether905 Net.ether905 4.24J Feb 17 2000
//2/*/usr/ucb/Socklet Socklet 4.25H Jul 30 1999

When I put a “Fsys -r 128” in the .boot, system crash at login, login does a
SIGILL, or nothing happens, or it reboots, etc
If I can get trought it, other process start to crash with a SIGSEGV, I have
dumper running and I never had a dump image.

When I do a “Fsys -NFsysRAM -c0 -r 128” after a normal boot, then dinit,
mount etc, sometimes it runs fine, sometimes some random process crash in a
SIGSEGV.

Is there a fix for this? I want to use the ramdisk for the “dialog” utility,
that create a tmpnam() file then remove it, whenever we press a key, so in
ram it could be faster than the HD. I tries to use a “vdir -m 128K -n /ram”
but when I export TMPDIR to /ram it does not work, files are created in
/tmp, however it works with the Fsys -r 128 mounted on /ram.

Frédéric.

I never got the Fsys RAM disk working, I ended up using vdir which has
worked beautifully so far.

Marc.


Frédéric <frederic@spamcop.dataradio.com> wrote in message
news:9de9mt$j2a$1@inn.qnx.com

I have a problem using a RAM disk in QNX, I search on “deja” to find this:

Marc Desjardine <MDesjardine@DELETE_THIS_PARTaptpower.com> wrote in
message
news:9693gi$ou0$> 1@inn.qnx.com> …
I am using Fsys to create a RAM disk while a system is running. To do
this
I use the command “Fsys -NFsysRAM -c0 -r3M &” to start up another
instance
of Fsys for the RAM disk. This works most of the time, but sometimes it
crashes the shell or other running processes, they die with SIGSEGV
signals.
Does anyone know why this isn’t working all the time? I am using Fsys
from
4.23A and switching to another version is not possible.

I have exactly the same problem, except I run QNX4.25D, here is a sin ver

PROGRAM NAME VERSION DATE
sys/Proc32 Proc 4.25J Sep 09 1999
sys/Proc32 Slib16 4.23G Oct 04 1996
sys/Slib32 Slib32 4.24B Aug 12 1997
/bin/Fsys Fsys32 4.24V Feb 18 2000
/bin/Fsys Floppy 4.24B Aug 19 1997
/bin/Fsys.eide eide 4.25A Feb 09 2000
//2/bin/Dev32 Dev32 4.23G Oct 04 1996
//2/bin/Dev32.ansi Dev32.ansi 4.23H Nov 21 1996
//2/bin/Dev32.ser Dev32.ser 4.23I Jun 27 1997
//2/bin/Dev32.rckt Dev32.rckt 4.24F Jun 03 1999
//2/bin/Dev32.par Dev.par 4.26 Feb 24 2000
//2/bin/Dev32.pty Dev32.pty 4.23G Oct 04 1996
//2/bin/Pipe Pipe 4.23A Feb 26 1996
//2/bin/cron cron 4.23B Oct 30 1997
//2/usr/bin/lpsrvr lpsrvr 4.24A Jun 26 1997
//2/bin/Fatfsys Fatfsys 4.26A Mar 27 2000
//2/bin/Net Net 4.25C Aug 30 1999
//2/bin/Net.ether905 Net.ether905 4.24J Feb 17 2000
//2/*/usr/ucb/Socklet Socklet 4.25H Jul 30 1999

When I put a “Fsys -r 128” in the .boot, system crash at login, login does
a
SIGILL, or nothing happens, or it reboots, etc
If I can get trought it, other process start to crash with a SIGSEGV, I
have
dumper running and I never had a dump image.

When I do a “Fsys -NFsysRAM -c0 -r 128” after a normal boot, then dinit,
mount etc, sometimes it runs fine, sometimes some random process crash in
a
SIGSEGV.

Is there a fix for this? I want to use the ramdisk for the “dialog”
utility,
that create a tmpnam() file then remove it, whenever we press a key, so in
ram it could be faster than the HD. I tries to use a “vdir -m 128K -n
/ram”
but when I export TMPDIR to /ram it does not work, files are created in
/tmp, however it works with the Fsys -r 128 mounted on /ram.

Frédéric.

“Marc Desjardine” <MDesjardine@DELETE_THIS_PARTaptpower.com> a écrit dans le
message news: 9dp7g7$8n3$1@inn.qnx.com

I never got the Fsys RAM disk working, I ended up using vdir which has
worked beautifully so far.

thanks, I will try with vdir… it’s a pity the ramdisk does not work with
Fsys…

I’ve got them both working. Vdir is better. Use it.


Bill Caroselli - Sattel Global Networks
1-818-709-6201 ext 122



“Frédéric” <frederic@spamcop.dataradio.com> wrote in message
news:9dp7qc$90r$1@inn.qnx.com

“Marc Desjardine” <MDesjardine@DELETE_THIS_PARTaptpower.com> a écrit dans
le
message news: 9dp7g7$8n3$> 1@inn.qnx.com> …
I never got the Fsys RAM disk working, I ended up using vdir which has
worked beautifully so far.

thanks, I will try with vdir… it’s a pity the ramdisk does not work with
Fsys…

I’ve been using ram disks forever and have never had a problem. I have used
almost every version from 4.22 to 4.25 and never had any problems. We never
use the -N parameter (this is undocumented and is probably suspect). One
thing you should note if you use a ram disk, QNX assumes the first 4 files
in the ram disk are special files. The ram disk creates a .bitmap and a
…inodes file only. Therefore, you should always add two files (QNX assumes
that the first two files are .boot and .altboot). Therefore, after doing the
dinit, mount, you should touch a .boot and .altboot to create
empty files. Otherwise, writes to the first two files will consistently
fail.
“Bill Caroselli” <Bill@Sattel.com> wrote in message
news:9dpa33$ads$1@inn.qnx.com

I’ve got them both working. Vdir is better. Use it.


Bill Caroselli - Sattel Global Networks
1-818-709-6201 ext 122



“Frédéric” <> frederic@spamcop.dataradio.com> > wrote in message
news:9dp7qc$90r$> 1@inn.qnx.com> …
“Marc Desjardine” <MDesjardine@DELETE_THIS_PARTaptpower.com> a écrit
dans
le
message news: 9dp7g7$8n3$> 1@inn.qnx.com> …
I never got the Fsys RAM disk working, I ended up using vdir which has
worked beautifully so far.

thanks, I will try with vdir… it’s a pity the ramdisk does not work
with
Fsys…