From owner-freebsd-questions@FreeBSD.ORG Fri Mar 24 14:05:33 2006 Return-Path: X-Original-To: questions@freebsd.org Delivered-To: freebsd-questions@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 27E6616A423 for ; Fri, 24 Mar 2006 14:05:33 +0000 (UTC) (envelope-from virenp@mail.utexas.edu) Received: from smtp.cm.utexas.edu (smtp.cm.utexas.edu [146.6.135.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0D31A43D46 for ; Fri, 24 Mar 2006 14:05:31 +0000 (GMT) (envelope-from virenp@mail.utexas.edu) Received: from mail.cm.utexas.edu (smtp.cm.utexas.edu [146.6.135.3]) by smtp.cm.utexas.edu (Postfix) with ESMTP id 835EB6D417; Fri, 24 Mar 2006 08:05:31 -0600 (CST) Received: from 66.25.138.31 (SquirrelMail authenticated user vpatel) by mail.cm.utexas.edu with HTTP; Fri, 24 Mar 2006 08:05:31 -0600 (CST) Message-ID: <1052.66.25.138.31.1143209131.squirrel@mail.cm.utexas.edu> In-Reply-To: <20060323230935.GA90169@xor.obsecurity.org> References: <58674.146.6.135.6.1143153068.squirrel@mail.cm.utexas.edu> <20060323230935.GA90169@xor.obsecurity.org> Date: Fri, 24 Mar 2006 08:05:31 -0600 (CST) From: "Viren Patel" To: "Kris Kennaway" User-Agent: SquirrelMail/1.4.5 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Cc: questions@freebsd.org Subject: Re: FreeBSD 6.1 - mount_nullfs broken? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: virenp@mail.utexas.edu List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Mar 2006 14:05:33 -0000 > On Thu, Mar 23, 2006 at 04:31:08PM -0600, Viren Patel > wrote: >> Hello. I just upgraded a FreeBSD 6.0 system to >> 6.1-prerelease and now mount_nullfs seems to be broken. >> I >> get the error "mount_nullfs: Operation not supported by >> device". Nothing has changed in the hardware or the >> config >> files. Here is the output dmesg: > > It's definitely working. > > Show us the exact command you're running. > > Kris > Thanks for your reply. Basically I run the ezjail.sh script and I've shown the disk layout before and after. I also tried running mount_nullfs directly and got the same results. # df -h Filesystem Size Used Avail Capacity Mounted on /dev/ad6s1a 1.9G 80M 1.7G 4% / devfs 1.0K 1.0K 0B 100% /dev /dev/ad6s1g 202G 245M 186G 0% /export /dev/ad6s1f 3.9G 18K 3.6G 0% /home /dev/ad6s1e 7.7G 1.9G 5.2G 27% /usr /dev/ad6s1d 7.7G 42M 7.1G 1% /var # /usr/local/etc/rc.d/ezjail.sh start ezjailConfiguring jails: set_hostname_allow=YES. Starting jails:mount_nullfs: Operation not supported by device . # df -h Filesystem Size Used Avail Capacity Mounted on /dev/ad6s1a 1.9G 80M 1.7G 4% / devfs 1.0K 1.0K 0B 100% /dev /dev/ad6s1g 202G 245M 186G 0% /export /dev/ad6s1f 3.9G 18K 3.6G 0% /home /dev/ad6s1e 7.7G 1.9G 5.2G 27% /usr /dev/ad6s1d 7.7G 42M 7.1G 1% /var devfs 1.0K 1.0K 0B 100% /export/jails/testjail/dev # umount /export/jails/testjail/dev # mount_nullfs -o ro /export/jails/basejail /export/jails/testjail/basejail mount_nullfs: Operation not supported by device After looking at the dmesg output more closely one discrepancy I found was the second last line: ad6: 238475MB at ata3-master SATA300 It was definitely SATA150 under FreeBSD 6.0, even after updates. So maybe a problem in the SATA300 driver? Viren