From owner-freebsd-questions Fri Oct 13 9:27: 8 2000 Delivered-To: freebsd-questions@freebsd.org Received: from sigbus.com (sigbus.com [207.211.10.110]) by hub.freebsd.org (Postfix) with ESMTP id 3AEDF37B672 for ; Fri, 13 Oct 2000 09:27:04 -0700 (PDT) Received: (from henrich@localhost) by sigbus.com (8.9.3/8.9.3) id JAA12571; Fri, 13 Oct 2000 09:26:56 -0700 (PDT) (envelope-from henrich) Date: Fri, 13 Oct 2000 09:26:56 -0700 From: Charles Henrich To: Greg Lehey Cc: freebsd-questions@freebsd.org Subject: Re: Vinum/Fsck 1TB filesystem Message-ID: <20001013092656.B12492@sigbus.com> References: <20001012113054.A9727@sigbus.com> <20001013131107.M2593@wantadilla.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <20001013131107.M2593@wantadilla.lemis.com> X-Operating-System: FreeBSD 3.3-RELEASE X-PGP-Fingerprint: 1024/F7 FD C7 3A F5 6A 23 BF 76 C4 B8 C9 6E 41 A4 4F Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On the subject of Re: Vinum/Fsck 1TB filesystem, Greg Lehey stated: > [Format recovered--see http://www.lemis.com/email/email-format.html] > > Please don't wrap program output and log files. Sorry, X-Windows paste got me. > Well, without knowing what went before, no. That's why I ask for the > information I do at http://www.vinumvm.org/vinum/how-to-debug.html. > Obviously you'll get this if you forget to newfs, or if newfs fails > for any reason. It would also be nice to know whether you have ever > been able to fsck this file system: you're pretty close to the > theoretical file system size limit. I'd like to investigate this, > since we don't see many 1 TB file systems, but at the moment I'm flat > out preparing for the next week of conferences. Is it possible to > recreate this problem later, and make 2 512 GB file systems for the > moment? Well right now there is data on the drives. Setting it up the first time through went flawlessly. I used vinum -stripe to stripe across the two 512GB drives, the newfs'd the bad boy and mounted it up. We used it for several hours when during the creation of a file write the system puked badly. During this write the first of the two drives activity lights stayed on, until I forced a reboot (some processes would not die), when it came back up the above error occured. I finally remembered fsck -b (duh), and it fsck'd off the alternate block just fine, corrected a single file error. When I went and touched the same file however, the same error conditions occured, and another reboot. Another fsck, and removing the file and directory structure it was in, and now everything is working okay. I've not ever seen anything like this before. Im beginning to think that taking the FS up to 1TB is just too risky, so will try and break it back down to two 512GB drives next week after the data is backed up. Im curious why fsck is horking so badly on that boot block though, shouldnt it automagically look for backups ? -Crh Charles Henrich Manex Visual Effects henrich@sigbus.com http://www.sigbus.com/~henrich To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message