From owner-freebsd-bugs@freebsd.org Thu Aug 25 20:41:42 2016 Return-Path: Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D3B3ABC4B0E for ; Thu, 25 Aug 2016 20:41:42 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BC3101A21 for ; Thu, 25 Aug 2016 20:41:42 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u7PKfgeh075370 for ; Thu, 25 Aug 2016 20:41:42 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 212139] r298900 introduced a fatal failure case for >2TB disk size reporting bugs Date: Thu, 25 Aug 2016 20:41:42 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-RC1 X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: tsoome@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Aug 2016 20:41:42 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D212139 --- Comment #3 from Toomas Soome --- I havent found yet good way, but there is something to think about. Essentially there are 2 cases: 1. unpartitioned raw disk with pool on it. We can get size from pool label = and provide as disk meta info down to biosdisk if we like to.=20 2. partitioned disk - almost all cases, except GPT backup label read, depen= d on partition boundaries, so essentially the read should honor the partition boundaries. It means the disk open, should again have means to pass the boundaries down= to biosdisk. So with exception of GPT backup label read and unpartitioned disk, all other reads should be checked not against disk size, but partition size... and th= is information is known. --=20 You are receiving this mail because: You are the assignee for the bug.=