search for: sda12

...mark results and other related information are available through this site. Please check it out: http://people.valinux.co.jp/~ryov/dm-ioband/ Bandwidth control on a per partition basis ========================================== Test procedure -------------- o Prepare three partitions sda11, sda12 and sda13. o Create three ioband devices ioband1, ioband2 and ioband3 on each partition respectively. o Give weights of 40, 20 and 10 to each ioband device respectively. o Run 50, 100 and 200 processes issuing random read/write direct I/O with 4KB data on each ioband device at the sam...

...mark results and other related information are available through this site. Please check it out: http://people.valinux.co.jp/~ryov/dm-ioband/ Bandwidth control on a per partition basis ========================================== Test procedure -------------- o Prepare three partitions sda11, sda12 and sda13. o Create three ioband devices ioband1, ioband2 and ioband3 on each partition respectively. o Give weights of 40, 20 and 10 to each ioband device respectively. o Run 50, 100 and 200 processes issuing random read/write direct I/O with 4KB data on each ioband device at the sam...

...mark results and other related information are available through this site. Please check it out: http://people.valinux.co.jp/~ryov/dm-ioband/ Bandwidth control on a per partition basis ========================================== Test procedure -------------- o Prepare three partitions sda11, sda12 and sda13. o Create three ioband devices ioband1, ioband2 and ioband3 on each partition respectively. o Give weights of 40, 20 and 10 to each ioband device respectively. o Run 50, 100 and 200 processes issuing random read/write direct I/O with 4KB data on each ioband device at the sam...

...ould anyone give me any advice? For dm-ioband details, please see the website at http://people.valinux.co.jp/~ryov/dm-ioband/ The number of issued I/Os -------------------------------------------------------------- | device | sda11 | sda12 | | weight setting | 80% | 20% | |----------------------+-------------------+-------------------| | KVM | I/Os | 4397 | 2902 | | | ratio to total | 60.2% | 39.8% | |-----+----...

...ould anyone give me any advice? For dm-ioband details, please see the website at http://people.valinux.co.jp/~ryov/dm-ioband/ The number of issued I/Os -------------------------------------------------------------- | device | sda11 | sda12 | | weight setting | 80% | 20% | |----------------------+-------------------+-------------------| | KVM | I/Os | 4397 | 2902 | | | ratio to total | 60.2% | 39.8% | |-----+----...

Hi All, I am trying to create an MD device. I am using the command: /sbin/mdadm --create --a /dev/md12 --level=1 --run --raid-devices=2 /dev/sda12 /dev/sdb12 to create the device, and to dynamically create the device file if needed. What I want is the device file to be created as /dev/md12, but with the -a flag it creates it as /dev/md<first unwsed minor number>. I have tried various options to the -a or --auto, but cannot seem to find...

.../dev/sda (hd1) /dev/sdb This makes me reluctant to boot into CentOS-7.2. An additional, possibly related, query. When I run grub2-mkconfig it lists various OS's it finds: ========================= Found Windows 7 (loader) on /dev/sda1 Found CentOS Linux release 7.1.1503 (Core) on /dev/sda12 Found Windows 7 (loader) on /dev/sdb1 Found CentOS release 6.5 (Final) on /dev/sdb5 Found CentOS release 5.6 (Final) on /dev/sdc7 done ========================= Why does it not list CentOS 7.2 since it ========================= Found linux image: /boot/vmlinuz-3.10.0-327.4.4.el7.x86_64 Found initrd...

On 07/28/2016 04:20 PM, geo.inbox.ignored wrote: <<>> > i do hope it is driver problem and not the touch pad. > ===> thank you Jesus. strange, but it was the driver. new install ran without a stall. lt is now recovered from 7-32 trashing. i would very much like to install 7-32, but it looks like it just may be that, like fine wine, 7-32 needs to age a little longer for my

...able to boot to the current system as before. But I found that this was not the case; on rebooting the machine hung, with a repeating "-" on the screen. The only way I was able to recover the current system was to use a CentOS Live USB stick I had to install CentOS on a spare partition (sda12). With that system running I was able to mount the old system (on sdb10) as /mnt, and the boot partition (sdb2) as /mnt/boot, and then give the command grub-install --root-directory=/mnt /dev/sda On re-booting the old system came up. (I may say I also tried to run grub-install from the USB stic...

...partitioning5.p11 partitioning5.fs \ + partitioning5.p13 \ + partition-type=mbr + +# Connect with guestfish and read/write stuff to partition 12. +guestfish --format=raw -a "nbd://?socket=$PWD/partitioning5.sock" <<'EOF' + run + mount /dev/sda12 / + touch /hello + fill-pattern "abc" 10000 /pattern + ll / + umount /dev/sda12 + sync +EOF -- 2.20.1

...h oos 7 already installed. after i tricked the oos 7 partition a few times to reduce size, i repartitioned drive with oos down to sda1= 1.6 GB system, sda2= 43.0 GB oos 7, sda4= 8.4 GB recovery, sda3= extended sda5= 1.1 GB boot, sda6= 3.1 GB swap, sda7 thru sda10= 11 GB linux os, sda11= 84 GB home, sda12= 66 GB open use. only reason i left oos 7 is that if i ever, God forbid, am forced to lower my self, it is installed. only times i have booted oos was during repartitioning to see if it had problems with sda3. it did not, i have not booted oos again. i did pull an update package, do not recall whi...

On 07/29/2016 02:52 AM, Peter wrote: > On 29/07/16 18:10, John R Pierce wrote: >> also, try and scrounge another DDR2 SODIMM for that thing, according to >> my google search, it supports up to 2 x 4GB == 8GB, and you said you >> only have the stock 2GB. > > They are dirt cheap on ebay, from Hong Kong with free shipping. I would > go all the way and max it out. >

An evolution of the patch I posted yesterday to qemu-devel (https://www.mail-archive.com/qemu-devel@nongnu.org/msg588920.html) which (a) works and (b) has a test. Rich.

I have posted several questions now and have ben unsuccessful in getting any responses, so i thought i would take a different tack. I know adjusting permissions on Samba shares, through the Microsoft MMC is possible when you have POSIX ACL support compiled in your kernel. I don't think that level of control is necessary for me and short of recompiling the kernel for that support i have been

...autodetect /dev/sda8 7903 8145 1951866 fd Linux raid autodetect /dev/sda9 8146 8511 2939863+ fd Linux raid autodetect /dev/sda10 8512 8574 506016 83 Linux /dev/sda11 8575 8637 506016 83 Linux /dev/sda12 8638 8700 506016 83 Linux /dev/sda13 8701 8825 1004031 83 Linux /dev/sda14 8826 8888 506016 83 Linux /dev/sda15 8889 9013 1004031 83 Linux /dev/sda16 9014 9726 5727141 83 Linux...

This is a revised version of the two series previously posted here: https://www.redhat.com/archives/libguestfs/2019-January/msg00137.html https://www.redhat.com/archives/libguestfs/2019-January/msg00139.html There have been many smaller changes but the highlights are: - Using SECTOR_SIZE instead of hard-coding 512 everywhere. - Additional safety checks that the EBR chain doesn't jump

We''ve been keeping around the inode sequence number in hopes that somebody would use it, but nobody uses it and people actually use i_version which serves the same purpose, so use i_version where we used the incore inode''s sequence number and that way the sequence is updated properly across the board, and not just in file write. Thanks, Signed-off-by: Josef Bacik