11-27-2007
lvmkd is the logical volume manager kernel daemon and I would not try to kill it, but I doubt that a kill would succeed. If your disks were mirrored, why did you use dd? The logical volume should have been intact by using the other side of the mirror. When you replaced the disk, lvm had to sync it if it was mirrored and this syncing operation is proabably was is causing your load. One other thing to try is to check for OS patches to LVM. But this does sound like a resync. I think it's lvdisplay that will show you the status of a resync.
8 More Discussions You Might Find Interesting
1. Post Here to Contact Site Administrators and Moderators
The site has gone slow for quite some time...
Can you do somethin abt it (2 Replies)
Discussion started by: DPAI
2 Replies
2. UNIX for Dummies Questions & Answers
Hi,
I have an SCO-Unix server running.
There are some processes (unknown to me) which consume a lot of the system resources. This slows down the server dramatically.
Is there a command or program that monitors what processes are using the cpu, disk, etc.. and tell me how excessive and how... (3 Replies)
Discussion started by: Hansaplast
3 Replies
3. Red Hat
Hi All,
I'm new here.
i was wondering if anyone could shed a light on the problem i am having.
I use a system for distributing broadband amongst users of for example a hotel, the system was designed by someone in the US and it is based on redhat 2.4 (i know its old) and the system uses... (3 Replies)
Discussion started by: clive306
3 Replies
4. Solaris
Hello All,
I have noticed that one of my servers, the busiest has become increasingly slow to respond and execute commands, the running applications appear to be fine though.
Here is some output from vmstat :-
kthr memory page disk faults cpu
r b... (5 Replies)
Discussion started by: Wez
5 Replies
5. UNIX for Advanced & Expert Users
Friends
Greetings. I have a RedHat 5.7 64bit virtual server on VMware ESXi 4.1. This server and other Redhat Servers are running very slow. I did some stats collection on ESXi and looks like Linux is holding the disk IO. I am not sure what is causing this behavior.
On Linux I checked the CPU... (4 Replies)
Discussion started by: sdewal
4 Replies
6. Red Hat
My code
Hi All,
I am having redhat linux 5.3 (Tikanga) with GFS file system and its very very slow for executing ls -ls command also.Please see the below for 2minits 12 second takes.
Please help me to fix the issue.
$ sudo time ls -la BadFiles |wc -l
0.01user 0.26system... (3 Replies)
Discussion started by: susindram
3 Replies
7. UNIX for Dummies Questions & Answers
Hi, what would be the first things to check on a system that normally works fine, and is not so fine this morning ? Its accessing menus and various other screens 100x slower than normal.
Version: UnixWare 5 7.1.3 i386 SCO UNIX_SVR5
I have tried this pf -ef|grep paulc and found a huge list of... (6 Replies)
Discussion started by: Mick_Dundee
6 Replies
8. AIX
Hello All,
I am trying to clone an entire AIX virtual machine to a new virtual machine including all partitions and OS.Can anyone help me on the procedure to follow? I am not really sure on how it can be done.Thanks in advance.
Please use CODE tags for sample input, sample output, and for code... (4 Replies)
Discussion started by: gull05
4 Replies
LEARN ABOUT DEBIAN
diskseekd
diskseekd(1) General Commands Manual diskseekd(1)
Name
diskseek, diskseekd - disk seek daemon; simulates Messy Dos' drive cleaning effect
Note
This manpage has been automatically generated from fdutils's texinfo documentation. However, this process is only approximative, and some
items, such as cross-references, footnotes and indices are lost in this translation process. Indeed, these items have no appropriate rep-
resentation in the manpage format. Moreover, only the items specific to each command have been translated, and the general information
about fdutils has been dropped in the manpage version. Thus I strongly advise you to use the original texinfo doc.
* To generate a printable copy from the texinfo doc, run the following commands:
./configure; make dvi; dvips fdutils.dvi
* To generate a HTML copy, run:
./configure; make html
A pre-made HTML can be found at: `http://www.tux.org/pub/knaff/fdutils'
* To generate an info copy (browsable using emacs' info mode), run:
./configure; make info
The texinfo doc looks most pretty when printed or as HTML. Indeed, in the info version certain examples are difficult to read due to the
quoting conventions used in info.
Description
Several people have noticed that Linux has a bad tendency of killing floppy drives. These failures remained completely mysterious, until
somebody noticed that they were due to huge layers of dust accumulating in the floppy drives. This cannot happen under Messy Dos, because
this excuse for an operating system is so unstable that it crashes roughly every 20 minutes (actually less if you are running Windows).
When rebooting, the BIOS seeks the drive, and by doing this, it shakes the dust out of the drive mechanism. diskseekd simulates this effect
by seeking the drive periodically. If it is called as diskseek, the drive is sought only once.
Options
The syntax for diskseekd is as follows:
diskseekd [-d drive] [-i interval] [-p pidfile]
-d drive
Selects the drive to seek. By default, drive 0 (`/dev/fd0') is sought.
-i interval
Selects the cleaning interval, in seconds. If the interval is 0, a single seek is done. This is useful when calling diskseek from a
crontab. The default is 1000 seconds (about 16 minutes) for diskseekd and 0 for diskseek.
-p pidfile
Stores the process id of the diskseekd daemon into pidfile instead of the default `/var/run/diskseekd.pid'.
Bugs
1. Other aspects of Messy Dos' flakiness are not simulated.
2. This section lacks a few smileys.
See Also
Fdutils' texinfo doc
fdutils-5.5 03Mar05 diskseekd(1)