Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
Tommi Makitalo noted that SCO OpenServer limits a disk to 7 slices, capping raw-device disk size around 14GB, as a reason to use cooked devices. Gary Quiring replied that fdisk allows 4 partitions with 7 slices each, and RAID controllers add logical drives. Asked about naming, Gary gave device names /dev/hd01 to hd04 for the first disk and hd11 to hd14 for the second.
Auto-generated by Claude from the posts below — may be imperfect; read the full thread.
Tommi M�kitalo — — source: Informix-list mailing list archive (1991-1998)
>
> But you see, there IS no cost and much benefit. The only benefit to using
> COOKED filesystem
> files (as opposed to COOKED devices which have NO benefit over RAW devices)
> is that they
> are a bit easier to administer, but not by much and you are always at risk
> of some overzealous
> operator or sysadmin deleting that HUGE file to make some space (if you
> think this unlikely just
> poll this newsgroup to see how many of us that has happened to).
There is one more reason to use cooked devices. We use Informix
on SCO OpenServer. OpenServer limits the number of slices on one disk
to 7. So maximum disksize for rawdevices is 14GB (7 * max size of chunk).
Of course more small disks are faster than one large. But I just wanted
to mention that.
Tommi Mäkitalo
Dr. Eckhardt + Partner GmbH
↪ replying to Tommi M�kitalo
Gary Quiring — — source: Informix-list mailing list archive (1991-1998)
On Fri, 28 Jan 2000 00:31:08 +0100, tommi@epgmbh.de (Tommi Mäkitalo) wrote:
>There is one more reason to use cooked devices. We use Informix
>on SCO OpenServer. OpenServer limits the number of slices on one disk
>to 7. So maximum disksize for rawdevices is 14GB (7 * max size of chunk).
>
>Of course more small disks are faster than one large. But I just wanted
>to mention that.
>
But you can fdisk the drive for 4 partitions, each having 7 per partition
to allow 28 chunks per physical drive. Add to that a raid controller, most
allow many logical partitions. I'm using MegaRaid with 4 logical drives,
each logical is broken down in 4 partitions and then another 7. More than
enough chunks.
Gary Quiring
↪ replying to Gary Quiring
Tommi M�kitalo — — source: Informix-list mailing list archive (1991-1998)
>
> But you can fdisk the drive for 4 partitions, each having 7 per partition
> to allow 28 chunks per physical drive. Add to that a raid controller, most
> allow many logical partitions. I'm using MegaRaid with 4 logical drives,
> each logical is broken down in 4 partitions and then another 7. More than
> enough chunks.
>
> Gary Quiring
>
Thanks for your reply.
It slips a little off-topic, but I would like to now how the partitions are
named. Which device do you use to maintain (divvy) the 2nd, 3rd and 4th
partition in OpenServer?
Tommi Mäkitalo
Dr. Eckhardt + Partner GmbH
↪ replying to Tommi M�kitalo
Gary Quiring — — source: Informix-list mailing list archive (1991-1998)
On Mon, 31 Jan 2000 11:27:15 +0100, tommi@epgmbh.de (Tommi Mäkitalo)
wrote:
>> But you can fdisk the drive for 4 partitions, each having 7 per partition
>> to allow 28 chunks per physical drive. Add to that a raid controller, most
>> allow many logical partitions. I'm using MegaRaid with 4 logical drives,
>> each logical is broken down in 4 partitions and then another 7. More than
>> enough chunks.
>It slips a little off-topic, but I would like to now how the partitions are
>named. Which device do you use to maintain (divvy) the 2nd, 3rd and 4th
>partition in OpenServer?
>
/dev/hd01 hd02 hd03 hd04 First Disk
/dev/hd11 hd12 hd13 hd14 Second Disk
And so on.
Gary Quiring
Your privacy choices
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.