Re: FreeBSD 6.1 - mount_nullfs broken?

2006-03-24 Thread Viren Patel
 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 SizeUsed   Avail Capacity  Mounted on
/dev/ad6s1a1.9G 80M1.7G 4%/
devfs  1.0K1.0K  0B   100%/dev
/dev/ad6s1g202G245M186G 0%/export
/dev/ad6s1f3.9G 18K3.6G 0%/home
/dev/ad6s1e7.7G1.9G5.2G27%/usr
/dev/ad6s1d7.7G 42M7.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 SizeUsed   Avail Capacity  Mounted on
/dev/ad6s1a1.9G 80M1.7G 4%/
devfs  1.0K1.0K  0B   100%/dev
/dev/ad6s1g202G245M186G 0%/export
/dev/ad6s1f3.9G 18K3.6G 0%/home
/dev/ad6s1e7.7G1.9G5.2G27%/usr
/dev/ad6s1d7.7G 42M7.1G 1%/var
devfs  1.0K1.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 WDC WD2500JS-55MHB0 02.01C03 at
ata3-master SATA300

It was definitely SATA150 under FreeBSD 6.0, even after
updates. So maybe a problem in the SATA300 driver?

Viren


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: FreeBSD 6.1 - mount_nullfs broken?

2006-03-24 Thread Kris Kennaway
On Fri, Mar 24, 2006 at 08:05:31AM -0600, Viren Patel wrote:

 # 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 WDC WD2500JS-55MHB0 02.01C03 at
 ata3-master SATA300
 
 It was definitely SATA150 under FreeBSD 6.0, even after
 updates. So maybe a problem in the SATA300 driver?

Unlikely.  It looks like you don't have kernel nullfs support enabled.

Kris


pgp83KXFePtfV.pgp
Description: PGP signature


Re: FreeBSD 6.1 - mount_nullfs broken?

2006-03-24 Thread Viren Patel
 On Fri, Mar 24, 2006 at 08:05:31AM -0600, Viren Patel
 wrote:

 # 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 WDC WD2500JS-55MHB0 02.01C03 at
 ata3-master SATA300

 It was definitely SATA150 under FreeBSD 6.0, even after
 updates. So maybe a problem in the SATA300 driver?

 Unlikely.  It looks like you don't have kernel nullfs
 support enabled.

 Kris


I am using the generic kernel. Looking through /etc there
is nothing regarding enabling nullfs. I also looked at
GENERIC kernel conf file without luck. How do I enable
nullfs?

Viren

Viren


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: FreeBSD 6.1 - mount_nullfs broken?

2006-03-24 Thread Kris Kennaway
On Fri, Mar 24, 2006 at 12:39:30PM -0600, Viren Patel wrote:
  On Fri, Mar 24, 2006 at 08:05:31AM -0600, Viren Patel
  wrote:
 
  # 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 WDC WD2500JS-55MHB0 02.01C03 at
  ata3-master SATA300
 
  It was definitely SATA150 under FreeBSD 6.0, even after
  updates. So maybe a problem in the SATA300 driver?
 
  Unlikely.  It looks like you don't have kernel nullfs
  support enabled.
 
  Kris
 
 
 I am using the generic kernel. Looking through /etc there
 is nothing regarding enabling nullfs. I also looked at
 GENERIC kernel conf file without luck. How do I enable
 nullfs?

Compile it into your kernel or load the module.  Read the handbook for
more help.

Kris


pgp2eFPowUIHy.pgp
Description: PGP signature


Re: FreeBSD 6.1 - mount_nullfs broken?

2006-03-24 Thread Lowell Gilbert
Kris Kennaway [EMAIL PROTECTED] writes:

 On Fri, Mar 24, 2006 at 12:39:30PM -0600, Viren Patel wrote:
   On Fri, Mar 24, 2006 at 08:05:31AM -0600, Viren Patel
   wrote:
  
   # 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 WDC WD2500JS-55MHB0 02.01C03 at
   ata3-master SATA300
  
   It was definitely SATA150 under FreeBSD 6.0, even after
   updates. So maybe a problem in the SATA300 driver?
  
   Unlikely.  It looks like you don't have kernel nullfs
   support enabled.
  
   Kris
  
  
  I am using the generic kernel. Looking through /etc there
  is nothing regarding enabling nullfs. I also looked at
  GENERIC kernel conf file without luck. How do I enable
  nullfs?
 
 Compile it into your kernel or load the module.  Read the handbook for
 more help.

