Main Page | Report this Page
Computers Forum Index  »  Computer - Databases  »  A Silly Database Question...
Page 1 of 2    Goto page 1, 2  Next

A Silly Database Question...

Author Message
howfie...
Posted: Sun Jun 14, 2009 11:06 pm
Guest
I couldn't find this information on Google, but why is the
visual representation of a database (in presentations and
graphical descriptions) always a can or a cylinder? Is it
because hard drives contain cylinders or is it because that
is what hard drives used to look like before the rectangular
ones appeared?

Thanks,
Josh
 
Ed Prochak...
Posted: Sun Jun 14, 2009 11:06 pm
Guest
On Jun 14, 3:06 pm, howfie <yaday... at (no spam) yabloo.com> wrote:
Quote:
I couldn't find this information on Google, but why is the
visual representation of a database (in presentations and
graphical descriptions) always a can or a cylinder? Is it
because hard drives contain cylinders or is it because that
is what hard drives used to look like before the rectangular
ones appeared?

Thanks,
Josh

Yes it harks back to storage being disc storage (hard drives).

Ed
 
Tony Toews [MVP]...
Posted: Mon Jun 15, 2009 4:46 am
Guest
howfie <yadayada at (no spam) yabloo.com> wrote:

Quote:
I couldn't find this information on Google, but why is the
visual representation of a database (in presentations and
graphical descriptions) always a can or a cylinder? Is it
because hard drives contain cylinders or is it because that
is what hard drives used to look like before the rectangular
ones appeared?

Correct. See http://en.wikipedia.org/wiki/Early_IBM_disk_storage#IBM_3330 for a
picture of such. And that is basically what you would see inside a modern hard
drive. Mind you that one is 200 Mb. I've seen others in 1979 which were mounted in
a machine slightly narrower than a washing machien and were 10 Mb.

Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
Granite Fleet Manager http://www.granitefleet.com/
 
Walter Mitty...
Posted: Mon Jun 15, 2009 2:45 pm
Guest
"Tony Toews [MVP]" <ttoews at (no spam) telusplanet.net> wrote in message
news:t86b35lf6hqj2niterb2hirsni7cm300vr at (no spam) 4ax.com...
Quote:
howfie <yadayada at (no spam) yabloo.com> wrote:

I couldn't find this information on Google, but why is the
visual representation of a database (in presentations and
graphical descriptions) always a can or a cylinder? Is it
because hard drives contain cylinders or is it because that
is what hard drives used to look like before the rectangular
ones appeared?

Correct. See http://en.wikipedia.org/wiki/Early_IBM_disk_storage#IBM_3330
for a
picture of such. And that is basically what you would see inside a
modern hard
drive. Mind you that one is 200 Mb. I've seen others in 1979 which were
mounted in
a machine slightly narrower than a washing machien and were 10 Mb.

Also see the wikipedia article on drum memory.
http://en.wikipedia.org/wiki/Magnetic_drum

The picture of the drum in the article really looks like a can. Drums fell
out of favor when compared to discs, because moveable heads made for much
cheaper construction.
In addition, stacking disk on top of each other in cylinder fashion allowed
you to pack more media onto the same square footage of floor space. The
great timesharing computers of the 1964-1982 time frame all used discs of
various sizes and capacities, as did the giant database mainframes of the
era. The early computers in the 1950s tended to use drums for main memory,
before core memory gained widespread use. See the article on the IBM 650.
http://en.wikipedia.org/wiki/IBM_650
 
howfie...
Posted: Tue Jun 16, 2009 1:20 pm
Guest
"Walter Mitty" <wamitty at (no spam) verizon.net> wrote in
news:wDpZl.1097$P5.777 at (no spam) nwrddc02.gnilink.net:

Quote:

"Tony Toews [MVP]" <ttoews at (no spam) telusplanet.net> wrote in message
news:t86b35lf6hqj2niterb2hirsni7cm300vr at (no spam) 4ax.com...
howfie <yadayada at (no spam) yabloo.com> wrote:

