Date: Wed, 3 Mar 2004 22:48:16 -0000 From: "James Read" <james@physicalsegment.com> To: =?iso-8859-1?Q?Pawe=B3_Ma=B3achowski?= <pawmal-posting@freebsd.lublin.pl> Cc: stable@freebsd.org Subject: Re: Using read-only NULLFS leads to panic. gdb output included, easy toreproduce. Message-ID: <00a501c40171$9e0f6dc0$c000000a@jd2400> References: <20040302213936.216CB5F103@shellma.zin.lublin.pl>
index | next in thread | previous in thread | raw e-mail
> 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. 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 machine 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. Off the top of my head I think it was /etc/periodic/weekly/310.locate. Once this was disabled (from inside and outside the jails), I didnt get any more panics 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 any 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 panics 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.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?00a501c40171$9e0f6dc0$c000000a>