Thanks for mentioning this, Brent. I have only 256MB of memory,
and I have a single processor. I have insmod version 2.3.14.

-Gene


Brent A Johnson wrote:
> 
> Gene,
> 
> If you have over 1GB of memory or an SMP processor, did you use
> the modified insmod to install the client?
> 
> -Brent
> 
> >Hi, I've been trying to troubleshoot this problem I'm
> >having with AFS on my machine for several weeks without
> >any success. I've done what I can to find the answer on
> >the web somehwere without success either.
> >
> >Anyhow, I have a RedHat 6.2 linux machine (linux kernel
> >2.2.14 running on an i686 machine, vendor: VA Linux)
> >and I have AFS 3.6 running on it. Through AFS, I can
> >read files off of other servers on the AFS network. I
> >can even create a file (for example, using touch) or
> >delete a file, so I can at least alter directory info.
> >But I cannot WRITE to a file on another server. For
> >example, if I try 'cat > file1' then a file file1 is
> >created, but I cannot write to it.
> >
> >Allow me to be a little more specific about what I mean
> >by "cannot write to it": at the moment that anything is
> >written to a file on AFS, my machine completely hangs.
> >Everything is frozen; mouse won't move, all processes hang!
> >I have to reboot the machine.
> >
> >This is very reproducible.
> >
> >I have checked AFS quotas, AFS user and group id's,
> >and flushed the AFS cache a few times. Nothing seems
> >to help. I've put the cache on a separate disk partition
> >to ensure that it has enough disk space, and made sure
> >that the appropriate AFS servers are in my CellServDB file.
> >
> >The only item I have which may or may not be a clue is
> >from the /var/log/messages file from startup. The loading
> >of afs appears to go just fine, with cache and servers
> >loading appropriately. But later, further down the messages
> >comes an item from the kernel:
> >
> >Nov  6 10:56:20 genesis kernel: afs: failed to store file
> >(14)
> >
> >If anyone has any ideas, please let me know. Thanks,
> >
> >-Gene Van Buren
> >

Reply via email to