Upgraded to 4.4 here and no problem with grep.
Try running memtest86, it be a problem with your memory
Oliver
Jed Reynolds wrote:
I'm seeing grep break when I grep large numbers of gzip files in /var/log. Posted bug on bugzilla. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=205534
Description of problem:
grep errors with:
*** glibc detected *** free(): invalid next size (normal): *** Aborted.
when doing recursive grep in /var/log, other places.
Version-Release number of selected component (if applicable): Linux 2.6.9-42.0.2.ELsmp 0x86_64, Linux 2.6.9-34.0.2.ELsmp i686
How reproducible:
Consistently on i686 and x86_64 boxes Centos4.4. Recently upgraded from CentOS 4.3 to 4.4. I have large /var/log directories with plenty of gzipped logs.
Steps to Reproduce:
- cd /var/log
- grep -ri "Check Spelling & Mumble" *
- (or) grep -ri "Check Spelling & Mumble" *gz
Actual results: Fails with: *** glibc detected *** free(): invalid next size (normal): *** Aborted.
Sometimes: *** glibc detected *** realloc(): invalid next size: 0x000.... *** Aborted.
Expected results: No failure.
Additional info:
Grepping 7GB of compressed logs on one server, grepping 4GB logs on other server. x86_64 Server had 35M or 3G+cache ram free; i686 server had 374M ram free, 960M+cache. _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos