Closed vguilleaume closed 5 months ago
I'm not sure your first log is produced by which step.
To Reproduce The steps to reproduce are the following:
- mklts can format the tapes
- ltfs mount works as expected
- start to copy files till a moment (i can't determine for now)
- dismount the tape
- try to mount again, and then get this mounting status.
- can't copy anymore file in the tape even if there are still space (around 6TB is used on a total of 17TB).
But it is cerated by step5, LTFS detected a permanent write error on step4 and make it read only at step4. So the tape was mounted as R/O at step5.
The first log says the tape was mounted as R/O like below. The log produced at step3 and step4 is required if you want to investigate the reason of the permanent write error. LTFS shall generate drive dump files because of the permanent write error. You need to contact to IBM for more investigation.
8cca LTFS11333I A cartridge with write-perm error is detected on DP. Seek the newest index (IP: Gen = 641, VCR = 1338) (DP: Gen = 640, VCR = 1304) (VCR = 1338).
8cca LTFS17286I VCR value is matched between IP-MAM and VCR (1338).
8cca LTFS17287I Making R/O mount from the location (a, 8).
Hi @piste-jp-ibm thanks for this quick answer. You are right the provided LTFS mount is the step5, and your answer is already helping.
I will try to find back the previous umount for this tape, and try to provide the log.
In the meantime, in the tape library logs, there are tape alert message mentioning a tape capacity problem:
49 Diminished native capacity 31h The media is either partitioned or shortened and is not configured to use full native capacity. If using partitioning, this is normal. If not, then determine why there is a partitioned cartridge present and unpartition the cartridge. 249 (Informational) No
I suspect that the tape(s) for some unknown reason are full at one stage (before raising its total capacity), and then there is no space anymore to write the index. Or something like this. Do you believe this could be a root cause?
I come back to you with the info. Thanks in advanced,
I suspect that the tape(s) for some unknown reason are full at one stage (before raising its total capacity), and then there is no space anymore to write the index. Or something like this. Do you believe this could be a root cause?
I don't think so. The TA reported from library might not be related into this problem.
Tape device is basically append device, so a permanent write error happens at a position the drive cannot write any following data. (Of course, we can issue another write at the error position and might have good response luckily and continue to write. But LTFS never does such kind of handling, because such kind of write error might cause bigger problem at read side later!)
In this case, LTFS might have a permanent write error in the step3 or step4. And LTFS make the tape R/O because of the permanent write error. This is the design of LTFS and LTFS works fine I believe.
Additional failure analysis is required by the IBM engineers to find out the root cause of the permanent write error.
I found back the previous LTFS log, and we have found i believe interesting information:
Apr 18 01:55:13 nodeum ltfs[2833710]: 2b3d34 LTFS11338I Syncing index of NO_BARCODE 11C97790B5.
Apr 18 01:55:13 nodeum ltfs[2833710]: 2b3d34 LTFS17068I Syncing index of NO_BARCODE (Reason: Periodic Sync) 11C97790B5.
Apr 18 01:55:13 nodeum ltfs[2833710]: 2b3d34 LTFS17235I Writing index of NO_BARCODE to b (Reason: Periodic Sync, 46548 files) 11C97790B5.
Apr 18 01:55:20 nodeum ltfs[2833710]: 2b3d34 LTFS17236I Wrote index of NO_BARCODE (Gen = 630, Part = b, Pos = 17648089, 11C97790B5).
Apr 18 01:55:20 nodeum ltfs[2833710]: 2b3d34 LTFS11337I Update index-dirty flag (0) - NO_BARCODE (0x0x55fcebd36760).
Apr 18 01:55:20 nodeum ltfs[2833710]: 2b3d34 LTFS17070I Synced index of NO_BARCODE (0) 11C97790B5.
Apr 18 01:55:39 nodeum ltfs[2833710]: 2b3d33 LTFS11337I Update index-dirty flag (1) - NO_BARCODE (0x0x55fcebd36760).
Apr 18 02:00:20 nodeum ltfs[2833710]: 2b3d34 LTFS11338I Syncing index of NO_BARCODE 11C97790B5.
Apr 18 02:00:20 nodeum ltfs[2833710]: 2b3d34 LTFS17068I Syncing index of NO_BARCODE (Reason: Periodic Sync) 11C97790B5.
Apr 18 02:00:20 nodeum ltfs[2833710]: 2b3d34 LTFS17235I Writing index of NO_BARCODE to b (Reason: Periodic Sync, 46552 files) 11C97790B5.
Apr 18 02:00:27 nodeum ltfs[2833710]: 2b3d34 LTFS17236I Wrote index of NO_BARCODE (Gen = 631, Part = b, Pos = 17680536, 11C97790B5).
Apr 18 02:00:27 nodeum ltfs[2833710]: 2b3d34 LTFS11337I Update index-dirty flag (0) - NO_BARCODE (0x0x55fcebd36760).
Apr 18 02:00:27 nodeum ltfs[2833710]: 2b3d34 LTFS17070I Synced index of NO_BARCODE (0) 11C97790B5.
Apr 18 02:00:54 nodeum ltfs[2833710]: 2b3d33 LTFS11337I Update index-dirty flag (1) - NO_BARCODE (0x0x55fcebd36760).
Apr 18 02:05:27 nodeum ltfs[2833710]: 2b3d34 LTFS11338I Syncing index of NO_BARCODE 11C97790B5.
Apr 18 02:05:27 nodeum ltfs[2833710]: 2b3d34 LTFS17068I Syncing index of NO_BARCODE (Reason: Periodic Sync) 11C97790B5.
Apr 18 02:05:27 nodeum ltfs[2833710]: 2b3d34 LTFS17235I Writing index of NO_BARCODE to b (Reason: Periodic Sync, 46556 files) 11C97790B5.
Apr 18 02:05:43 nodeum ltfs[2833710]: 2b3d34 LTFS17236I Wrote index of NO_BARCODE (Gen = 632, Part = b, Pos = 17707012, 11C97790B5).
Apr 18 02:05:43 nodeum ltfs[2833710]: 2b3d34 LTFS11337I Update index-dirty flag (0) - NO_BARCODE (0x0x55fcebd36760).
Apr 18 02:05:43 nodeum ltfs[2833710]: 2b3d34 LTFS17070I Synced index of NO_BARCODE (0) 11C97790B5.
Apr 18 02:05:57 nodeum ltfs[2833710]: 2b3d33 LTFS11337I Update index-dirty flag (1) - NO_BARCODE (0x0x55fcebd36760).
Apr 18 02:10:43 nodeum ltfs[2833710]: 2b3d34 LTFS11338I Syncing index of NO_BARCODE 11C97790B5.
Apr 18 02:10:43 nodeum ltfs[2833710]: 2b3d34 LTFS17068I Syncing index of NO_BARCODE (Reason: Periodic Sync) 11C97790B5.
Apr 18 02:10:43 nodeum ltfs[2833710]: 2b3d34 LTFS17235I Writing index of NO_BARCODE to b (Reason: Periodic Sync, 46556 files) 11C97790B5.
Apr 18 02:10:50 nodeum ltfs[2833710]: 2b3d34 LTFS17236I Wrote index of NO_BARCODE (Gen = 633, Part = b, Pos = 17739914, 11C97790B5).
Apr 18 02:10:50 nodeum ltfs[2833710]: 2b3d34 LTFS11337I Update index-dirty flag (0) - NO_BARCODE (0x0x55fcebd36760).
Apr 18 02:10:50 nodeum ltfs[2833710]: 2b3d34 LTFS17070I Synced index of NO_BARCODE (0) 11C97790B5.
Apr 18 02:11:15 nodeum ltfs[2833710]: 2b3d33 LTFS11337I Update index-dirty flag (1) - NO_BARCODE (0x0x55fcebd36760).
Apr 18 02:15:50 nodeum ltfs[2833710]: 2b3d34 LTFS11338I Syncing index of NO_BARCODE 11C97790B5.
Apr 18 02:15:50 nodeum ltfs[2833710]: 2b3d34 LTFS17068I Syncing index of NO_BARCODE (Reason: Periodic Sync) 11C97790B5.
Apr 18 02:15:50 nodeum ltfs[2833710]: 2b3d34 LTFS17235I Writing index of NO_BARCODE to b (Reason: Periodic Sync, 46560 files) 11C97790B5.
Apr 18 02:15:58 nodeum ltfs[2833710]: 2b3d34 LTFS17236I Wrote index of NO_BARCODE (Gen = 634, Part = b, Pos = 17770198, 11C97790B5).
Apr 18 02:15:58 nodeum ltfs[2833710]: 2b3d34 LTFS11337I Update index-dirty flag (0) - NO_BARCODE (0x0x55fcebd36760).
Apr 18 02:15:58 nodeum ltfs[2833710]: 2b3d34 LTFS17070I Synced index of NO_BARCODE (0) 11C97790B5.
Apr 18 02:16:17 nodeum ltfs[2833710]: 2b3d33 LTFS11337I Update index-dirty flag (1) - NO_BARCODE (0x0x55fcebd36760).
Apr 18 02:20:58 nodeum ltfs[2833710]: 2b3d34 LTFS11338I Syncing index of NO_BARCODE 11C97790B5.
Apr 18 02:20:58 nodeum ltfs[2833710]: 2b3d34 LTFS17068I Syncing index of NO_BARCODE (Reason: Periodic Sync) 11C97790B5.
Apr 18 02:20:58 nodeum ltfs[2833710]: 2b3d34 LTFS17235I Writing index of NO_BARCODE to b (Reason: Periodic Sync, 46564 files) 11C97790B5.
Apr 18 02:21:05 nodeum ltfs[2833710]: 2b3d34 LTFS17236I Wrote index of NO_BARCODE (Gen = 635, Part = b, Pos = 17801577, 11C97790B5).
Apr 18 02:21:05 nodeum ltfs[2833710]: 2b3d34 LTFS11337I Update index-dirty flag (0) - NO_BARCODE (0x0x55fcebd36760).
Apr 18 02:21:05 nodeum ltfs[2833710]: 2b3d34 LTFS17070I Synced index of NO_BARCODE (0) 11C97790B5.
Apr 18 02:21:23 nodeum ltfs[2833710]: 2b3d33 LTFS11337I Update index-dirty flag (1) - NO_BARCODE (0x0x55fcebd36760).
Apr 18 02:26:05 nodeum ltfs[2833710]: 2b3d34 LTFS11338I Syncing index of NO_BARCODE 11C97790B5.
Apr 18 02:26:05 nodeum ltfs[2833710]: 2b3d34 LTFS17068I Syncing index of NO_BARCODE (Reason: Periodic Sync) 11C97790B5.
Apr 18 02:26:05 nodeum ltfs[2833710]: 2b3d34 LTFS17235I Writing index of NO_BARCODE to b (Reason: Periodic Sync, 46568 files) 11C97790B5.
Apr 18 02:26:12 nodeum ltfs[2833710]: 2b3d34 LTFS17236I Wrote index of NO_BARCODE (Gen = 636, Part = b, Pos = 17834481, 11C97790B5).
Apr 18 02:26:12 nodeum ltfs[2833710]: 2b3d34 LTFS11337I Update index-dirty flag (0) - NO_BARCODE (0x0x55fcebd36760).
Apr 18 02:26:12 nodeum ltfs[2833710]: 2b3d34 LTFS17070I Synced index of NO_BARCODE (0) 11C97790B5.
Apr 18 02:27:09 nodeum ltfs[2833710]: 2b3d33 LTFS11337I Update index-dirty flag (1) - NO_BARCODE (0x0x55fcebd36760).
Apr 18 02:31:12 nodeum ltfs[2833710]: 2b3d34 LTFS11338I Syncing index of NO_BARCODE 11C97790B5.
Apr 18 02:31:12 nodeum ltfs[2833710]: 2b3d34 LTFS17068I Syncing index of NO_BARCODE (Reason: Periodic Sync) 11C97790B5.
Apr 18 02:31:12 nodeum ltfs[2833710]: 2b3d34 LTFS17235I Writing index of NO_BARCODE to b (Reason: Periodic Sync, 46572 files) 11C97790B5.
Apr 18 02:31:21 nodeum ltfs[2833710]: 2b3d34 LTFS17236I Wrote index of NO_BARCODE (Gen = 637, Part = b, Pos = 17861869, 11C97790B5).
Apr 18 02:31:21 nodeum ltfs[2833710]: 2b3d34 LTFS11337I Update index-dirty flag (0) - NO_BARCODE (0x0x55fcebd36760).
Apr 18 02:31:21 nodeum ltfs[2833710]: 2b3d34 LTFS17070I Synced index of NO_BARCODE (0) 11C97790B5.
Apr 18 02:31:31 nodeum ltfs[2833710]: 2b3d33 LTFS11337I Update index-dirty flag (1) - NO_BARCODE (0x0x55fcebd36760).
...
Apr 18 02:36:21 nodeum ltfs[2833710]: 2b3d34 LTFS11338I Syncing index of NO_BARCODE 11C97790B5.
Apr 18 02:36:21 nodeum ltfs[2833710]: 2b3d34 LTFS17068I Syncing index of NO_BARCODE (Reason: Periodic Sync) 11C97790B5.
Apr 18 02:36:21 nodeum ltfs[2833710]: 2b3d34 LTFS17235I Writing index of NO_BARCODE to b (Reason: Periodic Sync, 46576 files) 11C97790B5.
...
Apr 18 02:36:28 nodeum ltfs[2833710]: 2b3d34 LTFS17236I Wrote index of NO_BARCODE (Gen = 638, Part = b, Pos = 17895940, 11C97790B5).
Apr 18 02:36:28 nodeum ltfs[2833710]: 2b3d34 LTFS11337I Update index-dirty flag (0) - NO_BARCODE (0x0x55fcebd36760).
Apr 18 02:36:28 nodeum ltfs[2833710]: 2b3d34 LTFS17070I Synced index of NO_BARCODE (0) 11C97790B5.
...
Apr 18 02:36:56 nodeum ltfs[2833710]: 2b3d33 LTFS11337I Update index-dirty flag (1) - NO_BARCODE (0x0x55fcebd36760).
...
Apr 18 02:41:28 nodeum ltfs[2833710]: 2b3d34 LTFS11338I Syncing index of NO_BARCODE 11C97790B5.
Apr 18 02:41:28 nodeum ltfs[2833710]: 2b3d34 LTFS17068I Syncing index of NO_BARCODE (Reason: Periodic Sync) 11C97790B5.
Apr 18 02:41:28 nodeum ltfs[2833710]: 2b3d34 LTFS17235I Writing index of NO_BARCODE to b (Reason: Periodic Sync, 46576 files) 11C97790B5.
...
Apr 18 02:41:37 nodeum ltfs[2833710]: 2b3d34 LTFS17236I Wrote index of NO_BARCODE (Gen = 639, Part = b, Pos = 17926814, 11C97790B5).
Apr 18 02:41:37 nodeum ltfs[2833710]: 2b3d34 LTFS11337I Update index-dirty flag (0) - NO_BARCODE (0x0x55fcebd36760).
Apr 18 02:41:37 nodeum ltfs[2833710]: 2b3d34 LTFS17070I Synced index of NO_BARCODE (0) 11C97790B5.
...
Apr 18 02:42:04 nodeum ltfs[2833710]: 2b3d33 LTFS11337I Update index-dirty flag (1) - NO_BARCODE (0x0x55fcebd36760).
...
Apr 18 02:46:37 nodeum ltfs[2833710]: 2b3d34 LTFS11338I Syncing index of NO_BARCODE 11C97790B5.
Apr 18 02:46:37 nodeum ltfs[2833710]: 2b3d34 LTFS17068I Syncing index of NO_BARCODE (Reason: Periodic Sync) 11C97790B5.
Apr 18 02:46:37 nodeum ltfs[2833710]: 2b3d34 LTFS17235I Writing index of NO_BARCODE to b (Reason: Periodic Sync, 46580 files) 11C97790B5.
Apr 18 02:46:47 nodeum ltfs[2833710]: 2b3d34 LTFS17236I Wrote index of NO_BARCODE (Gen = 640, Part = b, Pos = 17958111, 11C97790B5).
Apr 18 02:46:47 nodeum ltfs[2833710]: 2b3d34 LTFS11337I Update index-dirty flag (0) - NO_BARCODE (0x0x55fcebd36760).
Apr 18 02:46:47 nodeum ltfs[2833710]: 2b3d34 LTFS17070I Synced index of NO_BARCODE (0) 11C97790B5.
...
Apr 18 02:47:13 nodeum ltfs[2833710]: 2b3d33 LTFS11337I Update index-dirty flag (1) - NO_BARCODE (0x0x55fcebd36760).
...
Apr 18 02:58:33 nodeum ltfs[2833710]: 2b3d33 LTFS30205I WRITE (0x0a) returns -20301.
Apr 18 02:58:33 nodeum ltfs[2833710]: 2b3d33 LTFS30263I WRITE returns Cartridge Fault (-20301) /dev/sg1.
Apr 18 02:58:33 nodeum ltfs[2833710]: 2b3d33 LTFS30261I Taking drive dump in buffer.
Apr 18 02:58:33 nodeum ltfs[2833710]: 2b3d33 LTFS30253I Saving drive dump to /tmp/ltfs_11C97790B5_2024_0418_025833.dmp.
Apr 18 02:58:53 nodeum ltfs[2833710]: 2b3d33 LTFS30262I Forcing drive dump.
Apr 18 02:58:54 nodeum ltfs[2833710]: 2b3d33 LTFS30253I Saving drive dump to /tmp/ltfs_11C97790B5_2024_0418_025833_f.dmp.
Apr 18 02:59:07 nodeum ltfs[2833710]: 2b3d33 LTFS12045E Cannot write block: backend call failed (-20301). Dropping to read-only mode.
Apr 18 02:59:07 nodeum ltfs[2833710]: 2b3d33 LTFS11072E Cannot write blocks: failed to write to the medium (-20301).
Apr 18 02:59:07 nodeum ltfs[2833710]: 2b3d33 LTFS11077E Cannot write: failed to write blocks to the medium (-20301).
Apr 18 02:59:07 nodeum ltfs[2833710]: 2b3d33 LTFS13014W Data partition writer: failed to write data to the tape (-20301).
Apr 18 02:59:07 nodeum ltfs[2833710]: 2b3d33 LTFS13024I Clean up extents and append index at index partition (-20301).
Apr 18 02:59:09 nodeum ltfs[2833710]: 2b3d33 LTFS13025I Get error position (17974866, 524288).
Apr 18 02:59:09 nodeum ltfs[2833710]: 2b3d33 LTFS11334I Remove extent : 200412_092027_Scanner_1.rxp (17971127, 1960837120).
Apr 18 02:59:09 nodeum ltfs[2833710]: 2b3d33 LTFS11343I Try to write an index on the IP on NO_BARCODE because of a permanent write error on the DP..
Apr 18 03:01:10 nodeum ltfs[2833710]: 2b3d33 LTFS17235I Writing index of NO_BARCODE to a (Reason: Write perm, 46584 files) 11C97790B5.
Apr 18 03:01:19 nodeum ltfs[2833710]: 2b3d33 LTFS17236I Wrote index of NO_BARCODE (Gen = 641, Part = a, Pos = 8, 11C97790B5).
Apr 18 03:01:19 nodeum ltfs[2833710]: 2b3d33 LTFS11337I Update index-dirty flag (0) - NO_BARCODE (0x0x55fcebd36760).
Apr 18 03:01:19 nodeum ltfs[2833710]: 2b3d34 LTFS11030I Failed to sync volume (-1126). Stop the periodic sync thread.
Apr 18 03:01:19 nodeum ltfs[2833710]: 2b3d2e LTFS17265I Skip writing the index because of the volume is not dirty and current self pointer points IP.
Apr 18 03:01:19 nodeum ltfs[2833710]: 2b3d2e LTFS11034I Volume unmounted successfully.
Apr 18 03:01:19 nodeum ltfs[2833710]: 2b3d2e LTFS30252I Logical block protection is disabled.
And specially this extract:
Apr 18 02:47:13 nodeum ltfs[2833710]: 2b3d33 LTFS11337I Update index-dirty flag (1) - NO_BARCODE (0x0x55fcebd36760).
...
Apr 18 02:58:33 nodeum ltfs[2833710]: 2b3d33 LTFS30205I WRITE (0x0a) returns -20301.
Apr 18 02:58:33 nodeum ltfs[2833710]: 2b3d33 LTFS30263I WRITE returns Cartridge Fault (-20301) /dev/sg1.
Apr 18 02:58:33 nodeum ltfs[2833710]: 2b3d33 LTFS30261I Taking drive dump in buffer.
Apr 18 02:58:33 nodeum ltfs[2833710]: 2b3d33 LTFS30253I Saving drive dump to /tmp/ltfs_11C97790B5_2024_0418_025833.dmp.
Apr 18 02:58:53 nodeum ltfs[2833710]: 2b3d33 LTFS30262I Forcing drive dump.
Apr 18 02:58:54 nodeum ltfs[2833710]: 2b3d33 LTFS30253I Saving drive dump to /tmp/ltfs_11C97790B5_2024_0418_025833_f.dmp.
Apr 18 02:59:07 nodeum ltfs[2833710]: 2b3d33 LTFS12045E Cannot write block: backend call failed (-20301). Dropping to read-only mode.
Apr 18 02:59:07 nodeum ltfs[2833710]: 2b3d33 LTFS11072E Cannot write blocks: failed to write to the medium (-20301).
Apr 18 02:59:07 nodeum ltfs[2833710]: 2b3d33 LTFS11077E Cannot write: failed to write blocks to the medium (-20301).
Apr 18 02:59:07 nodeum ltfs[2833710]: 2b3d33 LTFS13014W Data partition writer: failed to write data to the tape (-20301).
Apr 18 02:59:07 nodeum ltfs[2833710]: 2b3d33 LTFS13024I Clean up extents and append index at index partition (-20301).
Apr 18 02:59:09 nodeum ltfs[2833710]: 2b3d33 LTFS13025I Get error position (17974866, 524288).
Apr 18 02:59:09 nodeum ltfs[2833710]: 2b3d33 LTFS11334I Remove extent : 200412_092027_Scanner_1.rxp (17971127, 1960837120).
Apr 18 02:59:09 nodeum ltfs[2833710]: 2b3d33 LTFS11343I Try to write an index on the IP on NO_BARCODE because of a permanent write error on the DP..
Apr 18 03:01:10 nodeum ltfs[2833710]: 2b3d33 LTFS17235I Writing index of NO_BARCODE to a (Reason: Write perm, 46584 files) 11C97790B5.
Apr 18 03:01:19 nodeum ltfs[2833710]: 2b3d33 LTFS17236I Wrote index of NO_BARCODE (Gen = 641, Part = a, Pos = 8, 11C97790B5).
Apr 18 03:01:19 nodeum ltfs[2833710]: 2b3d33 LTFS11337I Update index-dirty flag (0) - NO_BARCODE (0x0x55fcebd36760).
Apr 18 03:01:19 nodeum ltfs[2833710]: 2b3d34 LTFS11030I Failed to sync volume (-1126). Stop the periodic sync thread.
Apr 18 03:01:19 nodeum ltfs[2833710]: 2b3d2e LTFS17265I Skip writing the index because of the volume is not dirty and current self pointer points IP.
Apr 18 03:01:19 nodeum ltfs[2833710]: 2b3d2e LTFS11034I Volume unmounted successfully.
Apr 18 03:01:19 nodeum ltfs[2833710]: 2b3d2e LTFS30252I Logical block protection is disabled.
If you have some explanation of what happened , this could help to troubleshoot the problem. Thanks again,
It looks everything works as expected.
Write error happens with -20301
, it is 03/0900 Read Perm or Write perm
(see ltfs_error.h
).
Apr 18 02:58:33 nodeum ltfs[2833710]: 2b3d33 LTFS30205I WRITE (0x0a) returns -20301.
Apr 18 02:58:33 nodeum ltfs[2833710]: 2b3d33 LTFS30263I WRITE returns Cartridge Fault (-20301) /dev/sg1.
Take drive dumps.
Apr 18 02:58:33 nodeum ltfs[2833710]: 2b3d33 LTFS30261I Taking drive dump in buffer.
Apr 18 02:58:33 nodeum ltfs[2833710]: 2b3d33 LTFS30253I Saving drive dump to /tmp/ltfs_11C97790B5_2024_0418_025833.dmp.
Apr 18 02:58:53 nodeum ltfs[2833710]: 2b3d33 LTFS30262I Forcing drive dump.
Apr 18 02:58:54 nodeum ltfs[2833710]: 2b3d33 LTFS30253I Saving drive dump to /tmp/ltfs_11C97790B5_2024_0418_025833_f.dmp.
Change the mounting file system to read-only mode (No more write is not permitted)
Apr 18 02:59:07 nodeum ltfs[2833710]: 2b3d33 LTFS12045E Cannot write block: backend call failed (-20301). Dropping to read-only mode.
Apr 18 02:59:07 nodeum ltfs[2833710]: 2b3d33 LTFS11072E Cannot write blocks: failed to write to the medium (-20301).
Apr 18 02:59:07 nodeum ltfs[2833710]: 2b3d33 LTFS11077E Cannot write: failed to write blocks to the medium (-20301).
Apr 18 02:59:07 nodeum ltfs[2833710]: 2b3d33 LTFS13014W Data partition writer: failed to write data to the tape (-20301).
Make the tape read-only LTFS volume because the reason of the write error in the step1 is medium reason. (SCSI sense 03/0900
shows it is medium reason, more4 specific SK 03/
means medium reason. Please refer the SCSI spec of drive...)
Apr 18 02:59:07 nodeum ltfs[2833710]: 2b3d33 LTFS13024I Clean up extents and append index at index partition (-20301).
Apr 18 02:59:09 nodeum ltfs[2833710]: 2b3d33 LTFS13025I Get error position (17974866, 524288).
Apr 18 02:59:09 nodeum ltfs[2833710]: 2b3d33 LTFS11334I Remove extent : 200412_092027_Scanner_1.rxp (17971127, 1960837120).
Apr 18 02:59:09 nodeum ltfs[2833710]: 2b3d33 LTFS11343I Try to write an index on the IP on NO_BARCODE because of a permanent write error on the DP..
Apr 18 03:01:10 nodeum ltfs[2833710]: 2b3d33 LTFS17235I Writing index of NO_BARCODE to a (Reason: Write perm, 46584 files) 11C97790B5.
Apr 18 03:01:19 nodeum ltfs[2833710]: 2b3d33 LTFS17236I Wrote index of NO_BARCODE (Gen = 641, Part = a, Pos = 8, 11C97790B5).
If you want to know more detail of the permanent write error, please contact to IBM support with the dump files, /tmp/ltfs_11C97790B5_2024_0418_025833.dmp
and ltfs_11C97790B5_2024_0418_025833_f.dmp
.
LTFS doesn't know the symptom of write error and it is not a scope of LTFS. LTFS just takes actions against error code (SCSI sense key). In this case, action is
a medium reason write error
on the non-volatile memory on tape. (LTFS check the non-volatile memory at the next mount and mount this tape as R/O.)Close this because there is no activity long time.
Please feel free to reopen if something new is found.
Describe the bug I'm facing to a case where the LTFS mount results with read-only mount. This happened multiple time with different LTO9. I never get this before, and i try to understand what's happened.
To Reproduce The steps to reproduce are the following:
Trace Log Here is the log of a tape where i have the problem:
Another one without the problem (yet), i just did a LTFS format:
Desktop (please complete the following information): LTFS 2.4.4.1 is used