06-29-2004
Thnaks for your reply,
Perderabo, you stated a SAN server, is this a Unix machine or a special machine? You also stated that the need fiber driver. Is this on all machine that would be accessing the data. Thus if you were accessing from a windows machine you need fiber NIC card and same for Unix side? I'm sorry to be asking soo much, just trying to get things right.
10 More Discussions You Might Find Interesting
1. AIX
hi
We have 2 AIX nodes running with HACMP and all of them connected to SAN,
Our shared storage is shark; I need to create shared volume group and I need the HACMP take a ware of it.
Regards (1 Reply)
Discussion started by: h2aix
1 Replies
2. Solaris
Hi everyone,
I wonder if I can canvas any opinions or thoughts (good or bad) on SAN attaching a SUN V880/490 to an EMC Clarion SAN?
At the moment the 880 is using 12 internal FC-AL disks as a db server and seems to be doing a pretty good job. It is not I/O, CPU or Memory constrained and the... (2 Replies)
Discussion started by: si_linux
2 Replies
3. Solaris
Hi,
How can we differentiate a SAN disk with a Solaris local disk?
Please respond.
Thanks (4 Replies)
Discussion started by: balu_solaris
4 Replies
4. AIX
Dera all
I have error repeating for two day, when I checked the error log by errpt command:
------------------------------------------------------------------------
LABEL: SC_DISK_ERR2
IDENTIFIER: 79B0DF89
Date/Time: Wed Oct 31 02:41:36 SAUS
Sequence Number: 9000... (1 Reply)
Discussion started by: magasem
1 Replies
5. Linux
Hello everyone.
I was wondering if there is a way to increase the size on the LUN on a SAN and make the Linux kernel understand the changes without restarting?
In the past it has always been rebooted to see the new values but im sure that there is a way now for the lvm to see the Free PE in... (8 Replies)
Discussion started by: d_ark
8 Replies
6. UNIX for Dummies Questions & Answers
Hello,
I'm posting this in the "Unix for Dummies" forum, since it is more of a theoretical question than an exact problem/fix I'm inquiring about.
I have a SunFire T2000 server with 4 internal hard drives, running Solaris 10. (So far so good :)
The company just purchased a large EMC SAN. ... (5 Replies)
Discussion started by: FredSmith
5 Replies
7. AIX
Can anyone recommend a good book on san storage basics and how it communicates with an AIX server? (1 Reply)
Discussion started by: NycUnxer
1 Replies
8. AIX
Has anyone tried SAN to SAN mirroring on IBM DS SAN Storage.
DS5020 mentions Enhanced Remote Mirror to multi-LUN applications
I wonder if Oracle High availibility can be setup using Remote Mirror option of SAN ? (1 Reply)
Discussion started by: filosophizer
1 Replies
9. AIX
Hi all,
We are migrating our SAN storage from HSV360 to 3PAR. The system runs aix 6.1 version with HACMP.
Please let me know what are requirements from OS side and how are the data copied to the new disks. (10 Replies)
Discussion started by: ElizabethPJ
10 Replies
10. Filesystems, Disks and Memory
hi! i got a rhel 6.3 host that already have an xfs filesystem mounted from a SAN (let's call it SAN-1) whose size is 9TB.
i will be receiving another SAN (let's call it SAN-2) storage of 15TB size. this new addition is physically on another SAN storage. SAN-1 is on a Pillar storage while the new... (6 Replies)
Discussion started by: rino19ny
6 Replies
LEARN ABOUT X11R4
systemd-machine-id-commit.service
SYSTEMD-MACHINE-ID-COMMIT.SERVICE(8) systemd-machine-id-commit.service SYSTEMD-MACHINE-ID-COMMIT.SERVICE(8)
NAME
systemd-machine-id-commit.service - Commit a transient machine ID to disk
SYNOPSIS
systemd-machine-id-commit.service
DESCRIPTION
systemd-machine-id-commit.service is an early boot service responsible for committing transient /etc/machine-id files to a writable disk
file system. See machine-id(5) for more information about machine IDs.
This service is started after local-fs.target in case /etc/machine-id is a mount point of its own (usually from a memory file system such
as "tmpfs") and /etc is writable. The service will invoke systemd-machine-id-setup --commit, which writes the current transient machine ID
to disk and unmount the /etc/machine-id file in a race-free manner to ensure that file is always valid and accessible for other processes.
See systemd-machine-id-setup(1) for details.
The main use case of this service are systems where /etc/machine-id is read-only and initially not initialized. In this case, the system
manager will generate a transient machine ID file on a memory file system, and mount it over /etc/machine-id, during the early boot phase.
This service is then invoked in a later boot phase, as soon as /etc has been remounted writable and the ID may thus be committed to disk to
make it permanent.
SEE ALSO
systemd(1), systemd-machine-id-setup(1), machine-id(5), systemd-firstboot(1)
systemd 237 SYSTEMD-MACHINE-ID-COMMIT.SERVICE(8)