similar to: Utility tool for dm-ioband.

Hi, I have 2 identical xSeries 346 with 2 identical IBM 72GB scsi drive. What i did is install the centos 4.2 serverCD on the first IBM and set the HDD to raid1 and raid0 for swap. Now what i did is get the 2nd HDD in the 1st Server swap it with the 1st HDD in the 2nd Server and rebuild the Raids. The 1st server rebuild the array fine. My problem is the Second server, after rebuilding it and

Thanks for your help Sean, did all the steps you mentioned. One thing I don't understand, when partitions are created, why does Linux number it awkwardly? For example, I created 1 Primary partition of 10% disk, then created 1 Extended partition of 90% disk. Inside that extended partition, I created 3 logical partitions 33% each. It went numbering sdb1, sdb5, sdb6 and sdb7. Where's the hell

Hi, I have a RAID 1 (using mdadm) on CentOS Linux and in /proc/mdstat I see this: md7 : active raid1 sda2[0] sdb2[1] 26627648 blocks [2/2] [UU] [-->> it's OK] md1 : active raid1 sdb3[1] sda3[0] 4192896 blocks [2/2] [UU] [-->> it's OK] md2 : active raid1 sda5[0] sdb5[1] 4192832 blocks [2/2] [UU] [-->> it's OK] md3 : active raid1 sdb6[1] sda6[0] 4192832 blocks [2/2]

Which disk is it? /dev/sda6 or /dev/sdb8 or /dev/sdc6? >From my log: Jun 10 21:25:39 postamt1 kernel: attempt to access beyond end of device Jun 10 21:25:39 postamt1 kernel: 08:06: rw=0, want=1680353324, limit=59954548 Jun 10 21:25:39 postamt1 kernel: EXT3-fs error (device sd(8,6)): ext3_readdir: directory #3473659 contains a hole at offset 1852399616 $ mount /dev/sdb6 on / type auto (rw)

Hi, I'm setting up ocfs on opensuse 10.3 with kernel 2.6.22.5-31 . Appreciate if you could guide on the solution to this error. I have a secondary hard disk (80G) created raw paritions primary /dev/sdb1 - 12G extended /dev/sdb2 - 12G comprising of /dev/sdb5 - 4G /dev/sdb6 - 3G /dev/sdb7 - 5G The error is as follows: Could not get a raw device slot for disk access. Please free up some

I have a 1.5TB internal disk on my server. I partitioned this with fdisk, and CentOS-5.6 runs perfectly on it. But fdisk gives a very strange report. Here is the perfectly normal response to mount: ----------------------------- /dev/sdb10 on / type ext3 (rw) proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) devpts on /dev/pts type devpts (rw,gid=5,mode=620) /dev/sdb2 on /boot type ext3

Hi all, I am running fedora 11 with kernel 2.6.30.9-102.fc11.x86_64 #1 SMP Fri Dec 4 00:18:53 EST 2009 x86_64 x86_64 x86_64 GNU/Linux. I am noticing a partition on my drive is reporting incorrect size with "df", the partition is ext3 size 204GB with about 79GB actual usage, the "df" result show the partition size to be 111GB, 93GB is missing. Please advice on what

Hello! I installed NexentaOS (Opensolaris kernel b104+). First booting system is true. Before first rebooting system updates boot_archive. It''s false. Computer is freeze and CapsLock and ScrollLock is blinking. Helps only RESET button. My system is Ubuntu 8.10, kernel-2.6.30-rc3-tip, Xen-3.4-Stable with debug options enabled. My hardware: AMD Athlon64X2 5400+, RAM 4GB. For DomU: mem=1024,

We are setup new DELL 6800 server fro Informix database. We create "raw" partitions and change "raw" partitions owner to "informix:informix". After reboot owner change back to "root". we don't have problem on CENTOS 3.X, but this problem happen on CENTOS 4.6. I double check "SELINUX" is "disable". does anyone know why it work on

We are set up CENTOS 5.2 (X86) as our database server.? I created raw partitions and also put definition on /etc/sysconfig/rawdevices. I can use "raw -qa" see raw partitions.? The wield things is after reboot /dev/raw is not exist any more. ? Does anyone know how to fix it? ? Thanks.

Hi everyone, I'm happy to announce that I've implemented a Block I/O bandwidth controller. The controller is designed to be of use in a cgroup or virtual machine environment. The current approach is that the controller is implemented as a device-mapper driver. What's dm-band all about? ======================== Dm-band is an I/O bandwidth controller implemented as a device-mapper

Hi everyone, I'm happy to announce that I've implemented a Block I/O bandwidth controller. The controller is designed to be of use in a cgroup or virtual machine environment. The current approach is that the controller is implemented as a device-mapper driver. What's dm-band all about? ======================== Dm-band is an I/O bandwidth controller implemented as a device-mapper

Hi everyone, This is dm-ioband version 0.0.4 release. Dm-ioband is an I/O bandwidth controller implemented as a device-mapper driver, which gives specified bandwidth to each job running on the same physical device. Changes since 0.0.3 (5th February): - Improve the performance when many processes are issuing I/Os simultaneously. - Change the table format to fully support dmsetup

Hi everyone, This is dm-ioband version 0.0.4 release. Dm-ioband is an I/O bandwidth controller implemented as a device-mapper driver, which gives specified bandwidth to each job running on the same physical device. Changes since 0.0.3 (5th February): - Improve the performance when many processes are issuing I/Os simultaneously. - Change the table format to fully support dmsetup

Hi everyone, This is dm-ioband version 0.0.4 release. Dm-ioband is an I/O bandwidth controller implemented as a device-mapper driver, which gives specified bandwidth to each job running on the same physical device. Changes since 0.0.3 (5th February): - Improve the performance when many processes are issuing I/Os simultaneously. - Change the table format to fully support dmsetup

Hi everyone, Here are new releases of bio-cgroup. Changes from the previous version are as follows: - Accurate dirty-page tracking Support migrating pages between bio-cgroups with minimum overhead, but I think such a situation is quite rare. - Fix a bug of swapcache page handling Sometimes, "bad page state" is occurred since the memory controller has temporarily changed the

Hi everyone, Here are new releases of bio-cgroup. Changes from the previous version are as follows: - Accurate dirty-page tracking Support migrating pages between bio-cgroups with minimum overhead, but I think such a situation is quite rare. - Fix a bug of swapcache page handling Sometimes, "bad page state" is occurred since the memory controller has temporarily changed the

Hi everyone, Here are new releases of bio-cgroup. Changes from the previous version are as follows: - Accurate dirty-page tracking Support migrating pages between bio-cgroups with minimum overhead, but I think such a situation is quite rare. - Fix a bug of swapcache page handling Sometimes, "bad page state" is occurred since the memory controller has temporarily changed the

Hi everyone, This is dm-ioband version 1.1.0 release. Dm-ioband is an I/O bandwidth controller implemented as a device-mapper driver, which gives specified bandwidth to each job running on the same physical device. - Can be applied to the kernel 2.6.26-rc2-mm1. - Changes from 1.0.0 (posted on May 19, 2008): - Measures against high memory pressure. I/O requests to reclaim pages won't

Hi everyone, This is dm-ioband version 1.1.0 release. Dm-ioband is an I/O bandwidth controller implemented as a device-mapper driver, which gives specified bandwidth to each job running on the same physical device. - Can be applied to the kernel 2.6.26-rc2-mm1. - Changes from 1.0.0 (posted on May 19, 2008): - Measures against high memory pressure. I/O requests to reclaim pages won't