<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Write filemarks in MSA Storage</title>
    <link>https://community.hpe.com/t5/msa-storage/write-filemarks/m-p/747997#M2881</link>
    <description>I'm using Netbackup 6.0 with a LTO Ultrium 2 dirve for backup sometimes I see failures due to write filemarks failure. In the fibre channel trace that I've captured, I noticed that the host sends out the CDB 0x102000000100 (a reserved bit is set) instead of the usual 0x100000000100 when it fails. I'm not sure whether this is an issue with the tape driver (HP LTO Ultrium2 driver 1.0.2.0) or the HBA driver. Does anyone know?</description>
    <pubDate>Fri, 02 Feb 2007 14:05:13 GMT</pubDate>
    <dc:creator>Steven Tan</dc:creator>
    <dc:date>2007-02-02T14:05:13Z</dc:date>
    <item>
      <title>Write filemarks</title>
      <link>https://community.hpe.com/t5/msa-storage/write-filemarks/m-p/747997#M2881</link>
      <description>I'm using Netbackup 6.0 with a LTO Ultrium 2 dirve for backup sometimes I see failures due to write filemarks failure. In the fibre channel trace that I've captured, I noticed that the host sends out the CDB 0x102000000100 (a reserved bit is set) instead of the usual 0x100000000100 when it fails. I'm not sure whether this is an issue with the tape driver (HP LTO Ultrium2 driver 1.0.2.0) or the HBA driver. Does anyone know?</description>
      <pubDate>Fri, 02 Feb 2007 14:05:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/msa-storage/write-filemarks/m-p/747997#M2881</guid>
      <dc:creator>Steven Tan</dc:creator>
      <dc:date>2007-02-02T14:05:13Z</dc:date>
    </item>
  </channel>
</rss>

