From owner-freebsd-stable@FreeBSD.ORG Fri Sep 11 08:57:26 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 004A7106566B for ; Fri, 11 Sep 2009 08:57:25 +0000 (UTC) (envelope-from dalroi@solfertje.student.utwente.nl) Received: from solfertje.student.utwente.nl (solfertje.student.utwente.nl [130.89.167.40]) by mx1.freebsd.org (Postfix) with ESMTP id A95638FC26 for ; Fri, 11 Sep 2009 08:57:25 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by solfertje.student.utwente.nl (Postfix) with SMTP id 9C40F8035 for ; Fri, 11 Sep 2009 10:57:24 +0200 (CEST) Received: from hollewijn.internal (hollewijn.internal [10.236.150.4]) by solfertje.student.utwente.nl (Postfix) with ESMTP id 07EB88034; Fri, 11 Sep 2009 10:57:23 +0200 (CEST) Mime-Version: 1.0 (Apple Message framework v1075.2) Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes From: Alban Hertroys In-Reply-To: <4AA9C7C3.1000007@modulus.org> Date: Fri, 11 Sep 2009 10:57:22 +0200 Content-Transfer-Encoding: 7bit Message-Id: <0853758B-4823-49B8-B63E-B5B72FE2661B@solfertje.student.utwente.nl> References: <15274_1252628653_4AA998AD_15274_284_1_4AA99819.9000601@modulus.org> <20090911034253.GM81123@cesium.hyperfine.info> <4AA9C7C3.1000007@modulus.org> To: Andrew Snow X-Mailer: Apple Mail (2.1075.2) X-DSPAM-Result: Innocent X-DSPAM-Processed: Fri Sep 11 10:57:24 2009 X-DSPAM-Confidence: 1.0000 X-DSPAM-Probability: 0.0023 X-DSPAM-Signature: 74,4aaa10f412071914714074 X-DSPAM-Factors: 27, Cc*, freebsd-stable@freebsd.org Subject: Re: gconcat file system damage X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Sep 2009 08:57:26 -0000 On 11 Sep 2009, at 5:45, Andrew Snow wrote: > Peter C. Lai wrote: >> What is the status of growfs(8) then? > > As far as I can tell, it doesn't work reliably with UFS2 partitions, > and it doesn't work at all with large partitions. > > People who do try to use it, can end up with corrupted > filesystems... and the code is currently unmaintained. Aha, I forgot about that step, but I did indeed use growfs to expand it. Is there any way to repair the corruption without erasing my data, or do I need to buy an external disk to backup to first (which I need for backups anyway)? If so, what's the pattern of the corruption? Is it likely to only start after a certain size? Lastly, having a tool in the base system that causes these kinds of issues doesn't seem like a very good idea. growfs does issue a warning that made me read the bugs section in the man page. That section points to an ffsinfo command that I ran on the filesystem in question, but it appears to be alright: ===== START CYLINDER SUMMARY ===== # 0@28202000: 0. csum in fscs ndir int32_t 0x00000001 nbfree int32_t 0x00002474 nifree int32_t 0x00005bfd nffree int32_t 0x0000000d ===== END CYLINDER SUMMARY ===== The filesystem is 740G, which seems to fit in the 'critical data structure'; 1480 < 0x2474... Or is this a different (and undocumented) issue? Alban Hertroys -- Screwing up is the best way to attach something to the ceiling. !DSPAM:74,4aaa10f412071914714074!