I couldn't find this information on Google, but why is the
visual representation of a database (in presentations and
graphical descriptions) always a can or a cylinder? Is it
because hard drives contain cylinders or is it because that
is what hard drives used to look like before the rectangular
ones appeared?

Correct. See
http://en.wikipedia.org/wiki/Early_IBM_disk_storage#IBM_3330 for a
picture of such. And that is basically what you would see inside a
modern hard
drive. Mind you that one is 200 Mb. I've seen others in 1979 which
were mounted in
a machine slightly narrower than a washing machien and were 10 Mb.

Also see the wikipedia article on drum memory.
Cool, thanks for all the info guys. I just wanted to be 100%

sure before I said anything to my database students or add
it to my powerpoints Smile.

Josh

Quote:
http://en.wikipedia.org/wiki/Magnetic_drum

The picture of the drum in the article really looks like a can. Drums
fell out of favor when compared to discs, because moveable heads made
for much cheaper construction.
In addition, stacking disk on top of each other in cylinder fashion
allowed you to pack more media onto the same square footage of floor
space. The great timesharing computers of the 1964-1982 time frame
all used discs of various sizes and capacities, as did the giant
database mainframes of the era. The early computers in the 1950s
tended to use drums for main memory, before core memory gained
widespread use. See the article on the IBM 650.
http://en.wikipedia.org/wiki/IBM_650




 
paul c...
Posted: Fri Jun 19, 2009 5:15 am
Guest
howfie wrote:
Quote:
"Walter Mitty" <wamitty at (no spam) verizon.net> wrote in
news:wDpZl.1097$P5.777 at (no spam) nwrddc02.gnilink.net:

"Tony Toews [MVP]" <ttoews at (no spam) telusplanet.net> wrote in message
news:t86b35lf6hqj2niterb2hirsni7cm300vr at (no spam) 4ax.com...
howfie <yadayada at (no spam) yabloo.com> wrote:

I couldn't find this information on Google, but why is the
visual representation of a database (in presentations and
graphical descriptions) always a can or a cylinder? Is it
because hard drives contain cylinders or is it because that
is what hard drives used to look like before the rectangular
ones appeared?
Correct. See
http://en.wikipedia.org/wiki/Early_IBM_disk_storage#IBM_3330 for a
picture of such. And that is basically what you would see inside a
modern hard
drive. Mind you that one is 200 Mb. I've seen others in 1979 which
were mounted in
a machine slightly narrower than a washing machien and were 10 Mb.
Also see the wikipedia article on drum memory.
Cool, thanks for all the info guys. I just wanted to be 100%
sure before I said anything to my database students or add
it to my powerpoints Smile.

Josh

http://en.wikipedia.org/wiki/Magnetic_drum

The picture of the drum in the article really looks like a can. Drums
fell out of favor when compared to discs, because moveable heads made
for much cheaper construction.
In addition, stacking disk on top of each other in cylinder fashion
allowed you to pack more media onto the same square footage of floor
space. The great timesharing computers of the 1964-1982 time frame
all used discs of various sizes and capacities, as did the giant
database mainframes of the era. The early computers in the 1950s
tended to use drums for main memory, before core memory gained
widespread use. See the article on the IBM 650.
http://en.wikipedia.org/wiki/IBM_650



I must say I thought it was one of the greatest questions I've ever seen
here. And half-thought it was a send-up until Walter replied! If this
is for real, maybe you should point out to the kids that the cylinders
were and are 'virtual', get them used to what that term can mean.


