From owner-freebsd-current Tue Oct 20 11:39:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA17598 for freebsd-current-outgoing; Tue, 20 Oct 1998 11:39:36 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from skraldespand.demos.su (skraldespand.demos.su [194.87.5.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA17591 for ; Tue, 20 Oct 1998 11:39:33 -0700 (PDT) (envelope-from mishania@skraldespand.demos.su) Received: by skraldespand.demos.su id WAA01373; (8.8.8/D) Tue, 20 Oct 1998 22:39:04 +0400 (MSD) Message-ID: <19981020223904.26635@demos.su> Date: Tue, 20 Oct 1998 22:39:04 +0400 From: "Mikhail A. Sokolov" To: current@FreeBSD.ORG Subject: ufd_dirbad and mp_lock() and happy reboots etc. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Organization: Demos Company, Ltd., Moscow, Russian Federation. X-Point-of-View: Gravity is myth, - the earth sucks. X-Useless-Header: Look ma! It's a # sign! Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, lately I was stuck to ufs_baddir on /, right as it in ufs_lookup.c ("mangled entry"). It took me some 2 days of constant hitting reset button to realize it since the machine would either not reboot and just "freeze" or reboot without giving a dump or something. Once I was lucky to see that the inode is mangled, since it finally got frozen when it was trying to sync disks, reboot and failed with mp_lock() on CPU0. I wonder why would it be so shy when it a) has broken FS, b) can't reboot properly, c) can't reboot when has SMP in use? The machine is ELF 3.0R, kernel aout, but it doesn't make any difference since it was the same during those days it was 3.0-current as of 24.04/21.05-1998 during last week or two. I also broke the reset button on the machine since the attitude to it got a bit less gentle as it was, but that's another issue. Thanks in advance, -- -mishania, who's gonna make a slogan 'a localized culprit of reboot is 99.999% of fix' his fetish. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message