Date: Thu, 24 Nov 2022 16:17:57 +0100 From: Nikos Vassiliadis <nvass@gmx.com> To: Alan Somers <asomers@freebsd.org> Cc: freebsd-fs@freebsd.org Subject: Re: filesystem created but no event in history Message-ID: <trinity-f0ecb1ab-16f9-4c32-8712-316004d16e55-1669303077413@3c-app-mailcom-bs05> In-Reply-To: <CAOtMX2hOdQdHsHpGixMPAu_wTuhAgtotAmKZ0QwfQo1TOvZ2rA@mail.gmail.com> References: <trinity-7bc22afb-ba3c-4d37-8fcd-1b85726e9063-1669287643921@3c-app-mailcom-bs05> <CAOtMX2hOdQdHsHpGixMPAu_wTuhAgtotAmKZ0QwfQo1TOvZ2rA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> Sent: Thursday, November 24, 2022 at 3:52 PM > From: "Alan Somers" <asomers@freebsd.org> > To: "Nikos Vassiliadis" <nvass@gmx.com> > Cc: freebsd-fs@freebsd.org > Subject: Re: filesystem created but no event in history > > On Thu, Nov 24, 2022 at 4:00 AM Nikos Vassiliadis <nvass@gmx.com> wrote: > > > > Hi, > > > > There was a new fs (danae/ROOT/12.4-RC2_2022-11-24_105735) created by freebsd-update > > > > > > root@danae:~ # zfs list -t all -r -o name,type,creation,origin danae | sed -n '1p; /105735/p' > > NAME TYPE CREATION ORIGIN > > danae/ROOT/12.4-RC2_2022-11-24_105735 filesystem Thu Nov 24 10:57 2022 danae/ROOT/default@2022-11-24-10:57:35-0 > > danae/ROOT/12.4-RC2_2022-11-24_105735@2022-11-24_11.10.48--1d snapshot Thu Nov 24 11:10 2022 - > > danae/ROOT/12.4-RC2_2022-11-24_105735@2022-11-24_11.10.52--1d snapshot Thu Nov 24 11:10 2022 - > > root@danae:~ # zfs list danae/ROOT/default@2022-11-24-10:57:35-0 > > NAME USED AVAIL REFER MOUNTPOINT > > danae/ROOT/default@2022-11-24-10:57:35-0 2.82M - 4.97G - > > root@danae:~ # > > > > > > I would expect that this event would be recorded in the pool's history but there is nothing there: > > root@danae:~ # zpool history danae | tail -20 > > 2022-11-24.00:00:05 zfs snapshot -r danae@2022-11-24_00.00.00--1m > > 2022-11-24.00:01:00 zfs destroy danae/ROOT/default@2022-10-24_00.00.00--1m > > 2022-11-24.00:01:00 zfs destroy danae/ROOT@2022-10-24_00.00.00--1m > > 2022-11-24.00:01:01 zfs destroy danae/tmp@2022-10-24_00.00.00--1m > > 2022-11-24.00:01:01 zfs destroy danae/usr/home@2022-10-24_00.00.00--1m > > 2022-11-24.00:01:01 zfs destroy danae/usr/ports@2022-10-24_00.00.00--1m > > 2022-11-24.00:01:01 zfs destroy danae/usr/src@2022-10-24_00.00.00--1m > > 2022-11-24.00:01:01 zfs destroy danae/usr@2022-10-24_00.00.00--1m > > 2022-11-24.00:01:01 zfs destroy danae/var/audit@2022-10-24_00.00.00--1m > > 2022-11-24.00:01:01 zfs destroy danae/var/crash@2022-10-24_00.00.00--1m > > 2022-11-24.00:01:01 zfs destroy danae/var/log@2022-10-24_00.00.00--1m > > 2022-11-24.00:01:01 zfs destroy danae/var/mail@2022-10-24_00.00.00--1m > > 2022-11-24.00:01:01 zfs destroy danae/var/tmp@2022-10-24_00.00.00--1m > > 2022-11-24.00:01:01 zfs destroy danae/var@2022-10-24_00.00.00--1m > > 2022-11-24.00:01:06 zfs destroy danae@2022-10-24_00.00.00--1m > > 2022-11-24.11:10:52 zfs snapshot -r danae@2022-11-24_11.10.48--1d > > 2022-11-24.11:10:56 zfs snapshot -r danae@2022-11-24_11.10.52--1d > > 2022-11-24.12:41:55 zfs create danae/nikos000 > > 2022-11-24.12:42:17 zfs rename danae/nikos000 danae/nikos001 > > > > I thought that the pool's history contains everything. > > Really confused, thanks in advance for your help > > Nikos > > Try "zpool history -i". > > Thanks a lot Alan! So bectl creates a snapshot and clones it to a new fs but these actions are considered internal. What do we really mean internal?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?trinity-f0ecb1ab-16f9-4c32-8712-316004d16e55-1669303077413>