From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org
X-Spam-Level: 
X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=ham
	autolearn_force=no version=3.4.4
Received: (qmail 4535 invoked from network); 2 Oct 2022 20:06:27 -0000
Received: from 9front.inri.net (168.235.81.73)
  by inbox.vuxu.org with ESMTPUTF8; 2 Oct 2022 20:06:27 -0000
Received: from mimir.eigenstate.org ([206.124.132.107]) by 9front; Sun Oct  2 16:04:45 -0400 2022
Received: from stockyard (<unknown> [172.102.12.5])
	by mimir.eigenstate.org (OpenSMTPD) with ESMTPSA id 6326c3a5 (TLSv1.2:ECDHE-RSA-AES256-SHA:256:NO)
	for <9front@9front.org>;
	Sun, 2 Oct 2022 13:04:44 -0700 (PDT)
Message-ID: <A1DBB7B503ADD7D8261D0224D8B23553@eigenstate.org>
To: 9front@9front.org
Date: Sun, 02 Oct 2022 16:04:41 -0400
From: ori@eigenstate.org
In-Reply-To: <1993373294.3416290.1664736998610@comcenter.netcologne.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
List-ID: <9front.9front.org>
List-Help: <http://lists.9front.org>
X-Glyph: ➈
X-Bullshit: transactional storage-aware scripting CSS hosting 
Subject: Re: [9front] [patch] cdfs handle block sizes correctly
Reply-To: 9front@9front.org
Precedence: bulk

Quoth Arne Meyer <meyer.arne83@netcologne.de>:
> The old Readblock value is fine for data tracks, because 4 2048 byte blocks fit in the 8192 byte RPCMAX. But cdda blocks are 2352 bytes and 4 of those don't fit into 8192 bytes and stuff breaks. If I read the code correctly my change should set the number of blocks to 4 for data tracks and to 3 for everything else.

Ah, I misunderstood you -- I thought you were saying you had disks
where the blocksize was larger than RPCMAX (8k).

I'll take another look.