similar to: Ext3 Performance Tuning - the journal

Hi, I'm trying to set up an iscsi 12.5 TB storage for some data backup. Doing so, I had some difficulties to find the right tool, maybe it's also a question of the system settings... The server is a 32Bit CentOS 5.3 with the recent updates. Ths iscsi connection can be establised. fdisk and parted fail to create any information on the device or fail completely. using the lvm tools

Hi, I have a strange problem with user quotas enabled on a xfs filesystem and samba 3.0.21c: When a standard block device (e.g. /dev/sdc1) is used for the fs, quota works like expected: /dev/sdc1 on /mnt/tmp type xfs (rw,usrquota) output from level quota:10 debug: [2006/04/19 14:38:48, 10] lib/sysquotas.c:sys_get_quota(394) sys_get_quota() uid(4004, 4004) [2006/04/19 14:38:48, 10]

Hi there, I'm using xen-3.0.2.2-86.1_rhel4.1 on a Redhat AS 4 update 1 for i386. When I create a new domU with the following conf file, everything is ok: ##BEGINNING## kernel = "/boot/vmlinuz-2.6.16-xen3_86.1_rhel4.1" ramdisk = "/boot/initrd-2.6.16-xen3_86.1_rhel4.1.img" builder='linux' memory = 1024 name = "myvm" vcpus = 8 vif = [

I am testing some kickstarts on ESXi virtual machine with pair of 16GB disks. Partitioning is lvm over raid. If i am using "logvol --grow i get "ValueError: not enough free space in volume group" Only workaround i can find is to add --maxsize=XXX where XXX is at least 640MB less than available. (10 extents or 320Mb per created logical volume) Following snippet is failing with

Hello All, I finally compiled xen 3.3.0 using make World, installed it but I cannot get it to Boot, I always get kernel panic, kernel not sync kind of errors, I suppose it''s some hard disk or partition issue, my setup is as follows. CentOS 5.2 x86_64 on a HP ML-115 Grub, menu.list Entries CentOS xen''s line title CentOS (2.6.18-92.1.22.el5xen) root

Hi all. I have currently a server: cat /etc/redhat-release CentOS release 5.7 (Final) uname -a Linux host.domain.com 2.6.18-274.18.1.el5 #1 SMP Thu Feb 9 12:45:44 EST 2012 x86_64 x86_64 x86_64 GNU/Linux I have there a filesystem mounted: /dev/vg0/paczki /home/paczki-workdir ext4 defaults,noatime 0 0 on which df gives strange output: LANG=C df -h

I am not sure if it''s a xen bug or lvm bug, or just my bad hardware, but here''s how to reproduce: /dev/vg0/centos1 is lvm block used by a domainU, it''s 8G in size. #lvcreate -L8192M -s -n snap1 vg0 #mount /dev/vg0/snap1 /mnt do some copying files here #umount /mnt #lvremove /dev/vg0/snap1 not removed! it says can''t allocated memory #xm mem-set 0 512 #lvremove

Hi! I'' ve a xen virtual machine, and i'' d like to assign cdrw device to it. My physical device on domain0 is /dev/hda, and in the configuration file i'' ve this: disk = [ ''phy:vg0/vx-disk,sda1,w'', ''phy:vg0/vx-swap,sda2,w'', ''phy:vg0/vx-data,sda5,w'' ] I'' ve tried to assign the cdrom to it in many ways i

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Is there some limit on the size of a file system which can be shared via samba? I'm trying to set up a file server with a 100GB shared partition and it doesn't want to work. I'm running Fedora Core 4, and Samba Version 3.0.14a-2. The output from testparm looks like this: [root@stitch samba]# testparm Load smb config files from