Once, I was given a 2321 (if I recall the model), sometimes called a
spaghetti picker. Real Buck Rogers concept, half disk and half tape
(with an astounding 500 msec access/latency time) but with serious
engineering, like a three-horsepower motor labelled "lubricate every
twenty years", no guff. Serious Nasa-style hydraulics, twenty gallon
reservoir and compressed nitrogen. I couldn't afford to hook it up. I
knew a really smart programmer but much younger who asked me what a
mainframe disk looked like. I told him the box that held seven or eight
of them was taller and longer than him so the 'Customer Engineer' (who
was a regular presence at all big IBM installations right up to about
twenty years ago) could get his head inside. Unfortunately it seems one
CE was decapitated which resulted in an EC, so-called "engineering
change".


When I thought again about his question afterwards I remembered how much
closer programming was to manual labour I was envious of that kid
because he had saved himself a lot of wasted years and I wished I had
been born later. On some smaller machines even in the 1960's, people
used tape drives for working storage to sort. These days, for myself, I
just use solid state stuff.


In those days a macho term among assembler programmers was
'bare-metal-programming', which the typical disks encouraged with the
'Count-Key-Data' instructions that were wired into their controllers.
Thankfully, modern disks have abstracted out that physical nonsense.
The same people considered it important to flip three thousand cards
without spilling them and looked down their noses at any object deck
that was thinner than three or four inches.


Then there's memory capacity. Did you know that even into the 1990's a
typical PARS/ACP flight reservation system for a medium-sized airline
(say 100-300 planes) occupied only about 300MB disk space? I have to
wonder how things would be now if today's main memory were available
then, a lot of decisions would have been different. Of course we know
what really happened to that memory - as a friend who was an IBM
salesman in the 1960's was told when some 512KB memory cpu's came out:
"your customers can't use it, we need most of it for OS/360'. In those
days the famous IBM motto was "THINK" and they used to give out desk
plaques to remind you to do that. I saw one that had been graffitee'd
to say "THINK OR THWIM".
..
 
Walter Mitty...
Posted: Fri Jun 19, 2009 5:15 am
Guest
"paul c" <toledobythesea at (no spam) oohay.ac> wrote in message
news:0IC_l.31406$Db2.24878 at (no spam) edtnps83...
Quote:
howfie wrote:
"Walter Mitty" <wamitty at (no spam) verizon.net> wrote in
news:wDpZl.1097$P5.777 at (no spam) nwrddc02.gnilink.net:
"Tony Toews [MVP]" <ttoews at (no spam) telusplanet.net> wrote in message
news:t86b35lf6hqj2niterb2hirsni7cm300vr at (no spam) 4ax.com...
howfie <yadayada at (no spam) yabloo.com> wrote:

I couldn't find this information on Google, but why is the
visual representation of a database (in presentations and
graphical descriptions) always a can or a cylinder? Is it
because hard drives contain cylinders or is it because that
is what hard drives used to look like before the rectangular
ones appeared?
Correct. See
http://en.wikipedia.org/wiki/Early_IBM_disk_storage#IBM_3330 for a
picture of such. And that is basically what you would see inside a
modern hard
drive. Mind you that one is 200 Mb. I've seen others in 1979 which
were mounted in
a machine slightly narrower than a washing machien and were 10 Mb.
Also see the wikipedia article on drum memory.
Cool, thanks for all the info guys. I just wanted to be 100%
sure before I said anything to my database students or add
it to my powerpoints Smile.

Josh

http://en.wikipedia.org/wiki/Magnetic_drum

The picture of the drum in the article really looks like a can. Drums
fell out of favor when compared to discs, because moveable heads made
for much cheaper construction.
In addition, stacking disk on top of each other in cylinder fashion
allowed you to pack more media onto the same square footage of floor
space. The great timesharing computers of the 1964-1982 time frame
all used discs of various sizes and capacities, as did the giant
database mainframes of the era. The early computers in the 1950s
tended to use drums for main memory, before core memory gained
widespread use. See the article on the IBM 650.
http://en.wikipedia.org/wiki/IBM_650


I must say I thought it was one of the greatest questions I've ever seen
here. And half-thought it was a send-up until Walter replied! If this is
for real, maybe you should point out to the kids that the cylinders were
and are 'virtual', get them used to what that term can mean.

