.
Something to look at next week.
--
Dmitry Filonov
Linux Administrator
SBGrid Core | Harvard Medical School
250 Longwood Ave, SGM-114
Boston, MA 02115
On Wed, Jul 3, 2019 at 12:18 PM Vladimir Melnik wrote:
> Thank you, it helped a little:
>
> $ for i in {1..5}; do { dd if=/dev/zero of=/mnt/g
> that pool.
> As long as I don't exhaust the pool's storage - I'm fine.
>
> You shouldb't expect that LVM will play the monitoring role here - either
> put some kind of monitoring, or create your own solution to monitor that
> fact.
>
> Best Regards,
> Strahil Nikolov
> On
Newly created snapshots will occupy some data and metadata space in LVM. So
the more snapshots you have, the more space will be utilized.
Yes, I understand that. The question is how to get snapshots error out
instead of breaking LVM completely. Is there any way to tell snapshots to
fail if after
is related but not that important. Is there a way to
schedule snapshot removal in cron? gluster snapshot delete requires
interactive confirmation and I don't see any flag to auto-confirm snapshot
removal.
Thank you,
Fil
--
Dmitry Filonov
Linux Administrator
SBGrid Core | Harvard Medical School
250
