>>> The issue of cores taking up unnecessary space when a rpool/ROOT is >>> cloned is valid. But disabling savecore does not address it. Either the >>> user has to run this by hand everytime (bad!!) or once they enable this >>> functionality all subsequent clones now have the issue until they >>> disable it. >>> >>> >> >> I don't understand what you're arguing for here. >> >> > Comment #6 stated that the issue for disabling savecore was the space > taken up when BEs are cloned. When a user is asked to provide the core > how does that occur ? Does he run savecore directly or update dumpadm > config file. Either way once savecore is run, the contents are in > savecore dir (which for now is /var/crash) and future BE updates will > include the cores unless the user deletes them, i.e. the issue will > occur the first time coredumps taken and the cores are not removed.
Easy: you tell them the better way to configure things before running savecore until its default behavior is fixed. Something like the following 3 commands: zfs create -o mountpoint=/crashdump rpool/crashdump dumpadm -s /crashdump dumpadm -y Dave