pace? I have to
wonder how things would be now if today's main memory were available then,
a lot of decisions would have been different. Of course we know what
really happened to that memory - as a friend who was an IBM salesman in
the 1960's was told when some 512KB memory cpu's came out: "your customers
can't use it, we need most of it for OS/360'. In those days the famous
IBM motto was "THINK" and they used to give out desk plaques to remind you
to do that. I saw one that had been graffitee'd to say "THINK OR THWIM".
.

Don't get me started down memory lane.
 
Tony Toews [MVP]...
Posted: Fri Jun 19, 2009 5:15 am
Guest
paul c <toledobythesea at (no spam) oohay.ac> wrote:

Quote:
Then there's memory capacity. Did you know that even into the 1990's a
typical PARS/ACP flight reservation system for a medium-sized airline
(say 100-300 planes) occupied only about 300MB disk space? I have to
wonder how things would be now if today's main memory were available
then, a lot of decisions would have been different. Of course we know
what really happened to that memory - as a friend who was an IBM
salesman in the 1960's was told when some 512KB memory cpu's came out:
"your customers can't use it, we need most of it for OS/360'. In those
days the famous IBM motto was "THINK" and they used to give out desk
plaques to remind you to do that. I saw one that had been graffitee'd
to say "THINK OR THWIM".

I missed the memory capacity days. Or really having to think about that stuff. I
started working on systems with 32, 48 or 64 Kb of RAM generally.. But I recall my
friend who'd been in the business 10 years longer than me saying he quit one company
a number of years previously because they wouldn't expand the RAM from 4 kb to 8 kb
even though that would've cost about $60K. He said they wasted much more than the
$60K in programmers time trying to shoehorn programs into that system.

Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
Granite Fleet Manager http://www.granitefleet.com/
 
howfie...
Posted: Mon Jun 22, 2009 3:54 am
Guest
Hi Paul,

Thanks for the info. With pictures like this,
http://www.columbia.edu/acis/history/cell2.jpg,
I guess it's easy to see why it's always a can or a cylinder.

Could you discuss a little more about your 'cylinders are virtual'
comment? I'm not really a hardware guy and this question is actually for
a simple introductory relational database course that I teach which
exclusively focuses on 'the query' and SQL. In the first lecture though,
I really like to talk about the history of databases and other little
tidbits of potentially useful (or useless) information.

Thanks!

paul c <toledobythesea at (no spam) oohay.ac> wrote in news:0IC_l.31406$Db2.24878
at (no spam) edtnps83:
Quote:

I must say I thought it was one of the greatest questions I've ever
seen
here. And half-thought it was a send-up until Walter replied! If this
is for real, maybe you should point out to the kids that the cylinders
were and are 'virtual', get them used to what that term can mean.


Once, I was given a 2321 (if I recall the model), sometimes called a
spaghetti picker. Real Buck Rogers concept, half disk and half tape
(with an astounding 500 msec access/latency time) but with serious
engineering, like a three-horsepower motor labelled "lubricate every
twenty years", no guff. Serious Nasa-style hydraulics, twenty gallon
reservoir and compressed nitrogen. I couldn't afford to hook it up. I
knew a really smart programmer but much younger who asked me what a
mainframe disk looked like. I told him the box that held seven or
eight
of them was taller and longer than him so the 'Customer Engineer' (who
was a regular presence at all big IBM installations right up to about
twenty years ago) could get his head inside. Unfortunately it seems
one
CE was decapitated which resulted in an EC, so-called "engineering
change".


When I thought again about his question afterwards I remembered how
much
closer programming was to manual labour I was envious of that kid
because he had saved himself a lot of wasted years and I wished I had
been born later. On some smaller machines even in the 1960's, people
used tape drives for working storage to sort. These days, for myself,
I
just use solid state stuff.


