Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!amelia!sun217!truesdel
From: truesdel@sun217..nas.nasa.gov (David A. Truesdell)
Newsgroups: comp.unix.wizards
Subject: Re: bigger longs (64 bits)
Message-ID: <4849@amelia.nas.nasa.gov>
Date: 9 Feb 90 21:22:24 GMT
References: <11071@encore.Encore.COM> <4812@amelia.nas.nasa.gov> <11083@encore.Encore.COM> <605@bbxsda.UUCP>
Sender: news@amelia.nas.nasa.gov
Lines: 24

scott@bbxsda.UUCP (Scott Amspoker) writes:
>In article <4812@amelia.nas.nasa.gov> (David A. Truesdell) writes:
>>lseek is already "broken" here.  I'm in the process of testing a striped
>>filesystem which currently weighs in at 20 GigaBytes, with a production size
>>expected to be 200+ GB.  

>Forgive my ignorance, but, what is a "striped" filesystem?

A striped (or stripeing) filesystem is one in which the filesystem is spread
out over a set of disks in order to increase capacity and/or performance and/or
reliability.  The filesystem I'm testing would be classed as "level 5 RAID".
(That's "Redundant Array of Inexpensive Disks", too bad our disks can't really
be called "Inexpensive".)

You can check out the September '89 (v7i9) issue of UNIX Review, which has an
article ("Winged Memory") which covers the ideas behind RAID, and the different
classes of RAID filesystems.


T.T.F.N.,
dave truesdell (truesdel@prandtl.nas.nasa.gov)

"Testing can show the presense of bugs, but not their absence." -- Dijkstra
"Each new user of a new system uncovers a new class of bugs." -- Kernighan