Anand Avati wrote:
OK, this is getting serious.
I have just discovered that the contents of my .viminfo has somehow been
clobbered by a .pine-debug file. It almost smells like it might be a leaky
pointer stomp. This may or may not be related to bug 126.
I have also just found that some of my log files are similarly corrputed
(nvidia-installer.log seems to have parts of the syslog message log in it!).
Do you have io-cache in your config? Can you attach the .viminfo and
.pine-debug files to bug #163?
Also, do you have a high entry-timeout or attr-timeout specified in
your mount options?
No. My gluster root mount options are:
defaults,noatime,nodiratime,direct-io-mode=off,log-file=/dev/null,log-level=NONE
The underlying ext3 file system is mounted with default parameters
(rw,data=ordered according to /proc/mounts)
Gordan
