i ever write email to you about the build-persistent -tape-rules.sh script, as i am not familiar with linux device technology , could you pls give me the full details on how to fix this issue?

Dec 19 '22 11:12 lqnewton

You will need to investigate 'udev' and how to create a udev rule set. (often default is located in /etc/udev/rules.d/)

The output of the 'build-persistent-tape-rules.sh' script and use the output to a config file.

e.g. $ ./build-persistent-tape-rules.sh ACTION=="add|change", KERNEL=="nst*", ENV{SUBSYSTEM}=="scsi_tape", ENV{ID_SERIAL_SHORT}=="50223344ab000100", SYMLINK+="tape/by-path/%E{ID_VENDOR}-%E{ID_MODEL}-%E{ID_SCSI_SERIAL}-nst", MODE="0666" ACTION=="add|change", KERNEL=="nst*", ENV{SUBSYSTEM}=="scsi_tape", ENV{ID_SERIAL_SHORT}=="50223344ab000200", SYMLINK+="tape/by-path/%E{ID_VENDOR}-%E{ID_MODEL}-%E{ID_SCSI_SERIAL}-nst", MODE="0666" ACTION=="add|change", KERNEL=="nst*", ENV{SUBSYSTEM}=="scsi_tape", ENV{ID_SERIAL_SHORT}=="50223344ab000300", SYMLINK+="tape/by-path/%E{ID_VENDOR}-%E{ID_MODEL}-%E{ID_SCSI_SERIAL}-nst", MODE="0666" ACTION=="add|change", KERNEL=="nst*", ENV{SUBSYSTEM}=="scsi_tape", ENV{ID_SERIAL_SHORT}=="50223344ab000400", SYMLINK+="tape/by-path/%E{ID_VENDOR}-%E{ID_MODEL}-%E{ID_SCSI_SERIAL}-nst", MODE="0666" ACTION=="add|change", KERNEL=="nst*", ENV{SUBSYSTEM}=="scsi_tape", ENV{ID_SERIAL_SHORT}=="50223344ab000900", SYMLINK+="tape/by-path/%E{ID_VENDOR}-%E{ID_MODEL}-%E{ID_SCSI_SERIAL}-nst", MODE="0666" ACTION=="add|change", KERNEL=="nst*", ENV{SUBSYSTEM}=="scsi_tape", ENV{ID_SERIAL_SHORT}=="50223344ab001000", SYMLINK+="tape/by-path/%E{ID_VENDOR}-%E{ID_MODEL}-%E{ID_SCSI_SERIAL}-nst", MODE="0666" ACTION=="add|change", KERNEL=="nst*", ENV{SUBSYSTEM}=="scsi_tape", ENV{ID_SERIAL_SHORT}=="50223344ab001100", SYMLINK+="tape/by-path/%E{ID_VENDOR}-%E{ID_MODEL}-%E{ID_SCSI_SERIAL}-nst", MODE="0666" ACTION=="add|change", KERNEL=="nst*", ENV{SUBSYSTEM}=="scsi_tape", ENV{ID_SERIAL_SHORT}=="50223344ab001200", SYMLINK+="tape/by-path/%E{ID_VENDOR}-%E{ID_MODEL}-%E{ID_SCSI_SERIAL}-nst", MODE="0666"

If the above looks suitable, use the output to build your udev rule. e.g. ./build-persistent-tape-rules.sh > /etc/udev/rules.d/70-persistent-tape.rules

Note: udev has been the standard user-space device management for Linux since about the Linux 2.2 kernel days. If you are uncomfortable with defining your own device rules, please refer to your linux administrator who will make short work of it. There are many udev references - e.g. https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/managing_storage_devices/assembly_overview-of-persistent-naming-attributes_managing-storage-devices

Dec 20 '22 04:12 markh794

Thank you mark, i will investigate your email and get back to you soon, thanks for your support.