Or you could come at it the other way; figure out how you did it when
you were running 6.0.  The procedure has not changed.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: FreeBSD 6.1 - mount_nullfs broken?

2006-03-24 Thread Viren Patel

 Compile it into your kernel or load the module.  Read the
 handbook for
 more help.

 Kris


That did it! The nullfs module was not being loaded into
the kernel. I added it to loader.conf.local and it works
now. This is definitely a change from 6.0 to
6.1-prerelease.

Viren

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: FreeBSD 6.1 - mount_nullfs broken?

2006-03-24 Thread Viren Patel

 Or you could come at it the other way; figure out how you
 did it when
 you were running 6.0.  The procedure has not changed.


I didn't change a thing, even in 6.0. The nullfs just
worked. I did the usual upgrade process to get from 6.0 to
6.1:

   1. change cvs tag from RELENG_6_0 to RELENG_6
   2. update sources
   3. make buildworld
   4. make buildkernel KERNCONF=GENERIC
   5. make installkernel KERNCONF=GENERIC
   6. reboot into single-user mode
   7. mergemaster -p
   8. make installworld
   9. mergemaster
   10. reboot

Viren


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: FreeBSD 6.1 - mount_nullfs broken?

2006-03-24 Thread Kris Kennaway
On Fri, Mar 24, 2006 at 01:24:35PM -0600, Viren Patel wrote:
 
  Compile it into your kernel or load the module.  Read the
  handbook for
  more help.
 
  Kris
 
 
 That did it! The nullfs module was not being loaded into
 the kernel. I added it to loader.conf.local and it works
 now. This is definitely a change from 6.0 to
 6.1-prerelease.

I don't think so.  Modules are all installed by default.

Kris


pgpW5ifWfq8IB.pgp
Description: PGP signature


Re: FreeBSD 6.1 - mount_nullfs broken?

2006-03-24 Thread Viren Patel
 On Fri, Mar 24, 2006 at 01:24:35PM -0600, Viren Patel
 wrote:
 
  Compile it into your kernel or load the module.  Read
 the
  handbook for
  more help.
 
  Kris
 

 That did it! The nullfs module was not being loaded into
 the kernel. I added it to loader.conf.local and it works
 now. This is definitely a change from 6.0 to
 6.1-prerelease.

 I don't think so.  Modules are all installed by default.

 Kris


Then something is broken. The module file is present in
/boot/kernel. However it does *not* get loaded unless I
put it in loader.conf.local. As mentioned previously, I am
using the generic kernel. I followed the standard upgrade
procedure when going from 6.0 to 6.1.

Viren

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: FreeBSD 6.1 - mount_nullfs broken?

2006-03-24 Thread Kris Kennaway
On Fri, Mar 24, 2006 at 04:52:40PM -0600, Viren Patel wrote:
  On Fri, Mar 24, 2006 at 01:24:35PM -0600, Viren Patel
  wrote:
  
   Compile it into your kernel or load the module.  Read
  the
   handbook for
   more help.
  
   Kris
  
 
  That did it! The nullfs module was not being loaded into
  the kernel. I added it to loader.conf.local and it works
  now. This is definitely a change from 6.0 to
  6.1-prerelease.
 
  I don't think so.  Modules are all installed by default.
 
  Kris
 
 
 Then something is broken. The module file is present in
 /boot/kernel. However it does *not* get loaded unless I
 put it in loader.conf.local. As mentioned previously, I am
 using the generic kernel. I followed the standard upgrade
 procedure when going from 6.0 to 6.1.

What is logged on the console when you try to mount_nullfs before
loading the nullfs.ko module (it should be loaded automatically)?

Kris


pgplhFmaDnMSk.pgp
Description: PGP signature


Re: FreeBSD 6.1 - mount_nullfs broken?

2006-03-23 Thread Kris Kennaway
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


pgpJWcyErcUxt.pgp
Description: PGP signature