DOC2000 file corruption

Hi folks,

I was wondering if anyone has had problems with file corruption in embedded
applications using DOC2000 flash drives under QNX4.25? We have an embedded
controller which boots from and stores data on a DOC2000 (the only drive on
the system), and the application is such that the unit could be powered down
without notice (ie no formal shutdown procedure - it’s very embedded). We
have had a few occasions where data files have been corrupted, probably as a
result of this. Is there any way to stop or minimise the liekelyhood of this
happening (we already use minimal disk caching, for instance), or even
better, recovering from it when it has?

Thanks in advance.

Best Regards,

Nick Tipping.

“Nick Tipping” <ntipping@sencon.co.uk> wrote in message
news:b61iih$huh$1@inn.qnx.com

Hi folks,

I was wondering if anyone has had problems with file corruption in
embedded
applications using DOC2000 flash drives under QNX4.25? We have an embedded
controller which boots from and stores data on a DOC2000 (the only drive
on
the system), and the application is such that the unit could be powered
down
without notice (ie no formal shutdown procedure - it’s very embedded). We
have had a few occasions where data files have been corrupted, probably as
a
result of this. Is there any way to stop or minimise the liekelyhood of
this
happening (we already use minimal disk caching, for instance), or even
better, recovering from it when it has?

Thanks in advance.

call sync() after write operations.

// wbr

better, recovering from it when it has?

I use chkfsys -Prqu /

Thanks in advance.

Best Regards,

Nick Tipping.

Thanks Ian, Thanks Mario.

Best Regards,

Nick Tipping.



“Nick Tipping” <ntipping@sencon.co.uk> wrote in message
news:b61iih$huh$1@inn.qnx.com

Hi folks,

I was wondering if anyone has had problems with file corruption in
embedded
applications using DOC2000 flash drives under QNX4.25? We have an embedded
controller which boots from and stores data on a DOC2000 (the only drive
on
the system), and the application is such that the unit could be powered
down
without notice (ie no formal shutdown procedure - it’s very embedded). We
have had a few occasions where data files have been corrupted, probably as
a
result of this. Is there any way to stop or minimise the liekelyhood of
this
happening (we already use minimal disk caching, for instance), or even
better, recovering from it when it has?

Thanks in advance.

Best Regards,

Nick Tipping.