similar to: LVM problem after adding new (md) PV

Hi, I''m running OpenSuse 12.2 with kernel 3.5.3 HBA= LSI 1068e using the MPTSAS driver (patched) (https://patchwork.kernel.org/patch/1379181/) SANOS1:/media # uname -a Linux SANOS1 3.5.3 #3 SMP Sun Sep 2 18:44:37 CEST 2012 x86_64 x86_64 x86_64 GNU/Linux I''ve tried to simulate a disk replacement but it seems that now /dev/sdg is stuck in the btrfs pool (RAID10) SANOS1:/media #

Dear all, actually I installed CentOS 5.4 x86_64 on 11 new Dell R710 servers. It is required to use 5.4 to be covered by the NetApp Interoperability Matrix for use of Snapdrive. All systems spit out the error message mpt2sas0: failure at drivers/scsi/mpt2sas/mpt2sas_scsih.c:4637/_scsih_add_device()! at boot time. In dmesg the complete SCSI initialization logging appears as follows: SCSI

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

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, 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 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

We have CENTOS 5.6 on DELL server. I create VG and LV on one SSD disk. after couple weeks I decide to delete it. I unmount file system but can not delete LV. It say "in use". I try following but still NOT work: # lvchange -an /dev/VG0-SSD910/LV01-SSD910 LV VG0-SSD910/LV01-SSD910 in use: not deactivating # kpartx -d /dev/VG0-SSD910/LV01-SSD910 # lvchange -an

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

I'm pulling my hair out trying to setup a mirrored logical volume. lvconvert tells me I don't have enough free space, even though I have hundreds of gigabytes free on both physical volumes. Command: lvconvert -m1 /dev/vg1/iscsi_deeds_data Insufficient suitable allocatable extents for logical volume : 10240 more required Any ideas? Thanks!, Gordon Here's the output from the

-----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

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

'--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

Hello, I hope this is the mailing list to discuss this issue, but if not sorry for spamming! I just discovered a really slow IO performance on DomUs running debian wheezy over wheezy dom0s, any operation that requires disk read or write takes a lot of time. Here are the hardware parameters: Single Xeon 5120 (dual core) 8GB of ram Hardware raid 2x250GB drives raid 1 his is the configuration

Hello ext3 list, I am having an odd issue with one of my filesystems, and I am hoping someone here can help out. Yes, I do have backups. :) But as is often the case, it's nice to avoid restoring from backup if possible. If there is a more appropriate place for this question please let me know. After quite a while between reboots, I saw a report on the console that the filesystem was

I have a handful of new systems where I've seen unexpectedly low disk performance on an Avago SAS controller, when using CentOS 7. It looked like a regression, so I installed CentOS 6 on one of them and reloaded CentOS 7 on the other. Immediately after install, a difference is apparent in the RAID rebuild speed. The CentOS 6 system is initializing its software RAID5 array at somewhere

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

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 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 = [

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:

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