In those days a macho term among assembler programmers was
'bare-metal-programming', which the typical disks encouraged with the
'Count-Key-Data' instructions that were wired into their controllers.
Thankfully, modern disks have abstracted out that physical nonsense.
The same people considered it important to flip three thousand cards
without spilling them and looked down their noses at any object deck
that was thinner than three or four inches.


Then there's memory capacity. Did you know that even into the 1990's a
typical PARS/ACP flight reservation system for a medium-sized airline
(say 100-300 planes) occupied only about 300MB disk space? I have to
wonder how things would be now if today's main memory were available
then, a lot of decisions would have been different. Of course we know
what really happened to that memory - as a friend who was an IBM
salesman in the 1960's was told when some 512KB memory cpu's came out:
"your customers can't use it, we need most of it for OS/360'. In those
days the famous IBM motto was "THINK" and they used to give out desk
plaques to remind you to do that. I saw one that had been graffitee'd
to say "THINK OR THWIM".
.
 
paul c...
Posted: Mon Jun 22, 2009 10:34 pm
Guest
howfie wrote:
Quote:
Hi Paul,

Thanks for the info. With pictures like this,
http://www.columbia.edu/acis/history/cell2.jpg,
I guess it's easy to see why it's always a can or a cylinder.

Could you discuss a little more about your 'cylinders are virtual'
comment? ...

I added some rambling history to Walter M's comment, but in a nutshell
they are virtual because they aren't real (ie., not real in a physical
sense,. although most old-time programmers treated them as if they were
real, this dates from the time when programmers though programs were
'inside' decks of 'object' cards)! The word 'virtual' had many other
targets besides those to do with disks and basically anything you
couldn't kick with your foot or at least not hurt your foot, was allowed
to be labelled as 'virtual'. Date and Dawen started to work during the
middle of that era and maybe that's partly why today they sometimes use
a term like 'virtual' to describe a 'relvar', some relvars are 'real'
and some are 'virtual', but this usage seems to me a refinement that
must exclude the hoi polloi (most of my acquaintances) from ever
understanding the difference. An outsider who is literate except for
computers might well conclude that if all relations are virtual, so must
be all relvars. lSometimes I think it even prevents db experts from
understanding what logical/data independence really means.
 
paul c...
Posted: Mon Jun 22, 2009 11:04 pm
Guest
paul c wrote:
Quote:
Walter Mitty wrote:
"howfie" <yadayada at (no spam) yabloo.com> wrote in message
news:Xns9C31ABF92C6E6yadayadayabloocom at (no spam) 216.196.97.131...
Hi Paul,

Thanks for the info. With pictures like this,
http://www.columbia.edu/acis/history/cell2.jpg,
I guess it's easy to see why it's always a can or a cylinder.
...


Some other comments: The use of multiple platters was an attempt to
increase the probability that more 'record's would be 'found'/accessed
by a single head seek (the seek is along an imaginary radius of the
platter). This is reminiscent of the engineering that was being added
to jet airplane engines in the same period, many features added that had
nothing to do with the original concept but rather with physical
limitations and side-effects. Somewhere there is a great article about
the complications of the jet engine for social and ergonomic reasons
written by a Harvard professor, it is more humanist than most of what
comes out of that business school.


Also, the programmable controllers contained some Buck Rogers concepts
that have since gone by the wayside. The electronics for each disk head
assembly treated certain cylinders (multiple vertical tracks), as
'special'. So there was a physical index of the 'file' locations record
in designated 'tracks' of iron oxide. In the IBM world this was known
as the VTOC/Volume Table of Contents. I had one boss who said if he
read one more resume of a system programmer who had invented a new VTOC
manipulation program, he was going to puke. This is some of why I wish
I were born later, I remember getting assigned to write some disk access
routines for a company branch in South America. They didn't want to use
the generic subroutines for disk access provided by IBM which had memory
sizes of thousands of bytes because they were short of 'main memmory'
and it was too expensive to bump their main memory from 16Kilo-bytes.
Whereas 'channel programs' of less than a hundred bytes would suffice to
squeeze their application into the available memory. 'Virtual'/hardware
'paging' memory required buying a new cpu but even with paging, there
were always high-use routines that one wanted kept in memory at all
times. It seems a lot of the 'system' programmers from those days are
still alive and as busy as ever on usenet. They can tell you a lot
more than I can, see the alt.folklore.computers usenet group.


