Date: Tue, 19 Feb 2008 01:14:08 +1100 From: Mark Andrews <Mark_Andrews@isc.org> To: "Kurt Buff" <kurt.buff@gmail.com> Cc: FreeBSD-bugs@freebsd.org, freebsd-stable@freebsd.org, freebsd-fs@freebsd.org, freebsd-security@freebsd.org, =?ISO-8859-1?Q?Dag-Erling_Sm=F8rgrav?= <des@des.no> Subject: Re: How to take down a system to the point of requiring a newfs with one line of C (userland) Message-ID: <200802181414.m1IEE8bd075081@drugs.dv.isc.org> In-Reply-To: Your message of "Mon, 18 Feb 2008 13:27:01 -0000." <a9f4a3860802180527k6fcfbdaeuf235540075b263b5@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> Patient: Doctor, it hurts when I do this! > > Doctor: Don't do that... Did you actually bother to read his report? While his example is used "/", if the report is correct then you just need to replace "/" with the path of any file system mount point that is world writable like say "/tmp". Do you have /tmp mounted like this? /dev/ad0s4e 507630 162050 304970 35% /tmp Have you tried using "/tmp" or some other suitable mount point before slinging off with the old Doctor joke? Even if it is only "/", having the system die and not be recoverable due to having a excessive number of files in "/" is a critical error. I'm sure you have *never* accidently copied a set of files to "/" in your life. Me, I know I've made that sort of mistake in the past, and as I'm not perfect, I'm sure I'll make that sort of mistake at some point in the future. I would however like the machine not to fallover when I do make that mistake. Now why don't you be constructive and verify whether the report is valid or not. I don't have a spare machine to test it on so I'm not going to attempt it. Mark -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: Mark_Andrews@isc.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200802181414.m1IEE8bd075081>