21 Jun
2015
21 Jun
'15
5:43 p.m.
Hi there!
Anyone remember much about Tru64 + LSM? It's been a while since I've done much
with Tru64, and I never used LSM before.
I got some new 36GB disks and am doing a fresh install, and wanted to mirror them with
LSM, as the SCSI controller is not a RAID card.
Initially, the installer picked really stupid defaults, choosing to use only about 3GB
of the 36GB available. I was hoping to do something like have the LSM be in total control
of the disk, with all filesystems and swap being on LSM volumes. The LSM documentation
says this would be called a "sliced" disk. I'm a little rusty on my
disklabel specifics, but the Tru64 docs seem to suggest that the 'a' slice is
usually used for the / filesystem, 'c' is the whole disk, and g or h is usually
used for the LSM private data.
So, my questions are:
1. Is it possible to install to and boot from an LSM sliced disk (as opposed to an LSM
"simple" disk)?
2. Is it possible to have swap be on an LSM volume, or does it have to be on a slice
(like dsk0b or something)
3. Is the 'a' slice strictly required for anything?
4. Would the best (or a good) way to go be to do something like a & b unused, c
whole disk, g all the space except 2MB, and h 2MB for LSM data?
Thanks and sorry for the stupid questions!
-Ben
22 Jun
22 Jun
9:44 a.m.
I wish I could help you with that but I can't.
But I can talk about partitions, if you are using the advanced file system
then none of the partition rules apply, if you are using the ufs then
the traditional layout is this:
a - boot partition, mounted as /
unlike linux, there is generally no /boot partition
b - swap partition
c - the entire disk
d to g - partitions for other stuff like /var /usr /tmp etc.
I have a pair of Alphaservers running Tru64 Unix in a cluster and it boots
from a raid set delivered by a RA8000 SAN and three
Alphaservers who boot
off local storage using a mirror set delivered by a KZPSC
(DAC960) or one
of its various similar siblings. In all cases the file system is Advfs
which looks a lot like the LSM with volume groups and logical volumes etc.
Here is a df of the system partitions from one of the systems:
Filesystem 512-blocks Used Available Capacity Mounted on
root_domain#root 2097152 327726 1748880 16% /
usr_domain#usr 8388608 3829826 4517680 46% /usr
var_domain#var 8388608 715100 7579952 9% /var
local_domain#local 16146432 8941490 6955808 57% /usr/local
As with you, it has been a long time since I looked closely at any of this.
I didn't understand the difference until I started looking at the
configuration when I went to answer your question. We haven't used the LSM
in years.
--
Richard Loken VE6BSV, Unix System Administrator : "Anybody can be a father
Athabasca University : but you have to earn
Athabasca, Alberta Canada : the title of 'daddy'"
** richardlo at admin.athabascau.ca ** : - Lynn Johnston
10:54 a.m.
Hi there!
Thanks for the reply!
I'm using AdvFS. You just mean that the partitions don't actually have to
conform to any specific convention, right? The AdvFs domains still get defined on disk
partitions, if you look at the symlinks in /etc/fdmns/<domain_name>.
You can put a symlink to a LSM volume in there too, but the problem I'm running
into is that the installer (text-based, because I don't have a graphics card) is
fairly insistent upon applying a disklabel that it calculates as barely sufficient to hold
the stuff you're trying to install, and wants to use 'a' for boot, 'b'
for swap, 'd' for the LSM private partition, and so on and so forth. I'll
probably have to resort to setting it up without LSM, then encapsulating it, but again
that wouldn't lead to a "sliced" LSM disk. (I think)
Might you be so kind as to show the ls -la from your /etc/fdmns/*/, and the disklabel
-r dskX from the disks?
The documentation suggests that come extra flexibility could be gained by doing a
graphical install.
Thanks!
-Ben
________________________________________
From: cctalk [cctalk-bounces at classiccmp.org] on behalf of Richard Loken [richardlo at
admin.athabascau.ca]
Sent: Monday, June 22, 2015 9:44 AM
To: General Discussion: On-Topic and Off-Topic Posts
Subject: Re: Tru64 LSM
I wish I could help you with that but I can't.
But I can talk about partitions, if you are using the advanced file system
then none of the partition rules apply, if you are using the ufs then
the traditional layout is this:
a - boot partition, mounted as /
unlike linux, there is generally no /boot partition
b - swap partition
c - the entire disk
d to g - partitions for other stuff like /var /usr /tmp etc.
I have a pair of Alphaservers running Tru64 Unix in a cluster and it boots
from a raid set delivered by a RA8000 SAN and three
Alphaservers who boot
off local storage using a mirror set delivered by a KZPSC
(DAC960) or one
of its various similar siblings. In all cases the file system is Advfs
which looks a lot like the LSM with volume groups and logical volumes etc.
Here is a df of the system partitions from one of the systems:
Filesystem 512-blocks Used Available Capacity Mounted on
root_domain#root 2097152 327726 1748880 16% /
usr_domain#usr 8388608 3829826 4517680 46% /usr
var_domain#var 8388608 715100 7579952 9% /var
local_domain#local 16146432 8941490 6955808 57% /usr/local
As with you, it has been a long time since I looked closely at any of this.
I didn't understand the difference until I started looking at the
configuration when I went to answer your question. We haven't used the LSM
in years.
--
Richard Loken VE6BSV, Unix System Administrator : "Anybody can be a father
Athabasca University : but you have to earn
Athabasca, Alberta Canada : the title of 'daddy'"
** richardlo at admin.athabascau.ca ** : - Lynn Johnston
12:20 p.m.
On Mon, 22 Jun 2015, Benjamin Huntsman wrote:
I'm using AdvFS. You just mean that the
partitions don't actually have
to conform to any specific convention, right? The AdvFs domains still get
defined on disk partitions, if you look at the symlinks in
/etc/fdmns/<domain_name>.
Now I'm embarrassed! Yes, it just means I don't know what I am talking
about. So, on a machine with a local disk, disklabel says this:
a: 2097153 0 AdvFS
b: 524287 2097153 swap
c: 35545088 0 unused 1024 8192
d: 11324074 1572864 unused 1024 8192
e: 8388608 11010048 AdvFS
f: 16146432 19398656 AdvFS
g: 8388608 2621440 AdvFS
h: 29671424 5873664 unused 1024 8192
and /etc/fdmns says this:
drwxr-xr-x 2 root system 8192 Feb 24 2003 local_domain/
drwxr-xr-x 2 root system 8192 Feb 24 2003 root_domain/
drwxr-xr-x 2 root system 8192 Feb 24 2003 usr_domain/
drwxr-xr-x 2 root system 8192 Feb 24 2003 var_domain/
And in turn:
root_domain: dsk0a@ -> /dev/disk/dsk0a
usr_domain: dsk0e@ -> /dev/disk/dsk0e
var_domain: dsk0g@ -> /dev/disk/dsk0g
local_domain: dsk0f@ -> /dev/disk/dsk0f
So it is indeed partitioned with disklabel and / is indeed on dsk0a:
You can put a symlink to a LSM volume in there too,
but the problem I'm
running into is that the installer (text-based, because I don't have a
graphics card) is fairly insistent upon applying a disklabel that it
calculates as barely sufficient to hold the stuff you're trying to
install, and wants to use 'a' for boot, 'b' for swap, 'd' for the
LSM
private partition, and so on and so forth. I'll probably have to resort
to setting it up without LSM, then encapsulating it, but again that
wouldn't lead to a "sliced" LSM disk. (I think)
I started to read the LSM manual just now but gave it up as a lot of work
that I sould not be doing on company time.
Might you be so kind as to show the ls -la from
your /etc/fdmns/*/, and
the disklabel -r dskX from the disks?
See attached.
--
Richard Loken VE6BSV, Unix System Administrator : "Anybody can be a father
Athabasca University : but you have to earn
Athabasca, Alberta Canada : the title of 'daddy'"
** richardlo at admin.athabascau.ca ** : - Lynn Johnston
3471
days inactive
3471
days old
3 comments
2 participants
participants (2)
-
BHuntsman＠mail2.cu-portland.edu -
richardlo＠admin.athabascau.ca