I think everybody interested in db should remember that the somewhat
seminal System R IBM group was heavily influenced by the limitations of
the hardward ot he early 1970's. It might be good thesis topic for some
bright kid to examine the way db history has been influenced by this,
rightly or wrongly. Seems important to me to remember that we might be
in quite a different position if hardware developments had occurred in a
different historical order.
 
paul c...
Posted: Mon Jun 22, 2009 11:18 pm
Guest
howfie wrote:
Quote:
Hi Paul,

Thanks for the info. With pictures like this,
http://www.columbia.edu/acis/history/cell2.jpg,
I guess it's easy to see why it's always a can or a cylinder.
...

Can't recall for sure, but I seem to remember that one addressed a 2321
slightly different than a disk. In addition to the three hex digitis
that identified the whole device, one mentioned cells instead of
cylinders. But it's so long ago now that my memory could be wrong.


One thing for sure, that 'drum' of vertical cells was about one foot in
diameter and the strips of tape which were extracted one at a time were
then 'wound' around a much smaller 'roller' in order to read and write
them. The main rotation was stepped unlike a disk which never stopped,
always rotating at the same speed. Then the cover of a cell would open,
a sever or eight strip of two-inch wide tape would be pulled out and
read. Watching this was like watching one of those perpetual motion
machines but at much faster speed. IBM advertised 'average access time'
of around 400 milli-seconds but this was a marketing number which didn't
include all the potential movements needed for an access 'from scratch'.
The 2321 I was given had about 1500 hours on the clock when I got it,
the university that bought it for about a hundred thousand 1965 dollars
plus a grand or more per month for on-call service gave up on it after
about two years of breakdowns.


Like tape and disk drives of that era, was physicall big and had small
capacity compared to today's devices, about 500 Mbytes if I recall the
capacity. Physically the containing box which included all the motors,
electronics, hydraulic system and reservoir was nearly six feet tall,
three feet wide and six feet long. It weighed something like 1500 pounds.
 
Tony Toews [MVP]...
Posted: Tue Jun 23, 2009 12:20 am
Guest
paul c <toledobythesea at (no spam) oohay.ac> wrote:

Quote:
Looks to me that it's only a matter of time before Solid State Disks
take over.

They already have at some high end server systems. Or for certain portions of the
data such as SQL Server stuff.

Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
Granite Fleet Manager http://www.granitefleet.com/
 
Leif Neland...
Posted: Fri Jun 26, 2009 5:06 pm
Guest
"Walter Mitty" <wamitty at (no spam) verizon.net> skrev i en meddelelse
news:HXK%l.580$NF6.84 at (no spam) nwrddc02.gnilink.net...
Quote:

"howfie" <yadayada at (no spam) yabloo.com> wrote in message
news:Xns9C31ABF92C6E6yadayadayabloocom at (no spam) 216.196.97.131...
Hi Paul,

Thanks for the info. With pictures like this,
http://www.columbia.edu/acis/history/cell2.jpg,
I guess it's easy to see why it's always a can or a cylinder.

Could you discuss a little more about your 'cylinders are virtual'
comment? I'm not really a hardware guy and this question is actually for
a simple introductory relational database course that I teach which
exclusively focuses on 'the query' and SQL. In the first lecture though,
I really like to talk about the history of databases and other little
tidbits of potentially useful (or useless) information.

Thanks!

I'm not sure what "cylinders are virtual" meant. I await Paul's response.

The term "cylinders" does come up repeatedly when discussing stacked disk
platters at the physical level.

