From owner-freebsd-questions Sun Jun 2 19:12:58 2002 Delivered-To: freebsd-questions@freebsd.org Received: from diomedes.noc.ntua.gr (diomedes.noc.ntua.gr [147.102.222.220]) by hub.freebsd.org (Postfix) with ESMTP id 809F037B405 for ; Sun, 2 Jun 2002 19:12:53 -0700 (PDT) Received: from mail.ntua.gr (mail.ntua.gr [147.102.222.65]) by diomedes.noc.ntua.gr (8.11.6/8.11.6) with ESMTP id g532CnA01589 for ; Mon, 3 Jun 2002 05:12:49 +0300 (EEST) Received: from erwin.gr (ppp098.dialup.ntua.gr [147.102.223.98]) by mail.ntua.gr (Netscape Messaging Server 4.15) with ESMTP id GX3Y5C00.KQF for ; Mon, 3 Jun 2002 05:12:48 +0300 Content-Type: text/plain; charset="iso-8859-7" From: Aggelos Economopoulos Reply-To: aoiko@cc.ece.ntua.gr To: freebsd-questions@FreeBSD.ORG Subject: Disk access Date: Mon, 3 Jun 2002 05:10:45 +0300 X-Mailer: KMail [version 1.4] MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200206030510.45507.aoiko@cc.ece.ntua.gr> Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG After adding a 40G ide disk(ad3) on my system, I 'ld like to devote some=20 extra space to FreeBSD (there is already a linux installation on the 40G=20 disk). However, after booting my -stable installation on the first=20 disk(ad0), I get the error message "excessive recursion in search for=20 slices" by the kernel on any attempt to access ad3 (mount a partition,=20 fdisk -s /dev/ad3, or even a read() on ad3). Initially, I thought I had hit a bug in sys/kern/subr_diskmbr.c. Only, us= ing=20 a userspace partition viewer (which understands the partition setup on ad= 3=20 when run under linux) I get simillar errors (ie infinite loop in the=20 partition handling code), which seem to stem from a read() returning sect= or=20 0 (the mbr of ad3) at somepoint in following the extended partition table= s=20 chain (do *not* consider this a fact, I could be wrong). I therefore conclude that this is not a problem in the partition handling= =20 code and given my lack of familiarity with the kernel I cannot even guess= =20 at the cause. For what it's worth, ->d_secperunit in the in kernel=20 disklabel is the same as the number of sectors reported by the linux=20 kernel. I can only assume that this is some obvious misconfiguration on m= y=20 part. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message