Date: Tue, 2 Mar 2004 21:51:30 -0400 (AST) From: "Marc G. Fournier" <scrappy@hub.org> To: James Read <james@physicalsegment.com> Cc: stable@freebsd.org Subject: Re: Using read-only NULLFS leads to panic. gdb output included,easy toreproduce. Message-ID: <20040302215043.P23774@ganymede.hub.org> In-Reply-To: <00b901c400ab$f7e90e30$c000000a@jd2400> References: <20040302213936.216CB5F103@shellma.zin.lublin.pl> <00b901c400ab$f7e90e30$c000000a@jd2400>
next in thread | previous in thread | raw e-mail | index | archive | help
Just curious, but why use nullfs for this? On our boxes, I do a: mount_unionfs -b /usr/ports /mnt/usr/ports and haven't had any problems ... curious as to what nullfs gives over unionfs for ports ... On Tue, 2 Mar 2004, James Read wrote: > Quickly forgot to mention this occured on 4.9 RELEASE and also when I > upgraded to 4.9-STABLE #0: Sun Feb 15. > > Kernel is GENERIC with just IPFW + DUMMYNET added in. > > Regards, > > James. > > > > > ----- Original Message ----- > From: "James Read" <james@physicalsegment.com> > To: "Pawe=B3 Ma=B3achowski" <pawmal-posting@freebsd.lublin.pl> > Cc: <stable@freebsd.org> > Sent: Wednesday, March 03, 2004 10:48 PM > Subject: Re: Using read-only NULLFS leads to panic. gdb output included,e= asy > toreproduce. > > > > > find /usr/ports -type f -perm -u+s & > > > find /usr/ports -type f -perm -u+s & > > > ... > > > find /mnt/1 -type f -perm -u+s & > > > find /mnt/1 -type f -perm -u+s & > > > ... > > > find /mnt/2 -type f -perm -u+s & > > > find /mnt/2 -type f -perm -u+s & > > > ... > > > > > > (Machine C crashed after few minutes). > > > > > > All I can say is that I've had this happen to me before. 'Me too' > > > > The ports were mounted in exact the same way, but with rw instead of ro= =2E > > > > Also a few jails were running at the time, infact 3 were. All had > /usr/ports > > mount_null'ed inside there jail. > > > > After running find from the usual periodic scripts it brought the machi= ne > > down every time it ran that script. > > > > What I did to stop the box from panicing all the time at that one > particular > > place, was just to disable the script that does the 'find' / locate. Of= f > the > > top of my head I think it was /etc/periodic/weekly/310.locate. Once thi= s > was > > disabled (from inside and outside the jails), I didnt get any more pani= cs > > from 'find'. > > > > Granted this isnt a fix, but it did save me from panic hell every week. > > > > If there is a better way / another way to 'mount_null' /usr/ports (or a= ny > > other mount point for that matter) to other places in/on the filesystem= , > by > > using NFS or other such things, then speak up! I don't like getting pan= ics > > more then anyone else does ;> > > > > Regards, > > > > James. > > > > > > -- > > This message has been scanned for viruses and > > dangerous content by MailScanner, and is > > believed to be clean. > > Mailscanner thanks transtec Computers for their support. > > > > _______________________________________________ > > freebsd-stable@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.or= g" > > > > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > Mailscanner thanks transtec Computers for their support. > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040302215043.P23774>