-
Notifications
You must be signed in to change notification settings - Fork 66
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Data file write failure for LTO-6 drives #99
Comments
Hello Peter, Can I enquire as to the underlying file system on /opt/mhvtl - is it ext3,4,xfs etc and if the underlying block device is 'local' or nfs/cifs etc. |
Hi, Mark. It is ext4. We put our mhvtl tape volume files under the old default directory of /opt/vtl. The disk where the files reside is local. We used a opt-vtl.mount file under the /etc/systemd/system directory to mount the disk to the /opt/vtl directory. It has these contents:
Does that answer your questions? Thank you, |
It seems like there might be issues with the latest mhvtl version and LTO-6 drives on RHEL8. I noticed that with mhvtl 1.6.4 the problems with LTO-6 drives don't occur on RHEL8. When I updated my system that has mhvtl 1.7.0 to use LTO-5 drives the problems did not occur. The only difference between what I was testing with before with mhvtl 1.7.0 was that the etc/generate_device_conf.in file had:
instead of:
Could there be something miscoded with the use of add_ibm_ultrium_6_drive vs add_ibm_ultrium_5_drive in the latest mhvtl version? (I used the zip file from the latest code as of June 5, 2022.) Thank you, |
Note that the system with issues is a ppc64le system with RHEL 8.5. But I also seemed to have similar issues when the etc/generate_device_conf.in file had add_ibm_ultrium_6_drive calls on a RHEL 8.5 x86_64 system. |
The read/write path is exactly the same for all 'emulations'. |
Could this account for the issues I am seeing with the drives created with add_ibm_ultrium_6_drive vs add_ibm_ultrium_5_drive? |
No - LTO-4+ emulations all support the same PR & SPIN/SPOUT code. Is it possible the application expects the -TD5 / -TD6 to behave slightly differently - and my 'emulation' is incomplete ? |
There might be an issue with our hardware that is causing us issues. The mhvtl volumes seem to work fine for a while, but eventually we may run into the issues noted here on some of our machines. However, this can happen for both LTO-5 and LTO-6 drives. |
I am noticing a lot of errors like this from mhvtl:
This causes an end of media error for our application and then we lock the drive so it cannot be written to afterward.
What would cause the "Data file write failure"? I looked at the code in vtlcart.c and found this:
The pwrite call is returning an unexpected value. This issue seems to occur on multiple different machines. I am using the mhvtl code from the commit on Mar 13th of this year.
The errors are occurring on RHEL8 x86_64 machines.
Thank you,
Peter
The text was updated successfully, but these errors were encountered: