From nobody Sat Jan 11 11:21:34 2025 X-Original-To: freebsd-fs@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 4YVbhd3YSxz5k6BC for ; Sat, 11 Jan 2025 11:22:09 +0000 (UTC) (envelope-from Alexander@Leidinger.net) Received: from mailgate.Leidinger.net (bastille.leidinger.net [89.238.82.207]) (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 ECDSA (P-256) client-digest SHA256) (Client CN "mailgate.leidinger.net", Issuer "E6" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4YVbhc3R5pz4HQ8 for ; Sat, 11 Jan 2025 11:22:08 +0000 (UTC) (envelope-from Alexander@Leidinger.net) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=leidinger.net header.s=outgoing-alex header.b=HjomgPw2; spf=pass (mx1.freebsd.org: domain of Alexander@Leidinger.net designates 89.238.82.207 as permitted sender) smtp.mailfrom=Alexander@Leidinger.net; dmarc=pass (policy=quarantine) header.from=leidinger.net List-Id: Filesystems List-Archive: https://lists.freebsd.org/archives/freebsd-fs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-fs@FreeBSD.org MIME-Version: 1.0 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=leidinger.net; s=outgoing-alex; t=1736594519; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=cN2E7EMEZwTwDSBgAf/7EYRfs2vf7/oDbcUEwV3qUHc=; b=HjomgPw2U7HWnRMANoBRqQ95ojN5LkNEjC1f2lPGu9/eoddFjNde8nfOdYkyRQKNt97QS3 As5amIaLrJl5s8YpYDIzIIJKQe7S0IKU0nDT8h4LClKF0i/XghzZ3cwplXdhZFP6kMRwKI /I2SCqptKJz/t31GubdE6QtEOZrtxfwWRFdMYo/9Z/DB3GjuRpROKxby8RrG+9zqMktqjf TH3oZYpBdB/nhQWMB2Iz0+ZjHYEcHyCAlfeusHJITM6mjkVXz872VcdRVVc7+joS/CNuxE 4mCu2H5+WcaZTlk7kHqGscZ3wRZlGfGidhhaacxhXEZk2zEeTLs6sQPsogC1Sw== Date: Sat, 11 Jan 2025 12:21:34 +0100 From: Alexander Leidinger To: andy thomas Cc: freebsd-fs@freebsd.org Subject: Re: How can I tell when ZFS has finished creating a snapshot? In-Reply-To: <856588185.13572.1736593439701@localhost> References: <856588185.13572.1736593439701@localhost> Message-ID: <357554e1ae8745a7dfc8701d4bbb45ac@Leidinger.net> Organization: No organization, this is a private message. Content-Type: multipart/signed; protocol="application/pgp-signature"; boundary="=_93c3eae43c412c4537a29bd1381e61a4"; micalg=pgp-sha256 X-Rspamd-Queue-Id: 4YVbhc3R5pz4HQ8 X-Spamd-Bar: ----- X-Spamd-Result: default: False [-5.10 / 15.00]; SIGNED_PGP(-2.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_SHORT(-1.00)[-0.999]; DMARC_POLICY_ALLOW(-0.50)[leidinger.net,quarantine]; R_SPF_ALLOW(-0.20)[+mx]; R_DKIM_ALLOW(-0.20)[leidinger.net:s=outgoing-alex]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; TO_DN_SOME(0.00)[]; ARC_NA(0.00)[]; HAS_ORG_HEADER(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ASN(0.00)[asn:34240, ipnet:89.238.64.0/18, country:DE]; DKIM_TRACE(0.00)[leidinger.net:+]; MID_RHS_MATCH_FROM(0.00)[]; MISSING_XM_UA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCVD_COUNT_ZERO(0.00)[0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; MLMMJ_DEST(0.00)[freebsd-fs@freebsd.org]; HAS_ATTACHMENT(0.00)[] This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --=_93c3eae43c412c4537a29bd1381e61a4 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed Am 2025-01-11 12:03, schrieb Ronald Klop: > For example: > > After creating a snapshot you delete a file in the original file > system. The file is still in the snapshot. So the size of the file will > be accounted to the snapshot. > > Modifying a file will give similar effect. The 'old' parts of the file > are only available via the snapshot so will be accounted to the > snapshot. Or in other words, the snapshot does not grow at all, it is read-only. Space is attributed to a snapshot if the live dataset doesn't reference a piece of data. Data which is removed or changed in the live dataset since the snapshot was taken is what you see in USED. You can use "zfs diff" to see where data has changed. I'm not sure if such data is attributed to the oldest or the most recent snapshot, but it's one of both (I guess to the oldest). Bye, Alexander. > Regards, > Ronald. > > Van: andy thomas > Datum: 11 januari 2025 11:40 > Aan: heasley > CC: freebsd-fs@freebsd.org > Onderwerp: Re: How can I tell when ZFS has finished creating a > snapshot? > >> But what could be increasing the size of the snapshot after it was >> created? Right now, yesterday's snapshot made at 14:45 UTC (nearly 22 >> hours ago) has grown to 468MB: >> >> root@clustor2:~ # date >> Sat Jan 11 10:31:05 GMT 2025 >> root@clustor2:~ # zfs list -t snapshot >> NAME USED AVAIL REFER MOUNTPOINT >> clustor2/ma@2025-01-10_14.45.00 468M - 3.09T - >> >> It's true the size this file system reported by 'zfs list' has >> increasesd from 3.09TB yesterday to 3.10TB now (it's used for storing >> user data in an HPC that currently has about 700 jobs running on it) >> but it's very strange that a snapshot supposedly "set in stone" at the >> time it is created should continue to grow afterwards! >> >> Andy >> >> On Fri, 10 Jan 2025, heasley wrote: >> >>> Fri, Jan 10, 2025 at 06:52:43PM +0000, andy thomas: >>>> Is there a way to find out the status of a snapshot creation? >>> >>> it should be near-instantaneous. "USED" would only change if files >>> in >>> the snapshot are deleted or overwritten. >>> >>> >> >> ----------------------------- >> Andy Thomas, >> Time Domain Systems >> >> Tel: +44 (0)7815 060872 >> https://www.time-domain.co.uk >> >> ------------------------- -- http://www.Leidinger.net Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF http://www.FreeBSD.org netchild@FreeBSD.org : PGP 0x8F31830F9F2772BF --=_93c3eae43c412c4537a29bd1381e61a4 Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc; size=833 Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEER9UlYXp1PSd08nWXEg2wmwP42IYFAmeCVE0ACgkQEg2wmwP4 2IYNzBAAhOV/ESYtjZ1l85hp567dXK5Dc0JId+YwYJc1dHQ13l+tFLIGXmKbVsve z5/a5c3pk9McoSh8QGlTIM7PuPl3fHpgQZJHNLyAQht9TfMolAUuvur6T2jis01K TdVSHttgSEiyaUmIMXuniq4gkU2l9s+70/yL5sv/zIH/l+Yvlf6uC7M5MYnX30cC W3gjZ2TABuMQ5/sUe7BP+crR9se9e4vmQ4RvAyTECwGbISjO5sKWXNjGPOGizDdR SEKl9DwadusiKeGdulLHLFBKaujrac/ULSMabnb3B5U2phgLGqhP1gvJ9P3Qey5P gVNFIQ1TnPoTuK4WyeZQd2cD/7HMKbB2PbEUUpyXwO0zfboJKMCa8oAwCJn2Ylg8 MWmHUutyFC/8G4OEP/OTxBm8osQcR8mSnSKH3BqBZovAiWAbMUNonhqCwkUUfy5a A941SaL+ek2ubogcf2m7n953XoD8ATyNhqSEeVQhQBev8bqecTPE5/r0SiceDm+I oYBrkGfjM1oeemS41jBw1vG/wmOxatkgs1O4Cf4YUakARW8Psu0FWUtkSmiQWn9B OOBddmg5TNNvOl1KyTbyUdiLBPHojfNIA+laW14lKD/C2LKZ27qSYj6Wf2oZZkhT flMrfpYRDDeh2kyITwn0T0nGdmkbpAECbQTpF1gsEnFQE4f4XQ0= =QsO9 -----END PGP SIGNATURE----- --=_93c3eae43c412c4537a29bd1381e61a4--