From owner-freebsd-questions@freebsd.org Tue Jan 5 14:24:52 2016 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 77A29A62412 for ; Tue, 5 Jan 2016 14:24:52 +0000 (UTC) (envelope-from vsasjason@gmail.com) Received: from mail-wm0-x232.google.com (mail-wm0-x232.google.com [IPv6:2a00:1450:400c:c09::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 250D512D8; Tue, 5 Jan 2016 14:24:52 +0000 (UTC) (envelope-from vsasjason@gmail.com) Received: by mail-wm0-x232.google.com with SMTP id l65so24699231wmf.1; Tue, 05 Jan 2016 06:24:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=tdFnU6vpCiYjnqHS86sTAakTLx6gDc5a9pfA6dXZ1pA=; b=l/t+aiaeguQLrS02rqcM8ZPPfpzZLGSDPZqPBIZMs4xABhs94w5iOusai2WualoXNj sN/kWZDiSwMvkzFCcWmzBaDq17qHLKtyIlecKG7hEdOPzRtalxrJ51PDxccH4FsMxEBu yIt2eUhYLzUDqRlX/4Q9hauc7TzsgHKENFHvB4mKLBrxsYhb+E259ZbXvolHgx3EzHnb UDwcQBjnGS6BI1xoWXTUmjpZBD/LowFbslyCp1aW+8X8r4nBl1wWk6Fo7QYtqbpKi+rk DfdMZh+O2ehtABvk0U0UfJvm6DNd8BXNYYDhoJKO4/v5fX5giKDhe607QIkYknhiwHwx jzjw== MIME-Version: 1.0 X-Received: by 10.28.54.78 with SMTP id d75mr4549049wma.6.1452003890534; Tue, 05 Jan 2016 06:24:50 -0800 (PST) Received: by 10.194.76.207 with HTTP; Tue, 5 Jan 2016 06:24:50 -0800 (PST) Received: by 10.194.76.207 with HTTP; Tue, 5 Jan 2016 06:24:50 -0800 (PST) In-Reply-To: <568BD0FB.5020303@FreeBSD.org> References: <568BC37C.2010903@FreeBSD.org> <568BD0FB.5020303@FreeBSD.org> Date: Tue, 5 Jan 2016 17:24:50 +0300 Message-ID: Subject: Re: There is problem during dump/restore. From: Anton Sayetsky To: Matthew Seaman Cc: FreeBSD Questions , Shahin Hasanov Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Jan 2016 14:24:52 -0000 5 =D1=8F=D0=BD=D0=B2. 2016 =D0=B3. 16:20 =D0=BF=D0=BE=D0=BB=D1=8C=D0=B7=D0= =BE=D0=B2=D0=B0=D1=82=D0=B5=D0=BB=D1=8C "Matthew Seaman" =D0=BD=D0=B0=D0=BF=D0=B8=D1=81=D0=B0=D0=BB: > > On 05/01/2016 13:39, Shahin Hasanov wrote: > > Thank you Matthew, > > I have two HDD da0,da1 > > da0 is 147GB - ufs > > da1 is 1.1TB - zfs > > Ah -- there is your problem. dump/restore only works with UFS. > > However, if what you want to do is copy a directory heirarchy from one > place to another preserving ownership and permissions and so forth, then > there are very many ways to do that. > > Two suggestions: > > 1) Using stuff from the base system only: > > # cd /src/dir > # tar -cf - . | ( cd /dest/dir ; tar -xvf - ) I think that's better to replace above 2 commands with one following: # tar cf - -C /src/dir . | tar xf -C /dest/dir - > 2) Using rsync(1) from ports: > > # rsync -avx /src/dir/ /dest/dir/ > > (Note the trailing slashes on the directory paths -- they're