From owner-freebsd-stable@FreeBSD.ORG Sat Dec 22 15:07:55 2012 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 49C05F3C for ; Sat, 22 Dec 2012 15:07:55 +0000 (UTC) (envelope-from mi+thun@aldan.algebra.com) Received: from smtp02.lnh.mail.rcn.net (smtp02.lnh.mail.rcn.net [207.172.157.102]) by mx1.freebsd.org (Postfix) with ESMTP id D92488FC0A for ; Sat, 22 Dec 2012 15:07:54 +0000 (UTC) Received: from mr17.lnh.mail.rcn.net ([207.172.157.37]) by smtp02.lnh.mail.rcn.net with ESMTP; 22 Dec 2012 10:07:55 -0500 Received: from smtp01.lnh.mail.rcn.net (smtp01.lnh.mail.rcn.net [207.172.4.11]) by mr17.lnh.mail.rcn.net (MOS 4.3.4-GA) with ESMTP id BVU04741; Sat, 22 Dec 2012 10:07:54 -0500 X-Auth-ID: anat Received: from pool-173-70-92-11.nwrknj.fios.verizon.net (HELO [192.168.1.8]) ([173.70.92.11]) by smtp01.lnh.mail.rcn.net with ESMTP; 22 Dec 2012 10:07:54 -0500 Message-ID: <50D5CCCA.2050000@aldan.algebra.com> Date: Sat, 22 Dec 2012 10:07:54 -0500 From: "Mikhail T." User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:14.0) Gecko/20120820 Thunderbird/14.0 MIME-Version: 1.0 To: stable@FreeBSD.org Subject: xz(1) keeps SEGFAULT-ing Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Dec 2012 15:07:55 -0000 Hello! I've set up several nightly backups all using the pipe-chain of dump | xz -9 | ccrypt > /remote/backups/fs.xz.cpt On one system these just work every night without a problem. On another I see xz SEGFAULT-ing about 90% through almost every night for one of the filesystems (the bigger of the two). This is, what cron emails me: DUMP: WARNING: should use -L when dumping live read-write filesystems! DUMP: Date of this level 1 dump: Sat Dec 22 03:23:00 2012 DUMP: Date of last level 0 dump: Thu Dec 6 01:23:02 2012 DUMP: Dumping /dev/ad4s1g (/home) to standard output DUMP: mapping (Pass I) [regular files] DUMP: Cache 16 MB, blocksize = 65536 DUMP: mapping (Pass II) [directories] DUMP: estimated 2157823 tape blocks. DUMP: dumping (Pass III) [directories] DUMP: dumping (Pass IV) [regular files] DUMP: 11.50% done, finished in 0:38 at Sat Dec 22 04:07:55 2012 DUMP: 17.80% done, finished in 0:46 at Sat Dec 22 04:20:37 2012 DUMP: 24.32% done, finished in 0:46 at Sat Dec 22 04:26:05 2012 DUMP: 31.23% done, finished in 0:44 at Sat Dec 22 04:28:27 2012 DUMP: 36.16% done, finished in 0:44 at Sat Dec 22 04:33:34 2012 DUMP: 43.21% done, finished in 0:39 at Sat Dec 22 04:33:51 2012 DUMP: 54.86% done, finished in 0:28 at Sat Dec 22 04:28:14 2012 DUMP: 60.63% done, finished in 0:25 at Sat Dec 22 04:30:24 2012 DUMP: 65.83% done, finished in 0:23 at Sat Dec 22 04:32:47 2012 DUMP: 70.54% done, finished in 0:20 at Sat Dec 22 04:35:18 2012 DUMP: 75.15% done, finished in 0:18 at Sat Dec 22 04:37:37 2012 DUMP: 80.28% done, finished in 0:14 at Sat Dec 22 04:39:10 2012 DUMP: 85.57% done, finished in 0:10 at Sat Dec 22 04:40:23 2012 DUMP: 90.50% done, finished in 0:07 at Sat Dec 22 04:41:46 2012 DUMP: SIGSEGV: ABORTING! DUMP: DUMP: DUMP: SIGSEGV: ABORTING! SIGSEGV: ABORTING! SIGSEGV: ABORTING! DUMP: SIGSEGV: ABORTING! Following xz's fault, all other processes (dump, ccrypt, sh) dump their cores to, but, according to dmesg, the culprit is always xz. According to core, the fault is somewhere inside liblzma.so.5. I recompiled the library to enable debugging and am trying to investigate, but, perhaps, someone has already run into this? Both systems used to run FreeBSD-8/amd64, when I first set the jobs up. I have since upgraded the troublesome server to 9.1, but that did not fix the problem. The remote filesystem (where ccrypt writes encrypted output) is mounted via smbfs on both servers, but I doubt that matters... Any ideas? Thanks, -mi