On 2010-01-27, Rob Sheldon <r...@associatedtechs.com> wrote:
> The longer version: this is a backup server running backuppc for a
> corporate client ("large enough number of workstations") that does research
> work ("some really big files"). I _thought_ I had read the big filesystem
> FAQ carefully, but somehow missed that fsck simply couldn't handle anything
> over 1TB without doing funny things during the fs setup."The default is to create an inode for each 8192 bytes of data space". They aren't especially funny things; if you have a fairly large filesystem with files most people would now call "medium" or larger, you'll probably be rather surprised at the difference in fsck time if you lower the inode density a bit... If it's not essential data I don't think I'd waste time tryings to fsck it. Force a read-only mount and copy any backuppc config you need off first, disklabel, allocate some swap, consider splitting into smaller chunks, and newfs with more appropriate settings, you'll still have the main OS install on the other partitions. Or, indeed, use a different OS if you prefer.
