search for: sdd4

...module support, but that was about it. Xm list shows: [root@localhost xen]# xm list Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 1019 2 r----- 44.6 Which is ok. I have created a loop back file system on my /dev/sdd4. If I mount /dev/sdd4 I can see a flat file of the correct size. If I mount this in loopback mode, I can see the contents properly. [root@localhost xen]# ls /remote lost+found vmdisk1 [root@localhost xen]# df Filesystem 1K-blocks Used Available Use% Mounted on /dev/sdd2...

...ganized my data, lots of "mv" and "cp". then, upon unmounting a ext3 partition the following was shown on the console: (the leading "Mar 22 02:40:04 sheep kernel:" is cut here) - ------------------------------- ~ sb orphan head is 940994 ~ sb_info orphan list: ~ inode sdd4:940994 at cf852874: mode 40755, nlink 0, next 486721 ~ inode sdd4:486721 at cfce8674: mode 40755, nlink 0, next 551857 ~ inode sdd4:551857 at cfce80d4: mode 40755, nlink 0, next 0 ~ Assertion failure in ext3_put_super() at fs/ext3/super.c:412: "list_empty(&sbi->s_orphan)" ~ -------...

Hello, I added a new disk into our RAID5 array, it looks like this: md2 : active raid5 sdd4[3] sde4[4] sda4[0] sdc4[2] sdb4[1] 3767274240 blocks level 5, 64k chunk, algorithm 2 [5/5] [UUUUU] # btrfs fi sh Label: none uuid: 5534d2e7-be31-49c7-8ab7-90c5ab8afe18 Total devices 1 FS bytes used 2.24TB devid 3 size 2.63TB used 2.63TB path /dev/md2 # mount ... /dev/md2 on /home type...

...1.el7.x86_64 $ rpm -qa | grep -i lvm lvm2-libs-2.02.115-3.el7_1.1.x86_64 lvm2-2.02.115-3.el7_1.1.x86_64 And the solution proposed in above examples does not work on it. After (lv xxx is only on /dev/sdb4 before): # lvconvert --mirrors 1 --stripes 4 /dev/cinder-volumes/xxx /dev/sda4 /dev/sdc4 /dev/sdd4 /dev/sdf4 I am getting in "lvdisplay -m": --- Logical volume --- LV Path /dev/cinder-volumes/xxx LV Name xxx VG Name cinder-volumes LV UUID AKjKAo-66cv-Ygc2-4Ykq-sSJQ-RJOY-mfjoMD LV Write Access read/write LV...

I have 4 disks in a RAID5 array. I want to add a 5th. So I did mdadm --add /dev/md3 /dev/sde1 This worked but, as expected, the disk isn't being used in the raid5 array. md3 : active raid5 sde1[4] sdd4[3] sdc3[2] sdb2[1] sda1[0] 2930279808 blocks level 5, 64k chunk, algorithm 2 [4/4] [UUUU] So then I tried the next step: mdadm --grow --raid-devices=5 /dev/md3 But now I have problems... mdadm: Cannot set device size/shape for /dev/md3: Invalid argument Can CentOS 4.6 grow md5 arrays?...

...8225280 bytes, blocks of 1024 bytes, counting from 0 Device Boot Start End #cyls #blocks Id System /dev/sdd1 0 - 0 0 0 Empty /dev/sdd2 0 - 0 0 0 Empty /dev/sdd3 0 - 0 0 0 Empty /dev/sdd4 0 - 0 0 0 Empty Warning: given size (233937920) exceeds max allowable size (233933761) sfdisk: bad input As I see in fdisk's and sfdisk output there is a difference at some level in disk geometry. Could you suggest a solution? Best regards, Rafal.

Hello list. The next days we are going to install Centos 7 on a new server, with 4*3Tb sata hdd as raid-5. We will use the graphical interface to install and set up raid. Do I have to consider anything before installation, because the disks are very large? Does the graphical use the parted to set/format the raid? I hope the above make sense. Thank you in advance. Nikos

...s off [ 10.657413] sd 3:0:0:0: [sdd] Mode Sense: 00 3a 00 00 [ 10.657432] sd 3:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn''t support DPO or FUA [ 10.657534] sdd: sda1 sda2 sda3 sda4 [ 10.672225] sd 0:0:0:0: [sda] Attached SCSI disk [ 10.674742] sdd1 sdd2 sdd3 sdd4 [ 10.675145] sd 3:0:0:0: [sdd] Attached SCSI disk [ 10.680425] sdb1 sdb2 sdb3 sdb4 [ 10.680814] sd 1:0:0:0: [sdb] Attached SCSI disk [ 10.681216] sdc1 sdc2 sdc3 sdc4 [ 10.681606] sd 2:0:0:0: [sdc] Attached SCSI disk [ 10.951914] md: raid0 personality registered for level 0 [ 10.9547...

...nod /dev/sdc b 8 32 # | mknod /dev/sdc1 b 8 33 # | mknod /dev/sdc2 b 8 34 # | mknod /dev/sdc3 b 8 35 # | mknod /dev/sdc4 b 8 36 # | # | mknod /dev/sdd b 8 48 # | mknod /dev/sdd1 b 8 49 # | mknod /dev/sdd2 b 8 50 # | mknod /dev/sdd3 b 8 51 # | mknod /dev/sdd4 b 8 52 # +-------- # Create mount points for filesystems mkdir -p /mnt/medium mkdir -p /mnt/system mkdir -p /mnt/rootfs # Mount the /proc filesystem (enables filesystem detection for 'mount') mkdir /proc mount -t proc proc /proc # Invoke busybox if requested via the kernel command line...

...s of the RAID5 root # cat /proc/mdstat Personalities : [raid1] [raid6] [raid5] [raid4] [multipath] md2 : active raid5 sda5[0](F) sde5[4](F) sdd5[3](F) sdc5[2] sdb5[1] 1724864512 blocks super 1.2 level 5, 512k chunk, algorithm 2 [5/2] [_UU__] md1 : active raid5 sda4[5](F) sde4[6](F) sdd4[7](F) sdc4[2] sdb4[1] 209713152 blocks level 5, 512k chunk, algorithm 2 [5/2] [_UU__] md0 : active raid1 sda1[0] sde1[4] sdd1[3] sdc1[2] sdb1[1] 511936 blocks [5/5] [UUUUU] If I check the drives I get informed that the md superblock has vanished on the missing drives. A reboo...

Hello, I originally posted this to xen-users, but someone suggested I post it here. I am having ACPI problems on a PenguinComputing Altus1600 system. It has 2x dual core Opteron 2210 processors. The system boots with a standard Debian or Ubuntu SMP kernel, with ACPI enabled. However the xen live cd, binary xen install, as well as my own custom compile of xen 3.0.4 from source will not boot.