Date: Tue, 8 Aug 2006 09:17:24 +0100 From: Freminlins <freminlins@gmail.com> To: "Atom Powers" <atom.powers@gmail.com> Cc: freebsd-questions@freebsd.org Subject: Re: Large File System? Message-ID: <eeef1a4c0608080117r22d05716x1e623dd6ee2cf573@mail.gmail.com> In-Reply-To: <df9ac37c0608071636j2f28bc6en66e985d528e8d85f@mail.gmail.com> References: <df9ac37c0608071513n7fdfc928r9d1aa3b9e8edfaec@mail.gmail.com> <ygfzmegm97g.fsf@dominion.borderworlds.dk> <df9ac37c0608071636j2f28bc6en66e985d528e8d85f@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 08/08/06, Atom Powers <atom.powers@gmail.com> wrote: > > > Thanks. I found my problem. (Sysinstall, aka fdisk, won't do more that > 1.2TB.) > BTW, anybody have any good advice on how to manage a large file system? Unfortunately I have to say "consider Solaris or Linux as they have journalling file systems." Although I have a couple of big file systems on FreeBSD, it is not a pretty sight if there is some sort of problem. Recently our colo lost power. The two boxes that needed manually fixing were the two big file system boxes. Background fsck did not fix them. To compare, we have one almost identical box running Linux. It came straight back up courtesy of ext3. Ignoring all the suggestions to get UPS (the colo had generator backed UPS which failed), etc, problems can/do happen. And when they do, journalling for big file systems is very useful. The single most important thing missing for me in FreeBSD is a journalling file system as I would use it on every box. You don't need to do anything more to manage big file systems per se. How big a file system are you going to create? What are you going to use it for? That might help with suggestions. --Atom Powers-- > Frem.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?eeef1a4c0608080117r22d05716x1e623dd6ee2cf573>