Two computers have the same problem (so probably sw problem):
lists many files, then gets stuck. (no error reported)
sin shows that ls remains REPLY-blocked to Fsys
(Some tasks from application software do the same - those which works with
filesystem too intesive, other works fine).
Any advice ?
Andy
Andrej Lucny <andy@microstep-mis.com> wrote:
Two computers have the same problem (so probably sw problem):
ls -lR /
lists many files, then gets stuck. (no error reported)
sin shows that ls remains REPLY-blocked to Fsys
What does “sin -Pls fi” give? That should try to give what file
the ls was trying to access when it blocked.
Have you run a chkfsys on all your partitions? Is it possible
you might have a corrupted filesystem?
What version of OS & Fsys do you have? (output of “sin ver” would
give that.)
David Gibbs
QNX Training Services
dagibbs@qnx.com
Thanks for response, I found that there was a directory with too much
entries, I moved it away and create again, works fine. (I am aware that it a
logical mistake of application which has to take care of directory size,
just I failed to derive this fact from the peculiar state of the application
process - reply to fsys - which I have never seen before).
Andy
“David Gibbs” <dagibbs@qnx.com> wrote in message
news:d8savs$1j6$2@inn.qnx.com…
Andrej Lucny <> andy@microstep-mis.com> > wrote:
Two computers have the same problem (so probably sw problem):ls -lR /
lists many files, then gets stuck. (no error reported)
sin shows that ls remains REPLY-blocked to FsysWhat does “sin -Pls fi” give? That should try to give what file
the ls was trying to access when it blocked.Have you run a chkfsys on all your partitions? Is it possible
you might have a corrupted filesystem?What version of OS & Fsys do you have? (output of “sin ver” would
give that.)-David
David Gibbs
QNX Training Services
dagibbs@qnx.com
Andrej Lucny <andy@microstep-mis.com> wrote:
Thanks for response, I found that there was a directory with too much
entries, I moved it away and create again, works fine. (I am aware that it a
logical mistake of application which has to take care of directory size,
just I failed to derive this fact from the peculiar state of the application
process - reply to fsys - which I have never seen before).
Hm… it wouldn’t seem obvious at first – but yup. The ls was asking
for the contents, and it was taking Fsys a LONG time to come up with
the answer, so while ls was waiting for the answer, it was REPLY blocked
on Fsys.
And, yeah, QNX uses a linear search of directories, so very large
directories will make things quite inefficient.
David Gibbs
QNX Training Services
dagibbs@qnx.com
Solved, stupid problem, there was a directory with large amount of files.
“Andrej Lucny” <andy@microstep-mis.com> wrote in message
news:d8s76h$sba$1@inn.qnx.com…
Two computers have the same problem (so probably sw problem):
ls -lR /
lists many files, then gets stuck. (no error reported)
sin shows that ls remains REPLY-blocked to Fsys(Some tasks from application software do the same - those which works with
filesystem too intesive, other works fine).Any advice ?
Andy