Re: 3100/80: 4G disk limit?

Anders Magnusson <[email protected]> Sun, 26 Apr 2026 10:27:20 +0200
Newsgroups	gmane.os.netbsd.ports.vax
Message-ID	<[email protected]>
This is a multi-part message in MIME format.
--------------Bzvv9FYS0vDY5iQVW7L9g6hs
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Den 2026-04-26 kl. 06:09, skrev Mouse:
>> But in software we are talking about disk addressing in bytes, so
>> then 4G is an obvious point where it can break.
> Right.  I suspect there is something somewhere that's carelessly
> declared 32-bit instead of 64-bit.  If you aren't aware of any such
> issue in the 3100/80 hardware, I'll assume there isn't any and, once I
> get it running a fully-updated 1.6.2 in 4G of disk, start looking for a
> software issue.
There are very little vax-dependent stuff for SCSI, most are related to 
access the registers (via bus_space_*) or DMA (which goes either 
directly to memory or via a buffer, but neither has anything to do with 
the block on disk addressed).

Should be reasonable simple though to add code to just dump the commands 
sent to the disk when accessing and see if it matches the expectations :-)

-- R
--------------Bzvv9FYS0vDY5iQVW7L9g6hs
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit

<!DOCTYPE html>
<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <div class="moz-cite-prefix">Den 2026-04-26 kl. 06:09, skrev Mouse:<span
      style="white-space: pre-wrap">
</span><span style="white-space: pre-wrap">
</span></div>
    <blockquote type="cite"
      cite="mid:[email protected]">
      <blockquote type="cite">
        <pre wrap="" class="moz-quote-pre">But in software we are talking about disk addressing in bytes, so
then 4G is an obvious point where it can break.
</pre>
      </blockquote>
      <pre wrap="" class="moz-quote-pre">
Right.  I suspect there is something somewhere that's carelessly
declared 32-bit instead of 64-bit.  If you aren't aware of any such
issue in the 3100/80 hardware, I'll assume there isn't any and, once I
get it running a fully-updated 1.6.2 in 4G of disk, start looking for a
software issue.</pre>
    </blockquote>
    There are very little vax-dependent stuff for SCSI, most are related
    to access the registers (via bus_space_*) or DMA (which goes either
    directly to memory or via a buffer, but neither has anything to do
    with the block on disk addressed).<br>
    <br>
    Should be reasonable simple though to add code to just dump the
    commands sent to the disk when accessing and see if it matches the
    expectations :-)<br>
    <br>
    -- R
  </body>
</html>

--------------Bzvv9FYS0vDY5iQVW7L9g6hs--