From owner-freebsd-fs@FreeBSD.ORG Sun Feb 27 16:37:25 2005 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4CFA816A4CE for ; Sun, 27 Feb 2005 16:37:25 +0000 (GMT) Received: from hosea.tallye.com (joel.tallye.com [216.99.199.78]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2DBED43D64 for ; Sun, 27 Feb 2005 16:37:01 +0000 (GMT) (envelope-from lorenl@alzatex.com) Received: from hosea.tallye.com (hosea.tallye.com [127.0.0.1]) by hosea.tallye.com (8.12.8/8.12.10) with ESMTP id j1RGabqS003092 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 27 Feb 2005 08:36:38 -0800 Received: (from sttng359@localhost) by hosea.tallye.com (8.12.8/8.12.10/Submit) id j1RGaaTC003090; Sun, 27 Feb 2005 08:36:36 -0800 X-Authentication-Warning: hosea.tallye.com: sttng359 set sender to lorenl@alzatex.com using -f Date: Sun, 27 Feb 2005 08:36:36 -0800 From: "Loren M. Lang" To: Thomas Foster Message-ID: <20050227163636.GA1672@alzatex.com> References: <00f201c515fa$8caef250$4300a8c0@home.lan> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <00f201c515fa$8caef250$4300a8c0@home.lan> User-Agent: Mutt/1.4.1i X-GPG-Key: ftp://ftp.tallye.com/pub/lorenl_pubkey.asc X-GPG-Fingerprint: B3B9 D669 69C9 09EC 1BCD 835A FAF3 7A46 E4A3 280C cc: freebsd-fs@freebsd.org Subject: Re: UFS2 Recovery Questions X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Feb 2005 16:37:25 -0000 On Fri, Feb 18, 2005 at 12:43:45PM -0800, Thomas Foster wrote: > Please excuse me if this is not the correct forum in which to ask this question and please try to bear with me. I was hoping to understand a few things about attempting to retrieve information from a drive on my FreeBSD 5.3 system. > > I recently was rearranging my web server content and accidentally removed a symbolic link recursively > > root@host # rm -rf music Are you sure the command wasn't rm -fr music/? The final / can make a big differnece with symlinks. It forces the system to look it up as a directory first, and without that, I think it would only remove the symlink. Also, -r should never be needed for a symlink, even if it point to a directory. > > The music link pointed to a directory that existed on a spserate drive mounted as /storage > > music -> /storage/Music/Mp3s > > > Now the questions is.. are the files even recoverable? Is this a lost cause? Any additional information required, any comments or suggestions, anything would be helpful. I thank you for your time in the matter. > > Thomas Foster > http://www.section6.net > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" > -- I sense much NT in you. NT leads to Bluescreen. Bluescreen leads to downtime. Downtime leads to suffering. NT is the path to the darkside. Powerful Unix is. Public Key: ftp://ftp.tallye.com/pub/lorenl_pubkey.asc Fingerprint: B3B9 D669 69C9 09EC 1BCD 835A FAF3 7A46 E4A3 280C From owner-freebsd-fs@FreeBSD.ORG Mon Feb 28 23:51:25 2005 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D8F2516A4D6; Mon, 28 Feb 2005 23:51:23 +0000 (GMT) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id BE3AD43D46; Mon, 28 Feb 2005 23:51:23 +0000 (GMT) (envelope-from bright@elvis.mu.org) Received: by elvis.mu.org (Postfix, from userid 1192) id B95C15C98E; Mon, 28 Feb 2005 15:51:23 -0800 (PST) Date: Mon, 28 Feb 2005 15:51:23 -0800 From: Alfred Perlstein To: fs@freebsd.org Message-ID: <20050228235123.GC81082@elvis.mu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i cc: jeffr@freebsd.org cc: Xin LI Subject: ffs softdeps fix request X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Feb 2005 23:51:26 -0000 There's an artifact of ffs softupdates that causes issues if a crash occurs while deleting or creating files. Basically, one can wind up with a directory that is empty, but the link count is artificially high. Then you can have a directory that is empty, but not removeable. It would be somewhat trivial to add some code to check the directory's contents when a VOP_RMDIR would have failed because of the link count check. But then my head went all explody when trying to figure out how that would impact the background fsck in progress. Any ideas? -- - Alfred Perlstein - Research Engineering Development Inc. - email: bright@mu.org cell: 408-480-4684 From owner-freebsd-fs@FreeBSD.ORG Tue Mar 1 00:04:19 2005 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2053316A4CE; Tue, 1 Mar 2005 00:04:19 +0000 (GMT) Received: from mail.chesapeake.net (chesapeake.net [208.142.252.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8EF5F43D2F; Tue, 1 Mar 2005 00:04:18 +0000 (GMT) (envelope-from jroberson@chesapeake.net) Received: from mail.chesapeake.net (localhost [127.0.0.1]) by mail.chesapeake.net (8.12.10/8.12.10) with ESMTP id j2100MVp099889; Mon, 28 Feb 2005 19:00:22 -0500 (EST) (envelope-from jroberson@chesapeake.net) Received: from localhost (jroberson@localhost)j2100LTj099885; Mon, 28 Feb 2005 19:00:22 -0500 (EST) (envelope-from jroberson@chesapeake.net) X-Authentication-Warning: mail.chesapeake.net: jroberson owned process doing -bs Date: Mon, 28 Feb 2005 19:00:21 -0500 (EST) From: Jeff Roberson To: Alfred Perlstein In-Reply-To: <20050228235123.GC81082@elvis.mu.org> Message-ID: <20050228185955.V50530@mail.chesapeake.net> References: <20050228235123.GC81082@elvis.mu.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: mckusick@mckusick.com cc: jeffr@freebsd.org cc: Xin LI cc: fs@freebsd.org Subject: Re: ffs softdeps fix request X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Mar 2005 00:04:19 -0000 On Mon, 28 Feb 2005, Alfred Perlstein wrote: > There's an artifact of ffs softupdates that causes issues if a crash > occurs while deleting or creating files. > You should really ask Kirk about this sort of thing. > Basically, one can wind up with a directory that is empty, but the > link count is artificially high. Then you can have a directory > that is empty, but not removeable. It would be somewhat trivial > to add some code to check the directory's contents when a VOP_RMDIR > would have failed because of the link count check. > > But then my head went all explody when trying to figure out how > that would impact the background fsck in progress. > > Any ideas? > > -- > - Alfred Perlstein > - Research Engineering Development Inc. > - email: bright@mu.org cell: 408-480-4684 > From owner-freebsd-fs@FreeBSD.ORG Tue Mar 1 23:45:29 2005 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 87C7216A4CE for ; Tue, 1 Mar 2005 23:45:29 +0000 (GMT) Received: from tower.berklix.org (bsd.bsn.com [194.221.32.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1789343D2D for ; Tue, 1 Mar 2005 23:45:28 +0000 (GMT) (envelope-from jhs@berklix.org) Received: from js.berklix.net (p549A68E8.dip.t-dialin.net [84.154.104.232]) (authenticated bits=0) by tower.berklix.org (8.12.9p2/8.12.9) with ESMTP id j21NjNYS047315; Wed, 2 Mar 2005 00:45:24 +0100 (CET) (envelope-from jhs@tower.berklix.net) Received: from fire.jhs.private (fire.jhs.private [192.168.91.41]) by js.berklix.net (8.12.11/8.12.11) with ESMTP id j21NkdH4002671; Wed, 2 Mar 2005 00:46:50 +0100 (CET) (envelope-from jhs@tower.berklix.net) Received: from fire.jhs.private (localhost [127.0.0.1]) by fire.jhs.private (8.13.1/8.13.1) with ESMTP id j21NkdQQ002368; Wed, 2 Mar 2005 00:46:39 +0100 (CET) (envelope-from jhs@fire.jhs.private) Received: (from jhs@localhost) by fire.jhs.private (8.13.1/8.13.1/Submit) id j21NkdrU002367; Wed, 2 Mar 2005 00:46:39 +0100 (CET) (envelope-from jhs) Date: Wed, 2 Mar 2005 00:46:39 +0100 (CET) Message-Id: <200503012346.j21NkdrU002367@fire.jhs.private> To: freebsd-fs@freebsd.org From: "Julian Stacey" Organization: http://berklix.com/~jhs/ Fcc: sent-mail User-agent: EXMH http://beedub.com/exmh/ on FreeBSD http://freebsd.org Subject: A bad lost+found causes fsck of FFS to repeatefly fail. X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Mar 2005 23:45:29 -0000 Folk on freebsd-fs, I had a FFS error that fsck couldnt fix, & I've seen similar before: If content of lost+found/ is itself damaged, fsck fails, it seems. Then one has to manually [copy elsewhere] & rm -rf lost+found then re-fsck. Should the above be added to man fsck, or content below submitted as a send-pr ? Or do readers here include FFS / FSCK maintainers ? Log & environ follow: uname -a FreeBSD fire.jhs.private 5.3-RELEASE FreeBSD 5.3-RELEASE #0: Sat Feb 26 21:47:28 CET 2005 jhs@fire.jhs.private:/usr1/src/sys/amd64/compile/FIRE64.small amd64 fsck: # (from later to give a feel of size of machine) Filesystem Size Used Avail Capacity Mounted on /dev/ad0s2a 260M 61M 178M 25% / /dev/ad0s2d 260M 35M 204M 15% /var /dev/ad0s2e 260M 80k 239M 0% /tmp /dev/ad0s2f 1.2G 876M 266M 77% /usr /dev/ad0s1a 260M 62M 177M 26% /a /dev/ad0s1d 260M 50M 189M 21% /a/var /dev/ad0s1f 1.2G 899M 248M 78% /a/usr /dev/ad0s3d 53G 42G 7.0G 86% /usr1 fstab: (for the problematic 40 Gig partition) /dev/ad0s3d /mnt ufs rw 2 2 fsck -y /dev/ad0s3d ** /dev/ad0s3d ** Last Mounted on /usr1 ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames MISSING '.' I=5393708 OWNER=root MODE=40755 SIZE=512 MTIME=Mar 1 12:50 2005 DIR=/lost+found/#5393708 UNEXPECTED SOFT UPDATE INCONSISTENCY CANNOT FIX, FIRST ENTRY IN DIRECTORY CONTAINS setup.ins UNEXPECTED SOFT UPDATE INCONSISTENCY ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups 1436147 files, 20432492 used, 5476106 free (107674 frags, 671054 blocks, 0.4% fr agmentation) mount -r /dev/ad0s3d /mnt cd /mnt/lost+found ; find . -type f | sort | xargs ls -l -rwxr-xr-x 1 jhs staff 3333 Jan 6 2003 ./#5393695/readme.txt -rwxr-xr-x 1 jhs staff 44069 Jul 27 2002 ./#5393698/camsetui.chm -rwxr-xr-x 1 jhs staff 64031 Dec 12 2002 ./#5393698/fvu1.chm -rwxr-xr-x 1 jhs staff 4708 Feb 5 2003 ./#5393698/readme.txt -rwxr-xr-x 1 jhs staff 86165 Feb 19 2003 ./#5393703/demo.dbd -rwxr-xr-x 1 jhs staff 1273 Feb 6 2003 ./#5393703/demo.txt -rwxr-xr-x 1 jhs staff 74235 Mar 1 12:50 ./#5393708/setup.ins -rwxr-xr-x 1 jhs staff 41 Jul 1 2002 ./#5393709 -rwxr-xr-x 1 jhs staff 4557 Jul 1 2002 ./#5393710 -rwxr-xr-x 1 jhs staff 396 Jul 1 2002 ./#5393711 -rwxr-xr-x 1 jhs staff 417 Jul 1 2002 ./#5393712 -rwxr-xr-x 1 root wheel 8192 Mar 1 12:46 ./#5393713 -rw-r--r-- 1 jhs staff 4397 Oct 5 2002 ./#5417187 -rw-r--r-- 1 jhs staff 6612 Oct 3 2002 ./#5417188 -rw-r--r-- 1 root wheel 0 Mar 1 13:25 ./#5417189 -r--r--r-- 1 root wheel 8155 May 22 2004 ./#6432678 -r--r--r-- 1 root wheel 2333 Jan 11 04:13 ./#6432683 -r--r--r-- 1 root wheel 2333 Jan 11 04:13 ./#6432684 -r--r--r-- 1 root wheel 21319 Jan 11 04:13 ./#6432685 -r--r--r-- 1 root wheel 21319 Jan 11 04:13 ./#6432686 -r--r--r-- 1 root wheel 2744 Jan 11 04:13 ./#6432687 -r--r--r-- 1 root wheel 2744 Jan 11 04:13 ./#6432688 -r--r--r-- 1 root wheel 4587 Jan 11 04:13 ./#6432689 -r--r--r-- 1 root wheel 4587 Jan 11 04:13 ./#6432690 -r--r--r-- 1 root wheel 5877 Jan 11 04:13 ./#6432691 -r--r--r-- 1 root wheel 5877 Jan 11 04:13 ./#6432692 -r--r--r-- 1 root wheel 2423 Jan 11 04:13 ./#6432693 -r--r--r-- 1 root wheel 2423 Jan 11 04:13 ./#6432694 -rw-r--r-- 1 root wheel 36534 Jan 11 04:22 ./#6432776 -rw-r--r-- 1 root wheel 36534 Jan 11 04:22 ./#6432777 -rw-r--r-- 1 root wheel 348 Jan 11 04:22 ./#6432778 -rw-r--r-- 1 root wheel 348 Jan 11 04:22 ./#6432779 -rw-r--r-- 1 root wheel 357 Jan 11 04:22 ./#6432780 -rw-r--r-- 1 root wheel 357 Jan 11 04:22 ./#6432781 -rw-r--r-- 1 root wheel 15020 Jan 11 04:22 ./#6432782 -rw-r--r-- 1 root wheel 15020 Jan 11 04:22 ./#6432783 -rw-r--r-- 1 root wheel 12965 Jan 11 04:22 ./#6432784 -rw-r--r-- 1 root wheel 12965 Jan 11 04:22 ./#6432785 -r--r--r-- 1 root wheel 351 Jan 19 20:21 ./#6432788 mkdir lost+found cd lost+found (cd /mnt/lost+found ; tar cf - . ) | tar xf - umount /dev/ad0s3d mount /dev/ad0s3d cd /mnt rm -rf lost+found rm: lost+found/#5393708: Directory not empty rm: lost+found: Directory not empty cd / umount /dev/ad0s3d fsck -y /dev/ad0s3d ** /dev/ad0s3d ** Last Mounted on /mnt ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames MISSING '.' I=5393708 OWNER=root MODE=40755 SIZE=512 MTIME=Mar 1 23:12 2005 DIR=/lost+found/#5393708 UNEXPECTED SOFT UPDATE INCONSISTENCY FIX? yes ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts LINK COUNT DIR I=5393708 OWNER=root MODE=40755 SIZE=512 MTIME=Mar 1 23:12 2005 COUNT 1 SHOULD BE 2 LINK COUNT INCREASING UNEXPECTED SOFT UPDATE INCONSISTENCY ADJUST? yes ** Phase 5 - Check Cyl groups 1436101 files, 20432208 used, 5476390 free (107758 frags, 671079 blocks, 0.4% fr agmentation) ***** FILE SYSTEM WAS MODIFIED ***** fsck -y /dev/ad0s3d # no errors :-) tunefs -p /dev/ad0s3d tunefs: ACLs: (-a) disabled tunefs: MAC multilabel: (-l) disabled tunefs: soft updates: (-n) enabled tunefs: maximum blocks per file in a cylinder group: (-e) 2048 tunefs: average file size: (-f) 16384 tunefs: average number of files in a directory: (-s) 64 tunefs: minimum percentage of free space: (-m) 8% tunefs: optimization preference: (-o) time tunefs: volume label: (-L) df -i /dev/ad0s3d Filesystem Size Used Avail Capacity iused ifree %iused Mounted on /dev/ad0s3d 53G 42G 7.0G 86% 1436101 5276217 21% /mnt dumpfs /dev/ad0s3d > ~/dumpfs How I (probably) created the damaged files system: Did several parallel NFS + AMD moves of trees with Many small files. small being of size 2048 bytes, very many, as these were sliced from a few 4 Gig DVDs (while chasing a different suspect error on another system) The machine crashed a few time, but it wasnt warm at all on top of chassis, & mbmon reports cpu fan spinning OK, Temp.= 29.0, 124.0, 25.0; Rot.= 2636, 2163, 0 Vcore = 1.49, 2.56; Volt. = 3.34, 3.60, 11.61, -11.40, -4.58 & I can see & feel air going in through chassis fan via extra big hole I cut in bottom front of chassis a couple of weeks back. A previous Feb 7 mbmon had a lower voltage, dont know significance: Temp.= 34.0, 124.0, 25.0; Rot.= 2678, 2636, 0 Vcore = 1.49, 2.56; Volt. = 3.34, 3.63, 11.61, -11.29, -3.66 If anyone want to create lots of small slice files: http://berklix.org/~jhs/src/bsd/jhs/bin/public/slice/ If there's any other info I should provide please say, Thanks. - Julian Stacey Net & Sys Eng Consultant, Munich http://berklix.com Mail in Ascii (Html=Spam). Ihr Rauch = mein allergischer Kopfschmerz. From owner-freebsd-fs@FreeBSD.ORG Wed Mar 2 19:40:57 2005 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CF20016A4CE for ; Wed, 2 Mar 2005 19:40:57 +0000 (GMT) Received: from sccrmhc12.comcast.net (sccrmhc12.comcast.net [204.127.202.56]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4843643D2F for ; Wed, 2 Mar 2005 19:40:55 +0000 (GMT) (envelope-from tbonius@comcast.net) Received: from ostros (c-24-18-102-54.client.comcast.net[24.18.102.54]) by comcast.net (sccrmhc12) with SMTP id <2005030219405401200run17e>; Wed, 2 Mar 2005 19:40:54 +0000 Message-ID: <001801c51f5f$cdde9dc0$4300a8c0@home.lan> From: "Thomas Foster" To: "Loren M. Lang" References: <00f201c515fa$8caef250$4300a8c0@home.lan> <20050227163636.GA1672@alzatex.com> Date: Wed, 2 Mar 2005 11:41:17 -0800 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 cc: freebsd-fs@freebsd.org Subject: Re: UFS2 Recovery Questions X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Mar 2005 19:40:57 -0000 Yes, I did use the -r option (bad muscle memmory habits), and it removed the symlink and the directories it pointed at. At this point I am still attempting to rescue the data from an image via sleuthkit T ----- Original Message ----- From: "Loren M. Lang" To: "Thomas Foster" Cc: Sent: Sunday, February 27, 2005 8:36 AM Subject: Re: UFS2 Recovery Questions > On Fri, Feb 18, 2005 at 12:43:45PM -0800, Thomas Foster wrote: >> Please excuse me if this is not the correct forum in which to ask this >> question and please try to bear with me. I was hoping to understand a few >> things about attempting to retrieve information from a drive on my >> FreeBSD 5.3 system. >> >> I recently was rearranging my web server content and accidentally removed >> a symbolic link recursively >> >> root@host # rm -rf music > > Are you sure the command wasn't rm -fr music/? The final / can make a > big differnece with symlinks. It forces the system to look it up as a > directory first, and without that, I think it would only remove the > symlink. Also, -r should never be needed for a symlink, even if it > point to a directory. > >> >> The music link pointed to a directory that existed on a spserate drive >> mounted as /storage >> >> music -> /storage/Music/Mp3s >> > >> >> Now the questions is.. are the files even recoverable? Is this a lost >> cause? Any additional information required, any comments or suggestions, >> anything would be helpful. I thank you for your time in the matter. >> >> Thomas Foster >> http://www.section6.net >> _______________________________________________ >> freebsd-fs@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-fs >> To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" >> > > -- > I sense much NT in you. > NT leads to Bluescreen. > Bluescreen leads to downtime. > Downtime leads to suffering. > NT is the path to the darkside. > Powerful Unix is. > > Public Key: ftp://ftp.tallye.com/pub/lorenl_pubkey.asc > Fingerprint: B3B9 D669 69C9 09EC 1BCD 835A FAF3 7A46 E4A3 280C > > From owner-freebsd-fs@FreeBSD.ORG Wed Mar 2 23:21:52 2005 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 02ED816A4CE for ; Wed, 2 Mar 2005 23:21:52 +0000 (GMT) Received: from tower.berklix.org (bsd.bsn.com [194.221.32.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4A5A143D39 for ; Wed, 2 Mar 2005 23:21:51 +0000 (GMT) (envelope-from jhs@berklix.org) Received: from js.berklix.net (p549A46F9.dip.t-dialin.net [84.154.70.249]) (authenticated bits=0) by tower.berklix.org (8.12.9p2/8.12.9) with ESMTP id j22NLiYS051059; Thu, 3 Mar 2005 00:21:44 +0100 (CET) (envelope-from jhs@tower.berklix.net) Received: from fire.jhs.private (fire.jhs.private [192.168.91.41]) by js.berklix.net (8.12.11/8.12.11) with ESMTP id j22NMfWX005651; Thu, 3 Mar 2005 00:23:06 +0100 (CET) (envelope-from jhs@tower.berklix.net) Received: from fire.jhs.private (localhost [127.0.0.1]) by fire.jhs.private (8.13.1/8.13.1) with ESMTP id j22NMfdD031805; Thu, 3 Mar 2005 00:22:41 +0100 (CET) (envelope-from jhs@fire.jhs.private) Message-Id: <200503022322.j22NMfdD031805@fire.jhs.private> To: freebsd-fs@freebsd.org From: "Julian Stacey" Organization: http://berklix.com/~jhs/ Munich Unix, BSD, Internet User-agent: EXMH http://beedub.com/exmh/ on FreeBSD http://freebsd.org In-reply-to: Your message of "Wed, 02 Mar 2005 00:46:39 +0100." <200503012346.j21NkdrU002367@fire.jhs.private> Date: Thu, 03 Mar 2005 00:22:41 +0100 Sender: jhs@berklix.org Subject: Re: A bad lost+found causes fsck of FFS to repeatefly fail. X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Mar 2005 23:21:52 -0000 I wrote about 24 hours ago: > I had a FFS error that fsck couldnt fix, & I've seen similar before: > If content of lost+found/ is itself damaged, fsck fails, it seems. > Then one has to manually [copy elsewhere] & rm -rf lost+found then re-fsck. > Should the above be added to man fsck, or > content below submitted as a send-pr ? Or do readers here > include FFS / FSCK maintainers ? > > Log & environ follow: > > uname -a > FreeBSD fire.jhs.private 5.3-RELEASE FreeBSD 5.3-RELEASE #0: Sat > Feb 26 21:47:28 CET 2005 > jhs@fire.jhs.private:/usr1/src/sys/amd64/compile/FIRE64.small amd64 Same scenario a day later on another of my hosts ! This one is not a 64bit amd just a normal 686, FreeBSD film.jhs.private 5.3-RELEASE FreeBSD 5.3-RELEASE #0: Fri Nov 5 04:19:18 UTC 2004 root@harlow.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 & its a 33 Gig instead of 40 Gig partition. Other than that, same story. - Julian Stacey Net & Sys Eng Consultant, Munich http://berklix.com Mail in Ascii (Html=Spam). Ihr Rauch = mein allergischer Kopfschmerz.