From owner-freebsd-stable@FreeBSD.ORG Sat Dec 22 16:39:26 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 0F95EF46 for ; Sat, 22 Dec 2012 16:39:26 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-f177.google.com (mail-wi0-f177.google.com [209.85.212.177]) by mx1.freebsd.org (Postfix) with ESMTP id 8E5998FC0A for ; Sat, 22 Dec 2012 16:39:25 +0000 (UTC) Received: by mail-wi0-f177.google.com with SMTP id hm2so3368765wib.10 for ; Sat, 22 Dec 2012 08:39:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=8j2ycBiUReFkT5cKdKvFE/7h4EwFbeeZMGwlmlL+Gbs=; b=xhG2veJ+aO3E5SrDPKybLuF3QTVmBeAxLrigP2QNAOMx/rzkyPPiLpTbse1H9Yppxo peVg2dL7VwKtWMM5jQcyIToHuYxterRWwOy/Y3gMhg8BjMBuHWsh//fwyN6RJrPsSlbu 7Fsh4Ldpa0tP9X8qC/sCFoaPIz1deGac4gVKjRvSiePaknCsZuKWcAaihfltNg/S6QON cG7CGnesr3mB5vrztmkZcxGcKd9xLB8RXNXu+BG+ON3Wug75MU/IbVa7dShoB5DdOCCz 2QhghShBtmR7grYFSPgY7DWY5NRdwBis8KMCft5awybhoHgSF3cflNjotn5h6XDaRF3D 8vTA== MIME-Version: 1.0 Received: by 10.194.179.34 with SMTP id dd2mr29138932wjc.1.1356194364284; Sat, 22 Dec 2012 08:39:24 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.217.57.9 with HTTP; Sat, 22 Dec 2012 08:39:23 -0800 (PST) In-Reply-To: <50D5CCCA.2050000@aldan.algebra.com> References: <50D5CCCA.2050000@aldan.algebra.com> Date: Sat, 22 Dec 2012 08:39:23 -0800 X-Google-Sender-Auth: qsaOXc8INaKwcpcGQ-YT65oq7aM Message-ID: Subject: Re: xz(1) keeps SEGFAULT-ing From: Adrian Chadd To: "Mikhail T." Content-Type: text/plain; charset=ISO-8859-1 Cc: stable@freebsd.org 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 16:39:26 -0000 Is it dumping core? Adrian On 22 December 2012 07:07, Mikhail T. wrote: > 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 > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"