02-14-2014
This sort of a move process should be done when booted in recovery-mode or similar. For AIX, you would boot from mksysb media, for RHEL it's boot thei install media and pick recovery mode etc.
Whatever you do, you need to have the OS in memory only but be able to access this disks. You will need to vary on the volume group and mount the filesystems, probably safest under /mnt.
Only then can you be sure that the filesystems in question are actually idle.
You need to confirm your OS and version before we can assist you much further.
Do you have a recent boot-able backup to recover with at the extreme?
Robin
10 More Discussions You Might Find Interesting
1. Solaris
Hi all,
I have to mount my home directory in one box, by default everyone's home directory will mount in all unix boxes which we have. But we have unmounted these home directories from some boxes to keep the data as safe. So for automation purpose i need my home directory only in those boxes to... (2 Replies)
Discussion started by: raghu.iv85
2 Replies
2. Solaris
Hi All,
:confused:
I had an issue with the USB in Solaris 10 Ultra SParc machine.
I am able to mount the USB in my machine using the mount command.
# mount -F pcfs /dev/dsk/c2t0d0s0:c /mnt
The problem is when i copy a file from my local hard disk to the USB using the " cp -p... (2 Replies)
Discussion started by: spavindla
2 Replies
3. Red Hat
Hi,
While i try to mount the NFS file system on the client linux server i am getting the error message as (4 Replies)
Discussion started by: gsiva
4 Replies
4. UNIX for Advanced & Expert Users
Hi,
Not entirely sure if this is the right thread.
Essentially, fdisk -l shows that /dev/sda is a drive (750 GB), with 1 partition at /dev/sda1 with system type "Linux".
I'm pretty nooby at working with drives, but I'm pretty sure that the output of:
mount /dev/sda1 /media/int
Should not... (4 Replies)
Discussion started by: FreddoT
4 Replies
5. Red Hat
Hi Friends,
My source server is HP and my destination is linux. I have to mount a dir thru nfs from source to destn. almost 8 servers i did the same thing and it is working fine but on the 9th server i can't able to mount.
Everything i have did for nfs configuration.Even i can able to ping... (1 Reply)
Discussion started by: Mohamed Thamim
1 Replies
6. Red Hat
Hi There,
I have following issue:
# df -k
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/hda1 30470144 4200476 24696908 15% /
/dev/hda6 223461396 82243140 129683992 39% /apps
/dev/hda5 10153988 155100 9474772 2%... (3 Replies)
Discussion started by: Sunil Koya
3 Replies
7. UNIX for Dummies Questions & Answers
I format a usb key:
mkfs -t ext4 /dev/sdf1
mkfs -t ext4 /dev/sdf2
(also tried mkfs.ext4 /dev/sdfx and mke2fs -t ext4 /dev/sdfx)
and have the following:
# fdisk -l
Device Boot Start End Blocks Id System
/dev/sdf1 * 64 6097695 3048816 ... (0 Replies)
Discussion started by: arpagon
0 Replies
8. UNIX for Dummies Questions & Answers
I have a virtual machine with Redhat installed .
I am trying to link CD/DVD Drive 1 to /media/cdrom1 and CD/DVD Drive 0 to /media/cdrom0
I tried making these changed in /etc/fstab by adding the below line to it
/dev/sr0 /media/cdrom0 iso9660 user,noauto,exec,utf8 0 0... (2 Replies)
Discussion started by: walterthered
2 Replies
9. Red Hat
we are facing a weird NFS mount issue on one of the linux host , a NFS volume of 2.4TB is mounted in the linux host , but df only reports 131g , which exactly matches rootfilesytem size
nfs mount
filer_filer1:/vol/bug_test/q0
131G 116G 8.5G 94% /nas/bug_test
root... (2 Replies)
Discussion started by: skamal4u
2 Replies
10. Solaris
Hi all
I have a mount issue, that is as follows:
somebody as mount a certain file system /sim5 on /, so when I do df -h /sim5it returns Filesystem size used avail capacity Mounted on
/dev/md/dsk/d10 9.6G 7.0G 2.6G 74% /, which is the same as df -h /... (25 Replies)
Discussion started by: fretagi
25 Replies
LEARN ABOUT CENTOS
systemd-readahead-done.service
SYSTEMD-READAHEAD-REPLAY.SERVICE(8) systemd-readahead-replay.service SYSTEMD-READAHEAD-REPLAY.SERVICE(8)
NAME
systemd-readahead-replay.service, systemd-readahead-collect.service, systemd-readahead-done.service, systemd-readahead-done.timer, systemd-
readahead - Disk read ahead logic
SYNOPSIS
systemd-readahead-replay.service
systemd-readahead-collect.service
systemd-readahead-done.service
systemd-readahead-done.timer
/usr/lib/systemd/systemd-readahead/systemd-readahead [OPTIONS...] COMMAND [DIRECTORY | FILE]
DESCRIPTION
systemd-readahead-collect.service is a service that collects disk usage patterns at boot time. systemd-readahead-replay.service is a
service that replays this access data collected at the subsequent boot. Since disks tend to be magnitudes slower than RAM, this is intended
to improve boot speeds by pre-loading early at boot all data on disk that is known to be read for the complete boot process.
systemd-readahead-done.service is executed a short while after boot completed and signals systemd-readahead-collect.service to end data
collection. On this signal, this service will then sort the collected disk accesses and store information about them in /.readahead.
Normally, both systemd-readahead-collect.service and systemd-readahead-replay.service are activated at boot so that access patterns from
the preceding boot are replayed and new data collected for the subsequent boot. However, on read-only media where the collected data cannot
be stored, it might be a good idea to disable systemd-readahead-collect.service.
On rotating media, when replaying disk accesses at early boot, systemd-readahead-replay.service will order read requests by their location
on disk. On non-rotating media, they will be ordered by their original access timestamp. If the file system supports it,
systemd-readahead-collect.service will also defragment and rearrange files on disk to optimize subsequent boot times.
OPTIONS
systemd-readahead understands the following options:
-h, --help
Prints a short help text and exits.
--max-files=
Maximum number of files to read ahead. Only valid for thes collect command.
--file-size-max=
Maximum size of files in bytes to read ahead. Only valid for the collect and replay commands.
--timeout=
Maximum time in microseconds to spend collecting data. Only valid for the collect command.
COMMANDS
The following commands are understood by systemd-readahead:
collect [DIRECTORY]
Collect read-ahead data on early boot. When terminating, it will write out a pack file to the indicated directory containing the
read-ahead data.
replay [DIRECTORY]
Perform read-ahead on the specified directory tree.
analyze [FILE]
Dumps the content of the read-ahead pack file to the terminal. For each file, the output lists approximately how much will be read
ahead by the replay command.
SEE ALSO
systemd(1)
systemd 208 SYSTEMD-READAHEAD-REPLAY.SERVICE(8)