No, i have done nothing except VTL service restart. This normally happens during 10TB DB2 or 14TB Oracle backup in the condition when I have about backup size or slightly more (Total minus Used) free space on VTL, I believe TSM somehow removes failed objects itself.
Numbers from my previous message (Total Size: 45056.00 GB / Used Size: 36170.66 GB) was during the 'offline drives', about 9TB free, TSM was trying to write 14TB Oracle database L0 backup. Now it is (Total Size: 45056.00 GB / Used Size: 30487.29 GB) Can't wait my TS3310 to be fixed so i can return to 'move everything older than one week to the physical tapes' scheme :) I have older crash dumps from May and nothing from June, can upload somewhere if you want. 1.5G 127.0.0.1-2019-05-12-04:05:54 1.2G 127.0.0.1-2019-05-22-23:01:33 8.9G 127.0.0.1-2019-05-31-20:06:04 On Sunday, June 16, 2019 at 11:46:13 PM UTC+3, quadstor wrote: > > Before update path is the problem with the out-of-space condition > fixed ? i.e either additional storage needs to be added or some of the > older tapes need to be expired+erased. > > For the crash on shutdown please check if there are any > vmcore-dmesg.txt files under /var/crash and send them across. > > > -- You received this message because you are subscribed to the Google Groups "QUADStor VTL" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/quadstor-vtl/9fa3a5f2-98ef-4442-9870-abb23bcfaf37%40googlegroups.com.
