This sounds to me like the dir_index option was applied to a file system
that didn't originally have it and an fsck -Df wasn't run at the time.
That may well be the most relevant information given here! I will
*certainly* give it a try.
Thank you!
--
To unsubscribe from this list go to the
Did you consider sharing a directory from the machine running distiller
and cifs-mounting it on the linux side to get ntfs behavior?
That is out of question. The Windows machines are graphic workstations
which are not all connected all the time and the Distiller service is
essential to the
I was under the impression that the Distiller app was running under
Windows. If it isn't, it doesn't make much sense for it to expect NTFS
filesystem semantics.
Yes, Distiller is running under Windows. When pages start to get ready,
one of the graphic operators opens Distiller on
I based my speculation on some observations I had made on some of my
own systems when I implemented dir_index. It so happens that, on that
system at least, a find /foo -print returns the filenames in sorted
order. Unfortunately, it isn't true on another system that I just
checked. So now I
On Fri, 23 Jan 2009, Miguel Medalha wrote:
This sounds to me like the dir_index option was applied to a file system
that didn't originally have it and an fsck -Df wasn't run at the time.
That may well be the most relevant information given here! I will *certainly*
give it a try.
I based