Hello list. I have a perfectly working PV host, with this configuration: kernel = "/boot/vmlinuz-2.6.18.8-xen-3.3.0-7mdv" ramdisk = "/boot/initrd-2.6.18.8-xen-3.3.0-7mdv.img" root = "/dev/sda1 ro" extra = "(hd0)/boot/grub/menu.lst" memory = 256 maxmem = 512 name = "sexonthebeach" uuid = "f36962f5-0dec-4708-84a0-f5b4dea48d34" disk = [

Hi! I am using xen-tools version: 3.9-4 to create domUs: 1. time xen-create-image --verbose --dist=lenny --install-source=/mnt/xen-file-images/lenny-64-template-debootstrap-30Jun09-fix2.tar --hostname dummy --ip xxx.xxx.xxx.xxx --force 2. xm create dummy.cfg Then I get the message Device /dev/vg0/dummy-disk is mounted in the privileged domain, and so cannot be mounted by a guest. 3. When I

Hello, I am having trouble expanding a volume. Every time I try to add bricks to the volume, I get this error: [root at gluster1 sdb1]# gluster volume add-brick vg0 gluster5:/export/brick2/sdb1 gluster6:/export/brick2/sdb1 /export/brick2/sdb1 or a prefix of it is already part of a volume Here is the volume info: [root at gluster1 sdb1]# gluster volume info vg0 Volume Name: vg0 Type:

On 06.07.2017 15:35, Robert Nichols wrote: > On 07/06/2017 04:43 AM, Volker wrote: >> Hi all, >> >> one of my lv has become completely unaccessible. Every read access >> results in a buffer io error: >> >> Buffer I/O error on dev dm-13, logical block 0, async page read >> >> this goes for every block in the lv. A ddrescue failed on every single

'--no-degraded' flag in the first mdadm call inhibits the startup of array unless all expected drives are present. This will prevent starting arrays in degraded state. Second mdadm call (after LVM is scanned) will scan unused yet devices and make an attempt to run all found arrays even they are in degraded state. Two new tests are added. This fixes rhbz1527852. Here is boot-benchmark

I thought I'd test replacing a failed drive in a 4 drive raid 10 array on a CentOS 5.2 box before it goes online and before a drive really fails. I 'mdadm failed, removed', powered off, replaced drive, partitioned with sfdisk -d /dev/sda | sfdisk /dev/sdb, and finally 'mdadm add'ed'. Everything seems fine until I try to create a snapshot lv. (Creating a snapshot lv

Hi, I have an iscsistorage which I attached to a new centos 6.3 server. I added logic volumes as usual, the block devices (sdb & sdc) showed up in dmesg; I can mount and access the stored files. Now we did an firmware software update to that storage (while unmounted/detached from the fileserver) and after reboot of the storage and reatache the iscsi nodes I do get new devices. (sdd &

Hi, I have a 2 nodes ocfs2 cluster running UEK 2.6.32-100.0.19.el5, ocfs2console-1.6.3-2.el5, ocfs2-tools-1.6.3-2.el5. My problem is that all the time when i try to run /etc/init.d/o2cb stop it fails with this error: Stopping O2CB cluster CLUSTER: Failed Unable to stop cluster as heartbeat region still active There is no active mount point. I tried to manually stop the heartdbeat with

Hi all, one of my lv has become completely unaccessible. Every read access results in a buffer io error: Buffer I/O error on dev dm-13, logical block 0, async page read this goes for every block in the lv. A ddrescue failed on every single block. $ lvdisplay --- Logical volume --- LV Path /dev/vg0/lv-vm-tviewer LV Name lv-vm-tviewer VG Name

Hi, using btrfs with LVM snapshots seems to be confusing /proc/mounts After mounting a snapshot of an original filesystem, the devicename of the original filesystem is overwritten with that of the snapshot in /proc/mounts. Steps to reproduce: arnd@kallisto:/mnt$ sudo mount /dev/vg0/original /mnt/original [ 107.041432] device fsid 5c3e8ca2-da56-4ade-9fef-103a6a8a70c2 devid 1 transid 4

Hi List! I want to use rsync to create differential backups of my lvm-snapshots. fullbackup-filename: /mnt/sdc1/snapshotvergleich/rootbackup1.img current snapshot: /dev/vg0/rootbackup note: compiled-in --copy-devices-patch root@xp8main3:/usr/local/src/rsync# ./rsync --version rsync version 3.1.0dev protocol version 31.PR5 Copyright (C) 1996-2009 by Andrew Tridgell, Wayne Davison, and