Re: D3 Linux vs. D3 Windows
- From: "ddspell-m3" <ddspell@xxxxxxxxx>
- Date: 11 Jul 2006 09:03:35 -0700
Thanks, but I believe there is some unused (unallocated) disk space in
the current configuration.
# df -k
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/sda6 8064272 2632372 5022248 35% /
/dev/sda2 46668 3868 40391 9% /boot
/dev/sda5 7060276 6305364 396264 95% /u
This is everything that is in use. I don't know how to tell about
unused space.
# fdisk -l
Disk /dev/sda: 255 heads, 63 sectors, 8841 cylinders
Units = cylinders of 16065 * 512 bytes
Device Boot Start End Blocks Id System
/dev/sda1 1 4 32098+ de Dell Utility
/dev/sda2 * 5 10 48195 83 Linux
/dev/sda3 11 8841 70935007+ 5 Extended
/dev/sda5 11 903 7172991 83 Linux
/dev/sda6 904 1923 8193118+ 83 Linux
/dev/sda7 1924 2178 2048256 82 Linux swap
/dev/sda8 2179 3326 9221278+ d3 Unknown
If I understand this correctly, I have 7 partitions defined. I think I
have 3 hard drives in a RAID 5 configuration. Each drive is 36 GB, so
that gives a total usuable space of 72 GB, right?
Glen B wrote:
"ddspell-m3" <ddspell@xxxxxxxxx> wrote in message
news:1152628703.276823.50150@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Ross,
1. Standardizing on one O/S.
2. Reduce or eliminate the need for multi-platform training.
3. To gain confidence that the system is under control.
For instance, right now I need to expand the size of the D3 file system
(database?) which will require me to use a utility that I have very
little experience. I believe the command in Linux is divvy, but it was
been about 3 years since I did it last. My uneasiness is that if I
screw it up, I don't know if I can recover. I have backups, but I've
never done a restore from scratch. I guess I should just grab a
machine and throw Linux on it and try a restore, but the problem with
this is that I don't have a macine with an identical configuration. I
guess this points out the need to buy two servers, albeit with less
disk and redundancy for the second one, when one buys a new server so
that a suitable test environment exists.
Install an additional drive, create a partition and mark it as type "d3"
using fdisk. Then, add another disk statement to the pick0 file. Shutdown
D3, reload, and *poof* you have more storage. You don't need to reload D3 or
perform any kind of Linux magical madness. An easier way would be to re-run
the D3_Setup application that should still be on your box. Go into the disk
menu and add an existing parition. You should shut D3 down before you do
that, though. If you want help doing the manual edit, post your current
/usr/lib/pick/pick0 here and the size of the drive you want to add.
I would hire a D3 expert, but I don't know where to find one locally
(Dallas, TX).
So you see, if I was on Windows, I don't think my concerns above would
be an issue.
Regards,
Danny
Glen
.
- Follow-Ups:
- Re: D3 Linux vs. D3 Windows
- From: Glen B
- Re: D3 Linux vs. D3 Windows
- References:
- D3 Linux vs. D3 Windows
- From: ddspell-m3
- Re: D3 Linux vs. D3 Windows
- From: Ross Ferris
- Re: D3 Linux vs. D3 Windows
- From: ddspell-m3
- Re: D3 Linux vs. D3 Windows
- From: Glen B
- D3 Linux vs. D3 Windows
- Prev by Date: Re: Selecting Multivalues
- Next by Date: Re: D3 Linux vs. D3 Windows
- Previous by thread: Re: D3 Linux vs. D3 Windows
- Next by thread: Re: D3 Linux vs. D3 Windows
- Index(es):
Relevant Pages
|