So, if you remount the filesystem, you don't get "?" when you "ls"? If this is the case, then I suspect that OrangeFS isn't handling an error condition correctly, resulting in incorrect inode information. When you run your tests, if you will turn on OrangeFS kernel debugging on the client, I may see where the problem is happening.
To turn on the appropriate kernel debug flags while the system is running: echo "file" > /proc/sys/pvfs2/kernel-debug The kernel debug messages will appear in your /var/log/messages file (or wherever your system messages go on your system). I would only need to see the messages from a test that failed. Becky On Thu, May 17, 2012 at 9:36 AM, Andrew Savchenko <[email protected]> wrote: > On Wed, 16 May 2012 16:44:23 -0400 Becky Ligon wrote: > > Another thought: after you get a failed make and you cannot access a > file > > through the kernel, what happens if you reboot the kernel? Do you still > > get "?" in your "ls" output? > > Perhaps I wrote too much and a point was lost. As I mention before, it > is sufficient just to unmount filesystem on a buggy client and mount > it againt (or just issue mount -o remount) to regain a normal access > to a faulty file(s). Of course, kernel reboot does the same, but it is > an overkill. > > Best regards, > Andrew Savchenko > -- Becky Ligon OrangeFS Support and Development Omnibond Systems Anderson, South Carolina
_______________________________________________ Pvfs2-users mailing list [email protected] http://www.beowulf-underground.org/mailman/listinfo/pvfs2-users
