Strang iostat numbers
by Carlos H. Reimer
Hi,
We have a bad performance issue in one of our database servers and I´ve
discovered very iostat strange numbers .
The server is showing up normally 100.00% disk utilization but this morning
I´ve shutted down the database and the iostat was still showing 100.00
%util.
What can explain this behaviour?
iostat -x
avg-cpu: %user %nice %system %iowait %idle
0.00 0.00 0.00 0.00 100.00
Device: rrqm/s wrqm/s r/s w/s rsec/s wsec/s rkB/s wkB/s
avgrq-sz avgqu-sz await svctm %util
sda 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00
0.00 451876.46 0.00 0.00 100.00
sdb 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00
0.00 451876.46 0.00 0.00 100.00
md1 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00
0.00 0.00 0.00 0.00 0.00
md0 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00
0.00 0.00 0.00 0.00 0.00
avg-cpu: %user %nice %system %iowait %idle
0.00 0.00 0.00 0.00 100.00
Device: rrqm/s wrqm/s r/s w/s rsec/s wsec/s rkB/s wkB/s
avgrq-sz avgqu-sz await svctm %util
sda 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00
0.00 451876.46 0.00 0.00 100.00
sdb 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00
0.00 451876.46 0.00 0.00 100.00
md1 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00
0.00 0.00 0.00 0.00 0.00
md0 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00
0.00 0.00 0.00 0.00 0.00
Reimer
17 years, 6 months
alsa 1.0.13 yum package?
by Charles Tuckey
Does anyone know when fedora will be releasing the alsa 1.0.13
packages? I need them to fix headphone problems with my Intel HC7
sound system. I have checked the fedora-core, fedora-extras and livna
but with no success.
--
Regards,
Charlie
17 years, 6 months
dbus dependencies problem
by Paul Smith
Dear All
I am having the following dependencies problem:
Resolving Dependencies
--> Populating transaction set with selected packages. Please wait.
---> Package dbus-x11.i386 0:1.0.1-2.fc6 set to be updated
---> Package dbus.i386 0:1.0.1-2.fc6 set to be updated
---> Package dbus-devel.i386 0:1.0.1-2.fc6 set to be updated
--> Running transaction check
--> Processing Dependency: dbus = 0.61 for package: dbus-qt
--> Finished Dependency Resolution
Error: Missing Dependency: dbus = 0.61 is needed by package dbus-qt
Any ideas?
Thanks in advance,
Paul
17 years, 6 months
FC5, MDADM and a raid recovery
by mjwestkamper
I built a softraid using mdadm some time ago. It used 4 250GB SATA drives.
All worked fine. Its loaded about 55% and runs 24x7.
I started to upgrade to FC6. Rather than leaving things as they were the
installer didn't recognize the RAID configuration and did something to
the first drive /dev/sda. I killed the install and rebooted FC5. It
booted correctly, however the RAID was apparently tampered with.
Thinking I should be able to recover I tried several cautious paths,
however to no avail. Here is a sequence that should help someone
schooled in the file systems. ANY suggestions will be greatly appreciated.
Mike
/[root@homeserver ~]# mdadm -Afv /dev/md0
mdadm: looking for devices for /dev/md0
mdadm: /dev/sde2 is not one of /dev/sda,/dev/sdb,/dev/sdc,/dev/sdd
mdadm: /dev/sde1 is not one of /dev/sda,/dev/sdb,/dev/sdc,/dev/sdd
mdadm: /dev/sde is not one of /dev/sda,/dev/sdb,/dev/sdc,/dev/sdd
mdadm: /dev/sdd1 is not one of /dev/sda,/dev/sdb,/dev/sdc,/dev/sdd
mdadm: /dev/sdd is identified as a member of /dev/md0, slot 4.
mdadm: /dev/sdc is identified as a member of /dev/md0, slot 2.
mdadm: /dev/sdb is identified as a member of /dev/md0, slot 1.
mdadm: /dev/sda is identified as a member of /dev/md0, slot 0.
mdadm: /dev/hdb1 is not one of /dev/sda,/dev/sdb,/dev/sdc,/dev/sdd
mdadm: /dev/hdb is not one of /dev/sda,/dev/sdb,/dev/sdc,/dev/sdd
mdadm: /dev/hda3 is not one of /dev/sda,/dev/sdb,/dev/sdc,/dev/sdd
mdadm: /dev/hda2 is not one of /dev/sda,/dev/sdb,/dev/sdc,/dev/sdd
mdadm: /dev/hda1 is not one of /dev/sda,/dev/sdb,/dev/sdc,/dev/sdd
mdadm: /dev/hda is not one of /dev/sda,/dev/sdb,/dev/sdc,/dev/sdd
mdadm: clearing FAULTY flag for device 0 in /dev/md0 for /dev/sdd
mdadm: added /dev/sdb to /dev/md0 as 1
mdadm: added /dev/sdc to /dev/md0 as 2
mdadm: no uptodate device for slot 3 of /dev/md0
mdadm: added /dev/sdd to /dev/md0 as 4
mdadm: added /dev/sda to /dev/md0 as 0
mdadm: /dev/md0 has been started with 3 drives (out of 4) and 1 spare.
[root@homeserver ~]# mount /dev/md0 /filestore
mount: wrong fs type, bad option, bad superblock on /dev/md0,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so /
17 years, 6 months
RE: How to encrypt and burn to dvdr my home dir?
by Christian Burger
>Robin Laing wrote:
>>
>> What about truecrypt?
>>
>> http://www.truecrypt.org/
>>
>> If I was making a backup, I would tar and encrypt as explained before
>> and then RAR the files to make the files sizes easier to deal with.
>>
>> Just a thought.
>
>After encryption, it isn't going to compress.
>
>Mike
Nope not much if any... but rar will chunk it into 650 meg or whatever size
chunks that are desired....
17 years, 6 months
fc6: won't display remote program locally
by Mike Wright
Hi all,
I've been using the command "ssh -Y remotebox" to provide a local X
session for administering remote boxes and it used to work well. I have
an id_dsa.pub key on the remote boxes and the login is almost instant.
Where the problem arises is when I try to run firefox or thunderbird on
the remote box that will display here. Lots of blinking lights on the
nic, and 70 seconds later I'm back at the prompt looking at "Done".
But, other things suchas gedit display locally correctly.
This works on my fc4 boxes, but on neither fc6 box. One is running
linux-2.6.18-1.2798.fc6xen and the other linux-2.6.18.2 vanilla. None
are running selinux. In all other regards the machines seem to work
similarly.
Has anybody else experienced this? If so, did you get it to work?
google and yahoo haven't been much help on this one.
Thanks,
Mike Wright
17 years, 6 months
SCSI drives
by Carlos H. Reimer
Hi,
I' trying to compare two Linux servers in the SCSI i/o subsystem features.
What I´m looking for:
. Disk and controller features?
. How much cache do the disks or cotroller have?
. Speek disk rotation?
. Is write back enabled?
. and others features
Where can I find those information in Linux ?
Thank you in advance!
Reimer
17 years, 6 months
FC6: Shift changes keysym of LeftAlt
by Pavel Lisy
Hello
I have long standing problem. Keyboard shortcuts depends on keypress
order.
When I press
LeftAlt-LeftShift-x shortcut is working
When I press
LeftShift-LeftAlt-x shortcut doesn't working
I have tryied make some research on it. Problem is in combination Shift
and Alt (Control-Shift, Control-Alt works always the same way)
LeftAlt returns this in 1. case
state 0x10, keysym 0xffe9, Alt_L (in xev)
<Shift><Alt>x (in gnome-keybinding-properties)
LeftAlt returns this in 2. case
state 0x11, keysym 0xffe7, Meta_L (in xev)
<Shift><Alt><Mod5>x (in gnome-keybinding-properties)
Is it normal?
It could be problem of what? (xorg-x11-drv-keyboard, metacity, ...)
Can I solve it somehow?
Is it error? Need I report it in bugzilla?
Detailed output from xev:
keypress order
1. LeftAlt down
2. LeftShift down
3. LeftShift up
4. LeftAlt up
returns this in "xev"
KeyPress event, serial 26, synthetic NO, window 0x4600001,
root 0x4d, subw 0x0, time 1371487573, (895,554), root:(897,617),
state 0x10, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
KeyPress event, serial 29, synthetic NO, window 0x4600001,
root 0x4d, subw 0x0, time 1371488661, (895,554), root:(897,617),
state 0x18, keycode 50 (keysym 0xffe1, Shift_L), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
KeyRelease event, serial 29, synthetic NO, window 0x4600001,
root 0x4d, subw 0x0, time 1371489149, (895,554), root:(897,617),
state 0x19, keycode 50 (keysym 0xfe0a, ISO_Prev_Group), same_screen
YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
KeyRelease event, serial 29, synthetic NO, window 0x4600001,
root 0x4d, subw 0x0, time 1371489757, (895,554), root:(897,617),
state 0x18, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
keypress order
1. LeftShift down
2. LeftAlt down
3. LeftAlt up
4. LeftShift up
returns this in "xev"
KeyPress event, serial 29, synthetic NO, window 0x4600001,
root 0x4d, subw 0x0, time 1371495099, (894,554), root:(896,617),
state 0x10, keycode 50 (keysym 0xffe1, Shift_L), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
KeyPress event, serial 29, synthetic NO, window 0x4600001,
root 0x4d, subw 0x0, time 1371495883, (894,554), root:(896,617),
state 0x11, keycode 64 (keysym 0xffe7, Meta_L), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
KeyRelease event, serial 29, synthetic NO, window 0x4600001,
root 0x4d, subw 0x0, time 1371496555, (894,554), root:(896,617),
state 0x99, keycode 64 (keysym 0xffe7, Meta_L), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
KeyRelease event, serial 29, synthetic NO, window 0x4600001,
root 0x4d, subw 0x0, time 1371497059, (894,554), root:(896,617),
state 0x11, keycode 50 (keysym 0xfe0a, ISO_Prev_Group), same_screen
YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
17 years, 6 months
udev device-persistence problem
by Terry Horsnell
FC6 - kernel 2.6.18-1.2798.fc6 - udev-095-14
I'm trying to develop some rules to give me device-name
persistence on my SCSI disks. I have a couple of test rules:
BUS=="scsi", PROGRAM="/sbin/scsi_id -g -u"
RESULT=="20004cffffe0e0976", NAME="dsk0_%n", OWNER="root", GROUP="root", MODE="0700"
RESULT=="SSEAGATE_ST336807LC_3KT0CTTM00007530YTR2", NAME="dsk1_%n", OWNER="root", GROUP="root", MODE="0700"
With these rules disabled, I get:
[root@dev1 ~]# ls -l /dev/dsk* /dev/sd* /dev/sg*
brwx------ 1 root disk 8, 0 Nov 28 11:48 /dev/sda
brwx------ 1 root disk 8, 1 Nov 28 11:48 /dev/sda1
brwx------ 1 root disk 8, 16 Nov 28 11:48 /dev/sdb
brwx------ 1 root disk 8, 17 Nov 28 11:48 /dev/sdb1
brwx------ 1 root disk 8, 18 Nov 28 11:48 /dev/sdb2
brwx------ 1 root disk 8, 19 Nov 28 11:48 /dev/sdb3
brwx------ 1 root disk 8, 20 Nov 28 11:48 /dev/sdb4
brwx------ 1 root disk 8, 21 Nov 28 11:48 /dev/sdb5
brwx------ 1 root disk 8, 22 Nov 28 11:48 /dev/sdb6
brwx------ 1 root disk 8, 23 Nov 28 11:48 /dev/sdb7
brwx------ 1 root disk 8, 24 Nov 28 11:48 /dev/sdb8
crw------- 1 root root 21, 0 Nov 28 11:48 /dev/sg0
crw------- 1 root root 21, 1 Nov 28 11:48 /dev/sg1
(Note the two sg generic entries).
If I now enable these rules and reboot, I get:
[root@dev1 ~]# ls -l /dev/dsk* /dev/sd* /dev/sg*
brwx------ 1 root disk 8, 0 Nov 28 12:05 /dev/dsk0_
crw------- 1 root root 21, 0 Nov 28 12:05 /dev/dsk0_0
brwx------ 1 root disk 8, 1 Nov 28 12:05 /dev/dsk0_1
brwx------ 1 root disk 8, 16 Nov 28 12:05 /dev/dsk1_
brwx------ 1 root disk 8, 17 Nov 28 12:05 /dev/dsk1_1
brwx------ 1 root disk 8, 18 Nov 28 12:05 /dev/dsk1_2
brwx------ 1 root disk 8, 19 Nov 28 12:05 /dev/dsk1_3
brwx------ 1 root disk 8, 20 Nov 28 12:05 /dev/dsk1_4
brwx------ 1 root disk 8, 21 Nov 28 12:05 /dev/dsk1_5
brwx------ 1 root disk 8, 22 Nov 28 12:05 /dev/dsk1_6
brwx------ 1 root disk 8, 23 Nov 28 12:05 /dev/dsk1_7
brwx------ 1 root disk 8, 24 Nov 28 12:05 /dev/dsk1_8
brwx------ 1 root root 8, 0 Nov 28 12:04 /dev/sda
brwx------ 1 root root 8, 1 Nov 28 12:04 /dev/sda1
brwx------ 1 root root 8, 16 Nov 28 12:04 /dev/sdb
brwx------ 1 root root 8, 17 Nov 28 12:04 /dev/sdb1
brwx------ 1 root root 8, 18 Nov 28 12:04 /dev/sdb2
brwx------ 1 root root 8, 19 Nov 28 12:04 /dev/sdb3
brwx------ 1 root root 8, 20 Nov 28 12:04 /dev/sdb4
brwx------ 1 root root 8, 21 Nov 28 12:04 /dev/sdb5
brwx------ 1 root root 8, 22 Nov 28 12:04 /dev/sdb6
brwx------ 1 root root 8, 23 Nov 28 12:04 /dev/sdb7
brwx------ 1 root root 8, 24 Nov 28 12:04 /dev/sdb8
Why have I got both sd devices and dsk devices?
And what is the second line?
Why have I got an entry:
crw------- 1 root root 21, 0 Nov 28 11:45 /dev/dsk0_0
This looks like a generic device, but if so, why only one?
And where are the normal sg devices?
If I change the order of the disks on the SCSI bus, the
'generic' entry changes to dsk1_0. It seems to be associated
with the first disk encountered in the bus scan.
My disks are in a SCSI shelf and dsk1 is now in a
lower-numbered slot than dsk0.
[root@dev1 ~]# ls -l /dev/dsk* /dev/sd* /dev/sg*
brwx------ 1 root root 8, 16 Nov 28 16:05 /dev/dsk0_
brwx------ 1 root root 8, 17 Nov 28 16:05 /dev/dsk0_1
brwx------ 1 root root 8, 0 Nov 28 16:05 /dev/dsk1_
crwx------ 1 root root 21, 0 Nov 28 16:05 /dev/dsk1_0
brwx------ 1 root root 8, 1 Nov 28 16:05 /dev/dsk1_1
brwx------ 1 root root 8, 2 Nov 28 16:05 /dev/dsk1_2
brwx------ 1 root root 8, 3 Nov 28 16:05 /dev/dsk1_3
brwx------ 1 root root 8, 4 Nov 28 16:05 /dev/dsk1_4
brwx------ 1 root root 8, 5 Nov 28 16:05 /dev/dsk1_5
brwx------ 1 root root 8, 6 Nov 28 16:05 /dev/dsk1_6
brwx------ 1 root root 8, 7 Nov 28 16:05 /dev/dsk1_7
brwx------ 1 root root 8, 8 Nov 28 16:05 /dev/dsk1_8
brwx------ 1 root root 8, 0 Nov 28 16:05 /dev/sda
brwx------ 1 root root 8, 1 Nov 28 16:05 /dev/sda1
brwx------ 1 root root 8, 2 Nov 28 16:05 /dev/sda2
brwx------ 1 root root 8, 3 Nov 28 16:05 /dev/sda3
brwx------ 1 root root 8, 4 Nov 28 16:05 /dev/sda4
brwx------ 1 root root 8, 5 Nov 28 16:05 /dev/sda5
brwx------ 1 root root 8, 6 Nov 28 16:05 /dev/sda6
brwx------ 1 root root 8, 7 Nov 28 16:05 /dev/sda7
brwx------ 1 root root 8, 8 Nov 28 16:05 /dev/sda8
brwx------ 1 root root 8, 16 Nov 28 16:05 /dev/sdb
brwx------ 1 root root 8, 17 Nov 28 16:05 /dev/sdb1
Is this all as expected?
Am I going to be screwed later on if I need to do something
that requires a generic SCSI device for a particular disk?
Why do I still get /dev/sd* entries?
Any clues anyone?
Cheers,
Terry.
17 years, 6 months
Virtual instruments
by Chris Norman
Hi people,
Are there any open source virtual instruments out there that can be put on
either Linux and / or Windows?
Cheers,
Chris Norman
<!-- cnorman(a)rnibncw.ac.uk -->
17 years, 6 months