On Tue, 10 Mar 2015, Peng Yu wrote: > > > On Tuesday, March 10, 2015, Benjamin Coddington <bcodding@xxxxxxxxxx> wrote: > On Mon, 9 Mar 2015, Peng Yu wrote: > > > Hi, > > > > I have a home directory from an ubuntu server shared to multiple other > > ubuntu servers as the home directory (the default login shell is bash > > on these servers) via NFS (see the following configuration in > > /etc/exports from the NFS server). > > > > /mnt/home 172.17.0.0/16(fsid=2,rw,insecure,no_subtree_check,sync,no_root_squash) > > > > autofs is used to mount the NFS on the client servers (see the > > following configuration). > > > > ~$ cat /etc/auto.master > > +auto.master > > /home /etc/auto.home --timeout=90 > > ~$ cat /etc/auto.home > > * -fstype=nfs4,rw,intr,fsc nsfserver:/mnt/home/& > > > > But I frequently end up with a situation when ~/.bash_history is not > > readable which blocks the logins to these client servers. I feel that > > this may be related with concurrent write to ~/.bash_history from > > these servers, which somehow screw up NFS. > > Hi Peng, what do you have that supports your feeling that the problem is > conflicts on the ~/.bash_history file? It's hard to help without more > information. > > > The login process hangs when a line related to ~/.bash_history in ~/.bashrc is being loaded. At that time, cat ~/.bash_history > also hangs, but stat the file works fine. After I delete ~/.bash_history, the login process stops hanging. > > The real difficulty is to reliably repoduce this problem in order to pinpoint the exact cause of the problem with nfs. So far I > only see the problem with ~/.bash_history, it is hard to believe this problem is related with the actual filename. A logic > conclusion is that it must be somehow related with how this file is written. A network capture would be a good next step toward finding the problem. Ben
