05-15-2009
what is your ultimate goal for this disk. Do you care about the data on the disk? If so, have you thought about doing a vgchange and vgscan? It might even be better to, if you can, use the original machine to export the vg information and then import it on the other machine
9 More Discussions You Might Find Interesting
1. Linux
Hi all,
I have a server running in RH ES4, the SCSI HD are running in RAID 1.
I backup the LVM config by using 'vgcfgbackup' and then remove all the HD.
I insert another HD (same size & branch but different model) into the machine and run linux rescue to recreate the... (0 Replies)
Discussion started by: donaldfung
0 Replies
2. UNIX for Advanced & Expert Users
Hello,
I have logical volume group of 50GB, in which I have 2 logical volumes, LogVol01 and LogVol02, both are of 10GB.
If I extend LogVol01 further by 10GB, then it keeps the extended copy after logical volume 2. I want to know where it keeps this information
Regards
Himanshu (3 Replies)
Discussion started by: ghimanshu
3 Replies
3. Solaris
Hi all,
I have a problem with vxvm volume which is mirror with two disks. when i am try to increase file system, it is throwing an ERROR: can not allocate 5083938 blocks, ERROR: can not able to run vxassist on this volume.
Please find a sutable solutions.
Thanks and Regards
B. Nageswar... (0 Replies)
Discussion started by: nageswarb
0 Replies
4. SuSE
Hi,
I have following set up on Open suse 11
vgdisplay
pvdisplay
lvdisplay
I would like to remove these disks /dev/sdb and /dev/sdc from LVM and do not use them for anything..
Can anyone please help me with this ? (1 Reply)
Discussion started by: upengan78
1 Replies
5. Solaris
Can somebody kindly help me to determine which one i should choose to better manipulate OS volume.
RAID manager or veritas volume manager?
Any critical differences between those two?
Thanks in advance. (5 Replies)
Discussion started by: beginningDBA
5 Replies
6. UNIX for Dummies Questions & Answers
I have a machine (5.10 Generic_142900-03 sun4u sparc SUNW,Sun-Fire-V210) that we are upgrading the storage and my task is to mirror what is already on the machine to the new disk. I have the disk, it is labeled and ready but I am not sure of the next steps to mirror the existing diskgroup and... (1 Reply)
Discussion started by: rookieuxixsa
1 Replies
7. Red Hat
I wanted to know how we can combine volumes over 2 physical drives.
# fdisk -l
Disk /dev/sda: 42.9 GB, 42949672960 bytes
255 heads, 63 sectors/track, 5221 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sda1 ... (16 Replies)
Discussion started by: ikn3
16 Replies
8. Red Hat
Hello friends,
We had to upgrade RHEL 4.x to 5.7 so we took complete backup. Since DIRECT UPGRADE not possible, we rebuilt 5.7 from scratch.
We had lvm configuration on DATA disks in previous OS and now we need to configure such that we should be able to have same old LVM configuration (like... (1 Reply)
Discussion started by: prvnrk
1 Replies
9. Solaris
Hi
I have created a new setup for VCS for doing some testing on virtual box. After creating 3 Solaris 10 machine (147148-26) with VCS. Here I have used one machine as ISCSI Storage.
VCS Version is
bash-3.2# /opt/VRTS/bin/haclus -value EngineVersion
6.0.10.0
bash-3.2#
bash-3.2# pkginfo... (4 Replies)
Discussion started by: hb00
4 Replies
LEARN ABOUT MINIX
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)