filesystem problem

A machine here gets its data corrupted from time to time.
Running the latest QNX patches. Using Fsys.ata with a Sandisk CompactFlash.
The application constantly logs data, 24 hours a day.

When “ls -l /home/xxx//.ctdat” is done to list all the data files
on the embedded machine, the PC reckons “interrupted function call or memory fault”
And that data can not be accessed.

If the directories are “ls -l”-ed one by one, the data can be seen.
chkfsys doesn’t improve things.
If all data is erased, the problem goes away and the PC
is ok again for the time being.

There is power backup so that the OS is always shutdown properly.
Any ideas what could be causing this?

acellarius@yahoo.com wrote:

A machine here gets its data corrupted from time to time.
Running the latest QNX patches. Using Fsys.ata with a Sandisk CompactFlash.
The application constantly logs data, 24 hours a day.

When “ls -l /home/xxx//.ctdat” is done to list all the data files
on the embedded machine, the PC reckons “interrupted function call or memory fault”
And that data can not be accessed.

I don’t think it’s a filesystem problem at all. It’s just a
user-unfriendly way of telling you that you’re trying to pass too many
arguments to a program:

$ boo=$(echo /bin/*)
$ while /bin/echo $boo > /dev/null
… do
… boo="$boo $boo"
… echo ${#boo}
… done
18789
37579
75159
150319
/bin/sh: /bin/echo: Interrupted function call

On 18 Feb 2003 17:17:28 GMT, Wojtek Lerch <wojtek_l@yahoo.ca> wrote:

acellarius@yahoo.com > wrote:
A machine here gets its data corrupted from time to time.
Running the latest QNX patches. Using Fsys.ata with a Sandisk CompactFlash.
The application constantly logs data, 24 hours a day.

When “ls -l /home/xxx//.ctdat” is done to list all the data files
on the embedded machine, the PC reckons “interrupted function call or memory fault”
And that data can not be accessed.

I don’t think it’s a filesystem problem at all. It’s just a
user-unfriendly way of telling you that you’re trying to pass too many
arguments to a program:

$ boo=$(echo /bin/*)
$ while /bin/echo $boo > /dev/null
… do
… boo="$boo $boo"
… echo ${#boo}
… done
18789
37579
75159
150319
/bin/sh: /bin/echo: Interrupted function call

Thanks for catching that!
Working with flash seems to bias one against flash & the filesystem…