Date: Fri, 23 Jan 2004 12:25:03 -0800 (PST) From: Greg Valcourt <gval@mts.net> To: freebsd-gnats-submit@FreeBSD.org Subject: misc/61800: inoinfo size too large, fsck segmentation faults Message-ID: <200401232025.i0NKP3eF062312@www.freebsd.org> Resent-Message-ID: <200401232030.i0NKU8jb057456@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 61800 >Category: misc >Synopsis: inoinfo size too large, fsck segmentation faults >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Jan 23 12:30:08 PST 2004 >Closed-Date: >Last-Modified: >Originator: Greg Valcourt >Release: FreeBSD 5.2 >Organization: Home >Environment: FreeBSD 5.2-RELEASE FreeBSD 5.2RELEASE #1: Thu Jan 22 22:27:27 CST 2004 root@:/usr/src/sys/i386/compile/MyKernel i386 >Description: I have a filesystem that mounts onto root via a directory called "/media". I noticed that I could not cd into it. Naturally, I did an ls -altr | grep "media": br-sr-Sr-- 8236 1931505524 1953653108 32, 0x65740020 May 23 1975 media Woh, that's wrong. So I umounted it. I ran fsck on the device: ** /dev/ad2s2c ** Last Mounted on /media ** Phase 1 - Check Blocks and Sizes cannot alloc 3267166364 bytes for inoinfo fsck: /dev/ad2s2c: Segmentation fault Now, mabey there is an error that fsck can't fix, but fsck should recognize this and give an appropriate error. The fact that it segmentation faults tells me that the program could not handle a particular situation. >How-To-Repeat: For me, I just run fsck again on that filesystem. For you, I don't know. You would have to encouter a similar corruption on your file system. I have the core file that it dumped. If you like it, email me and I will send you it. (It's over 6MB). >Fix: >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200401232025.i0NKP3eF062312>