From nobody Wed Apr 27 10:03:32 2022 X-Original-To: ports@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 5A1FC1AB09BE for ; Wed, 27 Apr 2022 10:03:36 +0000 (UTC) (envelope-from ml@netfence.it) Received: from soth.netfence.it (mailserver.netfence.it [78.134.96.152]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mailserver.netfence.it", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4KpDpv1TkXz3l83 for ; Wed, 27 Apr 2022 10:03:35 +0000 (UTC) (envelope-from ml@netfence.it) Received: from [10.1.2.18] (alamar.local.netfence.it [10.1.2.18]) (authenticated bits=0) by soth.netfence.it (8.17.1/8.17.1) with ESMTPSA id 23RA3Wwx091700 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NO) for ; Wed, 27 Apr 2022 12:03:32 +0200 (CEST) (envelope-from ml@netfence.it) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=netfence.it; s=202203; t=1651053812; bh=gMudi2SjaMO0v37/E8ScuL6NE1/itXzVdDiF7YzoyeY=; h=Date:Subject:To:References:From:In-Reply-To; b=AN9+t/wo/hZdMhG94MiifYyrRSediJ/ANB2ObJt1wDSPoO7884tcrzFqAOl3Y94jv DSSD/Af74GYNTxRtqA0GaPzrS51AES+zntoSBTsZiaMgirgqPYd31TgSY9scG/4gpG BM+GCOg0OGjX6mhsP+TymCQKqkaMstCof3hs6PGc= X-Authentication-Warning: soth.netfence.it: Host alamar.local.netfence.it [10.1.2.18] claimed to be [10.1.2.18] Message-ID: <537de4e5-1f98-8abc-a2f2-c974dc01b897@netfence.it> Date: Wed, 27 Apr 2022 12:03:32 +0200 List-Id: Porting software to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-ports List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-ports@freebsd.org X-BeenThere: freebsd-ports@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:91.0) Gecko/20100101 Thunderbird/91.8.1 Subject: Re: Fill a disk with more recent files Content-Language: en-US To: ports@freebsd.org References: <40ed09f1-f4b9-d4bf-26fa-9a93e73b09bb@netfence.it> From: Andrea Venturoli In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4KpDpv1TkXz3l83 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=netfence.it header.s=202203 header.b="AN9+t/wo"; dmarc=pass (policy=none) header.from=netfence.it; spf=pass (mx1.freebsd.org: domain of ml@netfence.it designates 78.134.96.152 as permitted sender) smtp.mailfrom=ml@netfence.it X-Spamd-Result: default: False [-4.00 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[netfence.it:s=202203]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:78.134.96.152]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[ports@freebsd.org]; HAS_XAW(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-1.000]; TO_DN_NONE(0.00)[]; DKIM_TRACE(0.00)[netfence.it:+]; DMARC_POLICY_ALLOW(-0.50)[netfence.it,none]; NEURAL_HAM_SHORT(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; MLMMJ_DEST(0.00)[ports]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:35612, ipnet:78.134.0.0/17, country:IT]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] X-ThisMailContainsUnwantedMimeParts: N On 4/27/22 11:50, Tomek CEDRO wrote: > If you want to enforce particular sort order you will have to call > rsync from another tool. Probably ls / find, sort, then rsync, maybe a > dedicated Python script. Sure, this was what I was thinking. I just wanted to avoid doing this if it already existed. > That also depends on how do you want to treat existing backup files. > Do you want to delete them all completely on backup, or remove oldest > files in order to make a room for the new files? Ideally the latter, although I don't think in the end it would make any difference (as it probably would mean delete them all). > Have you considered ZFS (full/incremental) snapshots and partitioning > your pool into areas based on backup priority? No, this is completely inapplicable for several reasons (data is on a Linux based NAS which can only use Ext3, data is already prioritized and I'm just talking about high priority, etc...). > With ZFS you can frequently create incremental snapshots for important > locations and stream them into a backup file. I know and I'm using this in several other situations. However here I'm collecting data from several sources (including Windows PCs, so ZFS is out of question). bye & Thanks av.