On May 17, 2002 08:32 -0500, Jesse Pollard wrote:
> Note - most these really large filesystems allow the inode tables and
> bitmaps to be stored on disks with a relatively small blocksize (raid 5),
> and the data on different drives (striped) with a large block size (I believe
> ours is 64K to 128K sized data blocks, inode/bitmaps are 16K-32K.)
>
> The division allows for high integrity of the meta data (which is also
> backed up daily (incremental) - but without the corresponding datablocks),
> along with maximum capacity for data. 1/5 of 200TB is about 40TB if raid5
> were used with everything.
Interestingly, this can also be done for Lustre, the OSS cluster
filesystem I am currently working on (http://www.clusterfs.com).
All of the filesystem metadata is actually stored on a separate server,
so its disk can be configured totally separately from the file data.
Cheers, Andreas
-- Andreas Dilger http://www-mddsp.enel.ucalgary.ca/People/adilger/ http://sourceforge.net/projects/ext2resize/- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu May 23 2002 - 22:00:15 EST