Date: Mon, 12 Sep 2011 19:05:31 -0500 From: Gary Gatten <Ggatten@waddell.com> Cc: "'questions@freebsd.org'" <questions@freebsd.org> Subject: Re: Crash when copying large files Message-ID: <12880_1315872332_4E6E9E4C_12880_4522_1_D9B37353831173459FDAA836D3B43499C803FA12@WADPMBXV0.waddell.com> In-Reply-To: <8732CB9D-4085-47B6-A9F2-0EC9A3351D26@mac.com>
next in thread | previous in thread | raw e-mail | index | archive | help
ftp the large files, then tar? I like the rsync idea too. ----- Original Message ----- From: Chuck Swiger [mailto:cswiger@mac.com] Sent: Monday, September 12, 2011 06:42 PM To: Toomas Aas <toomas.aas@raad.tartu.ee> Cc: questions@freebsd.org <questions@freebsd.org> Subject: Re: Crash when copying large files Hi-- On Sep 12, 2011, at 2:14 PM, Toomas Aas wrote: > I've mounted the new FS under /mnt and use tar to transfer the files: >=20 > cd /mnt > tar -c -v -f - -C /docroot . | tar xf - You probably wanted -p flag on the extract side. The manpage recommends one of the following constructs: To move file hierarchies, invoke tar as tar -cf - -C srcdir . | tar -xpf - -C destdir or more traditionally cd srcdir ; tar -cf - . | (cd destdir ; tar -xpf -) However, this isn't going to resolve the system panic'ing. Certainly, that's not a reasonable behavior... :-) > It seems that these large files cause a problem. Sometimes when the proce= ss reaches one of these files, the machine reboots. It doesn't create a cra= shdump 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 th= e process three times now, and caused the machine to crash as it reaches on= e or another large file. Any ideas what I should do to avoid the crash? Right, a machine with 8GB of RAM isn't going to be able to dump to a 2GB sw= ap area. (Although, I seem to recall some folks working on compressed cras= h dumps, but I don't know what state that is in.) But you can set hw.physm= em in loader.conf to limit the RAM being used to 2GB so you can generate a = crash dump if you wanted to debug it further. How big are your multi-GB files, anyway? If you want a workaround to avoid the crash, consider using either rsync or= dump/restore to copy the filesystem, rather than using tar. Regards, --=20 -Chuck _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" <font size=3D"1"> <div style=3D'border:none;border-bottom:double windowtext 2.25pt;padding:0i= n 0in 1.0pt 0in'> </div> "This email is intended to be reviewed by only the intended recipient and may contain information that is privileged and/or confidential. If you are not the intended recipient, you are hereby notified that any review, use, dissemination, disclosure or copying of this email and its attachments, if any, is strictly prohibited. If you have received this email in error, please immediately notify the sender by return email and delete this email from your system." </font>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?12880_1315872332_4E6E9E4C_12880_4522_1_D9B37353831173459FDAA836D3B43499C803FA12>