Date: Sun, 08 Aug 1999 16:02:57 -0700 From: Mike Smith <mike@smith.net.au> To: "Morgan Davis" <mdavis@cts.com> Cc: "Tom" <tom@uniserve.com>, "David Malone" <dwmalone@maths.tcd.ie>, freebsd-stable@freebsd.org Subject: Re: Removing files in /lost+found causes panic Message-ID: <199908082302.QAA13667@dingo.cdrom.com> In-Reply-To: Your message of "Sun, 08 Aug 1999 15:22:24 PDT." <NABBLJGKKPMOKACIENPPAEOHCHAA.mdavis@cts.com>
next in thread | previous in thread | raw e-mail | index | archive | help
It would, of course, have been _really_nice_ if you actually bothered to give us some details on these files before you nuked them... > Tom, thanks for the suggestion to use clri and fsck. This did the trick! > > David, I have Seagate SCSI drives, so it's not the IDE problem you > described. > > My conclusion is that there is something not right in the kernel if trying > to remove a file causes it to panic. Remove should be a lot like what clri > and fsck does -- dellocate the inode, update free block map, tie up any > loose ends so that that filesystem is stable. Apparently, rm is trying to > do more -- perhaps stat the file in some way that is getting tripped up on > odd characteristics of the file entry (since it looks like a block or > character device, etc.). Since these odd files are not supposed to show up > at all, I presume the kernel is assuming that such a situation never occurs > and doesn't have to plan for that contingency. > > --Morgan > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199908082302.QAA13667>