06-26-2007
if you have a 2nd disk you can use liveupgrade (man lu) to build a new disk (online) with the needed setup. afterwards you only need a downtime to reboot the machine with the new disk.
8 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
How do I create new disk slices taking space from an existing slice? Right now I have slice 6 (/usr) with 16G. I'd like to create slices 5 (/opt) and 7 (/export/home) and steal space from slice 6.
Thanks (3 Replies)
Discussion started by: kmgrady01
3 Replies
2. Solaris
Hi all,
we have an existing system that was configured using just one of the (two) internal disks. I want to mirror the disk using SVM, but have realised there is no free slice for creating the metadb's. Is there a workaround I can use for this?
In the past we have always kept slice 7 free -... (8 Replies)
Discussion started by: badoshi
8 Replies
3. SuSE
Hello Experts,
I am very new to unix environment.
Root filesystem in one of our Linux boxes has almost reached 100%. is there a procedure/ way to resize the root filesystem.
******************************************************
ld8331:/ # df -h|more
Filesystem Size Used... (2 Replies)
Discussion started by: ashok1784
2 Replies
4. Solaris
Hi all
I'm having difficulty setting up a proper disk structure on a 72GB HDD. The drive was previously part of a zfs pool. The zpool has ben destroyed and now I want to use the disk in a raid 5 array. I need to partition the disk accordingly though.
This is what the partition table currently... (7 Replies)
Discussion started by: notreallyhere
7 Replies
5. Red Hat
Hi Team,
Require your expertise on how to resize / partition.
This is VM.
Thank you.
Reggy
# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda2 15G 13G 556M 96% /
/dev/sda1 965M 43M 873M 5% /boot
tmpfs 502M 0 ... (5 Replies)
Discussion started by: regmaster
5 Replies
6. Solaris
I am trying to resize my disk space to be bigger on my solaris server (Sun Fire V240)
this server and other windows servers are attached to a SAN disks, the disk I want to resize is on the SAN.
I have free space on the SAN disks so I added some space to the windows disks and I made some... (8 Replies)
Discussion started by: sofihdi
8 Replies
7. Red Hat
Hi,
I'm running a Red Hat Enterprise Linux Server release 5.3 (Tikanga) on VMWare. It is a production system for which I may not get downtime soon. I happened to resize a underlying disk and the changes are not reflecting in the fdisk ouput. Further details are as follows.
The disk which i... (3 Replies)
Discussion started by: maverick_here
3 Replies
8. SCO
I have SCO Openserver 5.0.5
Root partition is 96% full and I would like to make it bigger. How can this be done?
1) Can I use 'dd' to backup 'root' and then backup '/u' to a third hard disk, then divvy the primary hard disk to have a larger 'root' filesystem (i.e. previous root + u)
2) ... (5 Replies)
Discussion started by: grips03
5 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)