Morning Derrick, On Mon, Aug 10, 2009 at 8:57 AM, Derrick Brashear <[email protected]> wrote:
> On Mon, Aug 10, 2009 at 11:43 AM, John W Higgins<[email protected]> wrote: > > Good Morning Jeffrey, > > > > On Mon, Aug 10, 2009 at 3:53 AM, Jeffrey Altman > > <[email protected]> wrote: > >> > >> I'm just wondering. Why do you believe that the file server > >> (or other) processes are writing to your volumes as opposed to > >> reading from them or writing to log (or other) files? > >> > > > > First, thanks for the response..... > > > > I'm basing this on a couple of things - first when I shut down the > OpenAFS > > server the disk activity stops. Second, I ran iotop to examine the io > usage > > and the writes were going to the 2 loop devices I was using to test > OpenAFS > > and nothing else is using that area but OpenAFS. > > I assume iotop lists process names; Given that there's no process > called OpenAFS, what did it really tell you? > Does it list fds? The process was called fileserver and it was the /usr/libexec/openafs/fileserver (I think that's the right location) process that was making the writes. > > > > And finally, top shows > > fileserver popping up every 10 seconds when the disk activity to the loop > > devices is occurring and then it goes back to sleep. > > > > Is it possible that because I'm using loop devices something out of the > norm > > is occuring? > > Unlikely. > > What version of OpenAFS? I suppose it's possible the background sync > thread is in some way hurting you. > I'm running 1.4.9 (which I know it's the most current so I'm more then happy to upgrade if that appears to be the issue). John
