Date: Sun, 12 Jun 2005 17:33:48 +0300 From: Giorgos Keramidas <keramida@ceid.upatras.gr> To: Wojciech Puchar <wojtek@tensor.3miasto.net> Cc: freebsd-questions@freebsd.org Subject: Checking huge filesystems [was: Re: Resizing /var (maybe off topic)] Message-ID: <20050612143348.GB57689@gothmog.gr> In-Reply-To: <Pine.NEB.4.62.0506121428160.10182@chylonia.3miasto.net> References: <42AAEA6B.9030602@frenchsuballiance.cjb.net> <Pine.NEB.4.62.0506121412260.21@chylonia.3miasto.net> <Pine.NEB.4.62.0506121428160.10182@chylonia.3miasto.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2005-06-12 14:41, Wojciech Puchar <wojtek@tensor.3miasto.net> wrote: > > i'm using different unices for 7 years and excluding few cases i never > made other partitioning scheme than 2 partitions: swap and / > > i have no problems like "there's out of space in partition x while > plenty of y". it's far easier to do backups too (single dump). [...] > fsck speed is same in checking one partition or many smaller. and it > doesn't matter at all as FreeBSD (and NetBSD) doesn't crash every few > hours like windows While you have made a few good and valid points, this last one is not really true. FWIW, Checking a filesystem involves allocating enough memory to reconstruct the inode and data block allocation bitmaps, when something is wrong, along with other meta-information. This information is kept in data structures that are traversed many times. It may be possible to check 20 filesystems of 100 GB each a lot faster than a single 2000 GB filesystem, if the fsck process that is supposed to check the latter runs out of memory because of the filesystem size.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050612143348.GB57689>