From: Mark Harvey @.> Sent: Tuesday, December 20, 2022 4:45 AM To: markh794/mhvtl @.> Cc: lqnewton @.>; Author @.> Subject: Re: [markh794/mhvtl] compatible with nbu 10.1? (Issue #112)

You will need to investigate 'udev' and how to create a udev rule set. (often default is located in /etc/udev/rules.d/)

The output of the 'build-persistent-tape-rules.sh' script and use the output to a config file.

e.g. $ ./build-persistent-tape-rules.sh ACTION=="add|change", KERNEL=="nst*", ENV{SUBSYSTEM}=="scsi_tape", ENV{ID_SERIAL_SHORT}=="50223344ab000100", SYMLINK+="tape/by-path/%E{ID_VENDOR}-%E{ID_MODEL}-%E{ID_SCSI_SERIAL}-nst", MODE="0666" ACTION=="add|change", KERNEL=="nst*", ENV{SUBSYSTEM}=="scsi_tape", ENV{ID_SERIAL_SHORT}=="50223344ab000200", SYMLINK+="tape/by-path/%E{ID_VENDOR}-%E{ID_MODEL}-%E{ID_SCSI_SERIAL}-nst", MODE="0666" ACTION=="add|change", KERNEL=="nst*", ENV{SUBSYSTEM}=="scsi_tape", ENV{ID_SERIAL_SHORT}=="50223344ab000300", SYMLINK+="tape/by-path/%E{ID_VENDOR}-%E{ID_MODEL}-%E{ID_SCSI_SERIAL}-nst", MODE="0666" ACTION=="add|change", KERNEL=="nst*", ENV{SUBSYSTEM}=="scsi_tape", ENV{ID_SERIAL_SHORT}=="50223344ab000400", SYMLINK+="tape/by-path/%E{ID_VENDOR}-%E{ID_MODEL}-%E{ID_SCSI_SERIAL}-nst", MODE="0666" ACTION=="add|change", KERNEL=="nst*", ENV{SUBSYSTEM}=="scsi_tape", ENV{ID_SERIAL_SHORT}=="50223344ab000900", SYMLINK+="tape/by-path/%E{ID_VENDOR}-%E{ID_MODEL}-%E{ID_SCSI_SERIAL}-nst", MODE="0666" ACTION=="add|change", KERNEL=="nst*", ENV{SUBSYSTEM}=="scsi_tape", ENV{ID_SERIAL_SHORT}=="50223344ab001000", SYMLINK+="tape/by-path/%E{ID_VENDOR}-%E{ID_MODEL}-%E{ID_SCSI_SERIAL}-nst", MODE="0666" ACTION=="add|change", KERNEL=="nst*", ENV{SUBSYSTEM}=="scsi_tape", ENV{ID_SERIAL_SHORT}=="50223344ab001100", SYMLINK+="tape/by-path/%E{ID_VENDOR}-%E{ID_MODEL}-%E{ID_SCSI_SERIAL}-nst", MODE="0666" ACTION=="add|change", KERNEL=="nst*", ENV{SUBSYSTEM}=="scsi_tape", ENV{ID_SERIAL_SHORT}=="50223344ab001200", SYMLINK+="tape/by-path/%E{ID_VENDOR}-%E{ID_MODEL}-%E{ID_SCSI_SERIAL}-nst", MODE="0666"

If the above looks suitable, use the output to build your udev rule. e.g. ./build-persistent-tape-rules.sh > /etc/udev/rules.d/70-persistent-tape.rules

Note: udev has been the standard user-space device management for Linux since about the Linux 2.2 kernel days. If you are uncomfortable with defining your own device rules, please refer to your linux administrator who will make short work of it. There are many udev references - e.g. https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/managing_storage_devices/assembly_overview-of-persistent-naming-attributes_managing-storage-devices

— Reply to this email directly, view it on GitHubhttps://github.com/markh794/mhvtl/issues/112#issuecomment-1358834768, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A43LWTCJ5VCBRNBB4T5ASIDWOE2V7ANCNFSM6AAAAAATDHNXHI. You are receiving this because you authored the thread.Message ID: @.***>

Dec 20 '22 04:12 lqnewton

[cid:ebf0c6ad-9f27-4e7b-8fca-24a7805ec99d] this is the configured the changer by the nbu, i run the build-presistent-tape-rules.sh and the result is below, it seems there is no /dev/tape/by-path device created, am i wrong ? pls kindly advise. than

[cid:b00501ca-610f-4459-8407-b3ce846feeec]

From: newton luo @.> Sent: Tuesday, December 20, 2022 4:54 AM To: markh794/mhvtl @.> Subject: Re: [markh794/mhvtl] compatible with nbu 10.1? (Issue #112)

Thank you mark, i will investigate your email and get back to you soon, thanks for your support.

From: Mark Harvey @.> Sent: Tuesday, December 20, 2022 4:45 AM To: markh794/mhvtl @.> Cc: lqnewton @.>; Author @.> Subject: Re: [markh794/mhvtl] compatible with nbu 10.1? (Issue #112)

You will need to investigate 'udev' and how to create a udev rule set. (often default is located in /etc/udev/rules.d/)

The output of the 'build-persistent-tape-rules.sh' script and use the output to a config file.

e.g. $ ./build-persistent-tape-rules.sh ACTION=="add|change", KERNEL=="nst*", ENV{SUBSYSTEM}=="scsi_tape", ENV{ID_SERIAL_SHORT}=="50223344ab000100", SYMLINK+="tape/by-path/%E{ID_VENDOR}-%E{ID_MODEL}-%E{ID_SCSI_SERIAL}-nst", MODE="0666" ACTION=="add|change", KERNEL=="nst*", ENV{SUBSYSTEM}=="scsi_tape", ENV{ID_SERIAL_SHORT}=="50223344ab000200", SYMLINK+="tape/by-path/%E{ID_VENDOR}-%E{ID_MODEL}-%E{ID_SCSI_SERIAL}-nst", MODE="0666" ACTION=="add|change", KERNEL=="nst*", ENV{SUBSYSTEM}=="scsi_tape", ENV{ID_SERIAL_SHORT}=="50223344ab000300", SYMLINK+="tape/by-path/%E{ID_VENDOR}-%E{ID_MODEL}-%E{ID_SCSI_SERIAL}-nst", MODE="0666" ACTION=="add|change", KERNEL=="nst*", ENV{SUBSYSTEM}=="scsi_tape", ENV{ID_SERIAL_SHORT}=="50223344ab000400", SYMLINK+="tape/by-path/%E{ID_VENDOR}-%E{ID_MODEL}-%E{ID_SCSI_SERIAL}-nst", MODE="0666" ACTION=="add|change", KERNEL=="nst*", ENV{SUBSYSTEM}=="scsi_tape", ENV{ID_SERIAL_SHORT}=="50223344ab000900", SYMLINK+="tape/by-path/%E{ID_VENDOR}-%E{ID_MODEL}-%E{ID_SCSI_SERIAL}-nst", MODE="0666" ACTION=="add|change", KERNEL=="nst*", ENV{SUBSYSTEM}=="scsi_tape", ENV{ID_SERIAL_SHORT}=="50223344ab001000", SYMLINK+="tape/by-path/%E{ID_VENDOR}-%E{ID_MODEL}-%E{ID_SCSI_SERIAL}-nst", MODE="0666" ACTION=="add|change", KERNEL=="nst*", ENV{SUBSYSTEM}=="scsi_tape", ENV{ID_SERIAL_SHORT}=="50223344ab001100", SYMLINK+="tape/by-path/%E{ID_VENDOR}-%E{ID_MODEL}-%E{ID_SCSI_SERIAL}-nst", MODE="0666" ACTION=="add|change", KERNEL=="nst*", ENV{SUBSYSTEM}=="scsi_tape", ENV{ID_SERIAL_SHORT}=="50223344ab001200", SYMLINK+="tape/by-path/%E{ID_VENDOR}-%E{ID_MODEL}-%E{ID_SCSI_SERIAL}-nst", MODE="0666"

If the above looks suitable, use the output to build your udev rule. e.g. ./build-persistent-tape-rules.sh > /etc/udev/rules.d/70-persistent-tape.rules

Note: udev has been the standard user-space device management for Linux since about the Linux 2.2 kernel days. If you are uncomfortable with defining your own device rules, please refer to your linux administrator who will make short work of it. There are many udev references - e.g. https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/managing_storage_devices/assembly_overview-of-persistent-naming-attributes_managing-storage-devices

— Reply to this email directly, view it on GitHubhttps://github.com/markh794/mhvtl/issues/112#issuecomment-1358834768, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A43LWTCJ5VCBRNBB4T5ASIDWOE2V7ANCNFSM6AAAAAATDHNXHI. You are receiving this because you authored the thread.Message ID: @.***>

Dec 20 '22 05:12 lqnewton

mark: i just rebooted the server and fixed the issue, now NBU can configure the VTL and backup successfully. i just thought uedvadm reload or trigger can create the device, but actually the reboot is needed. thanks again. newton

From: newton luo @.> Sent: Tuesday, December 20, 2022 5:08 AM To: markh794/mhvtl @.> Subject: Re: [markh794/mhvtl] compatible with nbu 10.1? (Issue #112)