|
|
|
FAQ |
|
This is supposed to be the "Known problems that can be solved" section of the filesystem & is deliberately kept small as we dont want to desell the product.
Q 1. New Virtual Directories Do Not Show Results ? A. Most the reason the reason may be that the query format is not in the language produced by the Query Grammer. Other common mistake can be the "space" in the filedname of the query. If ORION is compiled using the Debug options the ofs_mkdir function will produce hints as to why the query is wrong. The debug information can be printed by using the command dmesg and searching for the string "ORION view: I fail to understand the query format.
Q 2. Changes dont get reflected in the view ? A. Check whether the directory under which the file is created is not a "sticky directory". Or you can try an Invalidate the in kernel recordset cache by running the program "<ORIONinstallRoot>/database/incalidateRSCache.out"
Q 3. I create new folders and some files are already in it which dont meet the criteria ? A. The only reason for this to happen is that the the a "sticky direcotory" with the same name was created earlier and the file which showed up were created in the that directory. Can be avoided by choosing a sligtly different filename or changing the "parent attribute" of the directories which show up in the folder. Be sure to rename the parent attribute to some valid path.
Q 4. Copy or cp sleeps when large number of files are copied? A. Get the pid of the sleeping process and run the "<ORIONinstallRoot>/database/stopHangman.out [pid]". Repeat the process until the cp completes this is due the update deamon not being able to handle large number of requests for updation as the number of threads are limited.
Q. 7. Cannot Create hardlink and Symlinks ? A. Hardlinks cannot be created because of the inherent limitation of the ORION design which maintains the ORIONView and ORIONstore as seperate filesystem. And the Linux Kernel Does not support hardlinks across filesystem. Symlinks don't make make much sense in the filesytem as dynamic as an ORIONView. Nevertheless the feature will be provided in later releases along with the hack for hard links.
Q 6. All procees Interacting with the ORION views sleep indefinately ? A. Check if both the userspace database deamons are running using the ps -e "cacheFaultHandler.out" & "updateDb.out". If not the try start them by running the specified exes from the "<ORIONinstallRoot>/database/". If this does not solve the problem stop using the filesytem views immidiately & try after a fresh restart. If the problem is reproducable submit a bug report wit the step to reproduce the problem. After such a condition the valididity or even the existance of files created is not guaranteed.
Q 7. SegFaults under Heavy Load Condition ? A. This is a know bug in the File system due the kswapd running the prune_dcache to free up some the memory used by the DNLC cache. This BUG is needs to be resolved but it beyond the understand of the creators of OFS. (with the current amount of understanding) . Patches to remove this bug are welcomed. |