When a spindle holds a stack of disk platters, there is one head for each
surface that's actually used. These heads generally move together as a
unit, in what's called a "seek" operation.
Once a seek is done, each head can read/write one track worth of data.
If you put all these tracks together, they make up a "cylinder". This is
the total amount of data that can be read or written before another seek
has to be performed. Typically, the disk unit reads or writes a small
percentage of the cylinder before performing the next seek, but that
depnds on the usage pattern.

When disk geometry is viewed this way, a track can be seen as the
intersection of a cylinder and a surface.

The disks pretend there are x sectors on each y cylinders on each z

surfaces, giving a total of x*y*z sectors.

However, there are more sectors on the outer cylinders than the inner
cylinders, so the disk drive internally calculates what the logical sector
corresponds to in actual sector/cylinder/head.

That's why a disk can appear to have 64 heads. Just so large disks can be
compatible with old bios'es. I believe there is a limit on 1024 cylinders on
some bios or os'es.

Leif
 
George Neuner...
Posted: Sat Jun 27, 2009 12:47 am
Guest
On Fri, 26 Jun 2009 15:06:06 +0200, "Leif Neland" <leif at (no spam) neland.dk>
wrote:

Quote:

"Walter Mitty" <wamitty at (no spam) verizon.net> skrev i en meddelelse
news:HXK%l.580$NF6.84 at (no spam) nwrddc02.gnilink.net...

"howfie" <yadayada at (no spam) yabloo.com> wrote in message
news:Xns9C31ABF92C6E6yadayadayabloocom at (no spam) 216.196.97.131...
Hi Paul,

Thanks for the info. With pictures like this,
http://www.columbia.edu/acis/history/cell2.jpg,
I guess it's easy to see why it's always a can or a cylinder.

Could you discuss a little more about your 'cylinders are virtual'
comment? I'm not really a hardware guy and this question is actually for
a simple introductory relational database course that I teach which
exclusively focuses on 'the query' and SQL. In the first lecture though,
I really like to talk about the history of databases and other little
tidbits of potentially useful (or useless) information.

Thanks!

I'm not sure what "cylinders are virtual" meant. I await Paul's response.

The term "cylinders" does come up repeatedly when discussing stacked disk
platters at the physical level.

When a spindle holds a stack of disk platters, there is one head for each
surface that's actually used. These heads generally move together as a
unit, in what's called a "seek" operation.
Once a seek is done, each head can read/write one track worth of data.
If you put all these tracks together, they make up a "cylinder". This is
the total amount of data that can be read or written before another seek
has to be performed. Typically, the disk unit reads or writes a small
percentage of the cylinder before performing the next seek, but that
depnds on the usage pattern.

When disk geometry is viewed this way, a track can be seen as the
intersection of a cylinder and a surface.

The disks pretend there are x sectors on each y cylinders on each z
surfaces, giving a total of x*y*z sectors.

However, there are more sectors on the outer cylinders than the inner
cylinders, so the disk drive internally calculates what the logical sector
corresponds to in actual sector/cylinder/head.

Modern disks address content by linear block numbers which are
internally converted to surface/track/sector addresses.

Most disk firmware (though not all) still supports the old 16-bit
cylinder/head/sector addressing, but modern systems use it only in
firmware for bootstrapping ... once an OS is loaded, the system is
expected to use the linear block number interface. Most modern 32-bit
systems (Windows, Linux, Unix, etc.) use 64-bit disk block numbering.
Most 64-bit systems also use 64-bit block numbering ... AFAIK, only
ZFS uses 128-bit block numbers.

Quote:
That's why a disk can appear to have 64 heads. Just so large disks can be
compatible with old bios'es. I believe there is a limit on 1024 cylinders on
some bios or os'es.


George
 
 
Page 1 of 2    Goto page 1, 2  Next
All times are GMT
The time now is Tue Dec 08, 2009 6:36 pm