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.

On Mon, Jun 17, 2019 at 2:11 AM Sergey Kamyanov <[email protected]> wrote:
>
> Happened again :)
>
> update drive/path works but drives are immediately going offline/polling 
> again.
>
> Total Size: 45056.00 GB
> Used Size: 36170.66 GB
> VCartridge Usage: 104433.43 GB
> Deduped Size: 12290.02 GB
> Uncompressed Size: 1254.45 GB
> Compressed Size: 34155.99 GB
> Compression Hits: 90888.96 GB
> Dedupe Ratio: 2.949
>
> messages on the vtl server:
>
> Jun 16 05:58:05 srv-vtl-00 vtmdaemon: WARN: node_usr_notify:700 
> bdev_alloc_for_pgdata:5317 Cannot find a free bint for tape VT0161L4 size 512
> Jun 16 05:58:05 srv-vtl-00 vtmdaemon: WARN: node_usr_notify:700 
> tape_alloc_blocks:2796 pgdata alloc for entry size 512 failed
> Jun 16 05:58:05 srv-vtl-00 kernel: WARN: bdev_alloc_for_pgdata:5317 Cannot 
> find a free bint for tape VT0161L4 size 512
> Jun 16 05:58:05 srv-vtl-00 kernel: WARN: tape_alloc_blocks:2796 pgdata alloc 
> for entry size 512 failed
> Jun 16 05:58:05 srv-vtl-00 kernel: WARN: bdev_alloc_for_pgdata:5317 Cannot 
> find a free bint for tape VT0172L4 size 512
> Jun 16 05:58:05 srv-vtl-00 kernel: WARN: tape_alloc_blocks:2796 pgdata alloc 
> for entry size 512 failed
> Jun 16 05:58:05 srv-vtl-00 vtmdaemon: WARN: node_usr_notify:700 
> bdev_alloc_for_pgdata:5317 Cannot find a free bint for tape VT0172L4 size 512
> Jun 16 05:58:05 srv-vtl-00 vtmdaemon: WARN: node_usr_notify:700 
> tape_alloc_blocks:2796 pgdata alloc for entry size 512 failed
> Jun 16 05:58:05 srv-vtl-00 vtmdaemon: WARN: node_usr_notify:700 
> bdev_alloc_for_pgdata:5317 Cannot find a free bint for tape VT0173L4 size 512
> Jun 16 05:58:05 srv-vtl-00 kernel: WARN: bdev_alloc_for_pgdata:5317 Cannot 
> find a free bint for tape VT0173L4 size 512
> Jun 16 05:58:05 srv-vtl-00 kernel: WARN: tape_alloc_blocks:2796 pgdata alloc 
> for entry size 512 failed
>
> Updating 3.0.33 to 3.0.35 now. Will send before and after logs to the support 
> address.
>
> Forgot to mention that the server began to crash reboot during service stop 
> since 3.0.33 update.
>
>
>
>
> On Wednesday, June 5, 2019 at 12:38:54 PM UTC+3, quadstor wrote:
>>
>> On Wed, Jun 5, 2019 at 2:15 PM Sergey Kamyanov <[email protected]> wrote:
>> >
>> > I'm running 3.0.33 now, will schedule the update window soon.
>> > The master disk is not so fast for random io (12x 4T NLSAS on Netapp).
>> > I see about 2k iops and 100% disk load on dd tables load.
>>
>> This is addressed in 3.0.35.  Please generate the diagnostic logs
>> (HTML UI -> System Page -> Run Diagnostics) before and after the
>> upgrade and send them across to [email protected]
>>
>> >
>> > As for the behavior - all drives just go offline in TSM and the only way 
>> > to bring them back online is quadstor service restart.
>>
>> The drives should not have gone offline at the client/server OS level.
>> i.e the /dev/IBMtape[n] or similar devices should be accessible
>> The next time this occurs does a  manual "UPDATE PATH" work ?
>>
>> For example
>> update path QUADSTOR1 drive0 srctype=server desttype=drive
>> library=lib0 device=/dev/IBMtape0 online=yes
>>
>> The command is similar to the define path command but with the
>> trailing "online=yes"
>> Follow up with a "q path" command to see if all paths are online
>>
> --
> 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/3844308b-2902-4fe4-b77a-fb33847c5a34%40googlegroups.com.

-- 
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/CAPEgkt4VYrT_FbX1FM3iLH4hZD91QW9K8T0FcJHeFOJF%3Def1JA%40mail.gmail.com.

Reply via email to