Re: Restarting exports disturbs clients

2013-05-03 Thread Graham Allan
On Fri, May 03, 2013 at 02:08:26PM +0200, Bernt Hansson wrote:
 2013-05-03 12:49, Daniel Feenberg skrev:
 
 When we change the exportfs file on our FreeBSD 9.1 fileserver:
 
kill -HUP `cat /var/run/mountd.pid`
 
 That seems a bit harsh, try /etc/rc.d/nfsd restart or
 /etc/nfsserver restart.

Sending SIGHUP to mountd has always been the right way to have it reread
the exports file - should really be much less disruptive than restarting
the service.

Graham
-- 
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


8.3 hanging on boot, Dell 1950 with mfi and qlogic HBA

2013-03-25 Thread Graham Allan
I feel sure I'm missing something pretty obvious here but I can't figure 
out what.


I have a Dell 1950 which I just installed 8.3 (amd64) onto. It has an 
internal OS drive on mfi (Dell PERC) and a qlogic QLE2462 for external 
SAN connection.


Problem is, the machine hangs on boot if the SAN fiber is connected. It 
boots up fine if disconnected, then I can reconnect the fiber and mount 
the SAN drives.


When booting with fiber connected, it hangs after these messages:
kbd3 at ukbd1
kbd3: ukbd1, generic (0), config:0x0, flags:0x3d
ums1: EP2 Interrupt on usbus1
ums1: 3 buttons and [XYZ] coordinates ID=0
uhub5: 4 ports with 4 removable, self powered

(which just look like normal device probes) then if I reboot with the 
fiber disconnected, the next lines are:


Trying to mount root from ufs:/dev/mfid0s1a
start_init: trying /sbin/init

Verbose boot doesn't seem to give any additional clues.

I feel convinced it's failing to find or mount the root filesystem - 
I've certainly seen this in the past where an add-in HBA like this 
usurps the internal OS drive, fixable by hard-wiring the bus order in 
/boot/device.hints. That's what I thought of first here, but mfi doesn't 
use CAM (I guess), and the OS drive /dev/mfid0 isn't changing its device 
name...


and of course I'm not getting any root mount errors either.

Is there part of the boot mechanism I'm missing?

Graham
--
-
Graham Allan
School of Physics and Astronomy - University of Minnesota
-
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org