From owner-freebsd-current Sun Oct 29 21:54:57 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 821) id C7A6937B4C5; Sun, 29 Oct 2000 21:54:54 -0800 (PST) Date: Sun, 29 Oct 2000 21:54:54 -0800 From: "John W. De Boskey" To: Current List Cc: Adrian Chadd Subject: vinum & fsck wrappers strangeness Message-ID: <20001029215454.A60321@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I ran into an interesting gotcha with fsck and vinum... I have the following line in /etc/fstab: /dev/vinum/raid5 /pub ufs rw 2 2 and during an upgrade (old current to current), I commented the line out during the reboot process. After bringing the new system online, I executed: /sbin/fsck -y /dev/vinum/raid5 and received the following error: fsck: exec /usr/sbin/fsck_unused for /dev/vinum/raid5: No such file or directory Knowing that I've been able to fsck this volume in the past I checked for a vinum specific fsck binary. Nothing there. It then occurred to me it's a ufs volume, and I've always fsck'd it by mount point. I then uncommented the line in /etc/fstab and executed: /sbin/fsck -y /pub and it worked correctly. After the above (with the /etc/fstab line uncommented), I re-executed:o /sbin/fsck -y /dev/vinum/raid5 and it worked correctly. So, it appears that fsck is attempting to determine a file system type, tries to use /etc/fstab, and then falls back to a secondary scheme. In the secondary scheme, ufs is what we want, but vinum is what we're getting. If anyone has any information about this please let me know. I'll try to look into it tomorrow. Thanks, John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message