[moving over to caiman-discuss ...] Antonello Cruz wrote: > I am seeing some confusing output from 'beadm list -a'. Basically, it is > telling me I have snapshots that are older than the parent filesystem. > > > [acruz at zurca]% beadm list -a osol-121 > BE/Dataset/Snapshot Space Policy Created > ------------------- ----- ------ ------- > osol-121 > rpool/ROOT/osol-121 9.87G static 2009-08-20 08:14 > rpool/ROOT/osol-121 at 2009-07-10-00:36:17 23.60M static 2009-07-09 17:36 > rpool/ROOT/osol-121 at 2009-07-13-22:09:26 13.56M static 2009-07-13 15:09 > rpool/ROOT/osol-121 at 2009-08-20-15:14:53 12.67M static 2009-08-20 08:14 > rpool/ROOT/osol-121 at install 199.93M static 2009-02-18 11:18 > rpool/ROOT/osol-121 at pos-update 17.34M static 2009-07-13 15:29 > rpool/ROOT/osol-121 at pos_image-update 9.64M static 2009-08-20 08:30 > rpool/ROOT/osol-121 at testBE 9.01M static 2009-08-14 10:54 > rpool/ROOT/osol-121 at to_bfu 13.10M static 2009-08-14 10:13 > > (I omitted columns Active and Mountpoint to fit the width.) > > Only osol-121 at pos_image-update was taken after the image-update (because > I did it manually). I recall taking the snapshots @pos-update, at testBE > and @to_bfu from BE osol-118. I also suspect that @install is the > snapshot taken by the installer at install time. However, they now show > up as a snapshot of osol-121. > > zfs list shows similar results: > > > [acruz at zurca]% zfs list -r -t all rpool/ROOT/osol-121 > NAME USED AVAIL REFER MOUNTPOINT > rpool/ROOT/osol-121 9.87G 731G 6.31G > /tmp/tmptcsYUZ > rpool/ROOT/osol-121 at install 200M - 3.54G - > rpool/ROOT/osol-121 at 2009-07-10-00:36:17 23.6M - 5.38G - > rpool/ROOT/osol-121 at 2009-07-13-22:09:26 13.6M - 5.38G - > rpool/ROOT/osol-121 at pos-update 17.3M - 5.39G - > rpool/ROOT/osol-121 at to_bfu 13.1M - 5.55G - > rpool/ROOT/osol-121 at testBE 9.01M - 5.55G - > rpool/ROOT/osol-121 at 2009-08-20-15:14:53 12.7M - 6.24G - > rpool/ROOT/osol-121 at pos_image-update 9.64M - 6.30G - > > I wonder if it is approprate to silently image-update the snapshot.
The contents of those snapshots haven't changed. Since the snapshot taken of osol-118 to create the osol-121 clone file system is younger than those pre-existing snapshots of osol-118, upon promotion of osol-121 (which happens when the osol-121 BE gets activated) osol-121 assumes ownership. > I > mean, I no longer have the snapshots I've taken from osol-118. Is this > supposed to work like this? As stated above, upon activation of a BE, we promote the BE's dataset(s) and so this snapshot ownership shifting happens. > I have not tried to promote any of these > snapshots to see what I get. You can't promote a snapshot. But if you create a BE from one of those pre-existing snapshots, e.g. # beadm create -e osol-121 at testBE testBE you actually get whatever contents were there when you cloned osol-118 to create @testBE. Does this answer your questions? thanks, -ethan > > Thanks, > > Antonello > _______________________________________________ > pkg-discuss mailing list > pkg-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
