John Garvey <jpg@cisco.com> wrote in message
news:3A4374B1.5BF6EC6D@cisco.com…
Augie Henriques wrote:
[bad pdm config files]
Yes, you (and many others) are victims of a “flowery performance
optimisation” (writing blocks to disk is slow, so don’t do it!).This is fixed in Fsys 4.24O, although I strongly recommend you
upgrade to 4.24V as it also fixes deadlocks in link(), rename(),
and write(), fixes message buffer corruption bugs with stat(),
ramdisk issues, ENOSPC fixes, ensures fsync() always physically
writes inodes, and also bugs with discarded disk writes to
_REMOVABLE media (and more).
I’m using a DELL Inspiron 5000 laptop with QNX 4.25 and Photon 1.14 from the
June 2000 CD. This system does have Fsys 2.24V. The pdm.cfg file goes bad
more often than I care to fix it (retore from backup). This is a new system
we are setting up for NASA. I don’t want them to get the wrong impression
about QNX 4.25 and Photon 1.14.
Please help.
Augie
This is not really a bug as much as a big annoyance. I
I think this is a bug. Losing the Photon Desktop Manager is not good.Yes, it is plainly a bug. Delayed-writes of bitmap blocks (as a
performance aid) is simply unacceptable without explicit user
compliance (Fsys -a). Suggestions involving ‘-d’ just move the
timing window of corruption and are a poor substitute for upgrading.It is a pity that QNX4/NTO filesystem issues receive little informed
official comment and too much unofficial unfounded glory-day rhetoric.