From owner-freebsd-questions@FreeBSD.ORG Mon Sep 12 23:33:29 2011 Return-Path: Delivered-To: questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 46058106566B for ; Mon, 12 Sep 2011 23:33:29 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mx02.qsc.de (mx02.qsc.de [213.148.130.14]) by mx1.freebsd.org (Postfix) with ESMTP id 0ABC78FC13 for ; Mon, 12 Sep 2011 23:33:28 +0000 (UTC) Received: from r56.edvax.de (port-92-195-14-151.dynamic.qsc.de [92.195.14.151]) by mx02.qsc.de (Postfix) with ESMTP id 3E45F1DAD7; Tue, 13 Sep 2011 01:33:28 +0200 (CEST) Received: from r56.edvax.de (localhost [127.0.0.1]) by r56.edvax.de (8.14.5/8.14.5) with SMTP id p8CNXRmU002498; Tue, 13 Sep 2011 01:33:27 +0200 (CEST) (envelope-from freebsd@edvax.de) Date: Tue, 13 Sep 2011 01:33:27 +0200 From: Polytropon To: Toomas Aas Message-Id: <20110913013327.f3bdc95d.freebsd@edvax.de> In-Reply-To: <20110913001445.15346yix2qz78j4s@webmail.raad.tartu.ee> References: <20110913001445.15346yix2qz78j4s@webmail.raad.tartu.ee> Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: questions@freebsd.org Subject: Re: Crash when copying large files X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Polytropon List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Sep 2011 23:33:29 -0000 On Tue, 13 Sep 2011 00:14:45 +0300, Toomas Aas wrote: > Hello! > > I'm trying to move a filesystem to a new larger RAID volume. The old > filesystem was using gjournal, and I have also created the new > filesystem with gjournal. The FS in question holds the DocumentRoot of > our web server, and in its depths, a couple of fairly large (several > gigabytes) files are lurking. > > I've mounted the new FS under /mnt and use tar to transfer the files: > > cd /mnt > tar -c -v -f - -C /docroot . | tar xf - > > It seems that these large files cause a problem. Sometimes when the > process reaches one of these files, the machine reboots. It doesn't > create a crashdump in /var/crash, which may be because the system has > less swap (2 GB) than RAM (8 GB). Fortunately the machine comes back > up OK, except that the target FS (/mnt) is corrupt and needs to be > fsck'd. I've tried to re-run the process three times now, and caused > the machine to crash as it reaches one or another large file. Any > ideas what I should do to avoid the crash? The par program operates on a per-file basis. In case that causes a problem, try to leave this route and use the "old- fashioned" tools dump and restore. Make sure the file system isn't mounted, then use: # cd /your/target/directory # dump -0 -f - /dev/ | restore -r -f - wheree refers to the device you've initially mounted /mnt from. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...