similar to: Mounting RAID1 writeable with two devices missing but all data present

Hi! I recently tried to mount a filesystem in RAID1 mode using loopback devices. I followed the instructions at [1]. Here''s exactly what I''ve done: $ dd if=/dev/zero of=raid1_0.img bs=1M count=500 $ dd if=/dev/zero of=raid1_1.img bs=1M count=500 $ mkfs.btrfs -m raid1 -d raid1 raid1_0.img raid1_1.img $ losetup /dev/loop0 raid1_0.img $ losetup /dev/loop1 raid1_1.img $ mount -t

Hey, guys. I have a problem when installing syslinux 4.06, and I'd be grateful if someone could tell me how to solve the problem. My task - to install the bootloader on the virtual machine image. The image contains the MBR and the only partition with the file system ext4. The file system contains all the files for the guest OS. To install bootloader into the image of the guest OS, I use the

dd if=/dev/null of=img5 bs=1 seek=2G dd if=/dev/null of=img6 bs=1 seek=2G mkfs.btrfs -d raid1 -m raid1 img5 img6 losetup /dev/loop4 img5 losetup /dev/loop5 img6 btrfs device scan mount -t btrfs /dev/loop4 dir umount dir losetup -d /dev/loop5 mount -t btrfs -o degraded /dev/loop4 dir umount dir losetup -d /dev/loop4 ioctl: LOOP_CLR_FD: Device or resource busy mkfs.ext3 /dev/loop4 mke2fs 1.39

Hi, I have Xen 3.3.1 dom0 on Debian with 2.6.26-2-xen-amd64 kernel and I had to "xm destroy" my domU. Now when I try to start it again it fails like this: # xm list | grep n39 # # xm create -c /xen/conf/n39 Using config file "/xen/conf/n39". ROOT xen1:~> Error: Device 4 (vbd) could not be connected. losetup -r /dev/loop1 /xen/iso/amd64-netbsd-6.iso failed # losetup -a

Hi, This left me puzzled for a while: 22:29 borg:/ # losetup /dev/loop1 /.B.disk 22:29 borg:/ # mount /dev/loop1 /B mount: /dev/loop1: can''t read superblock 22:29 borg:/ # blkid /dev/loop1 /dev/loop1: UUID="e19fe89b-cde3-4ccc-bc70-b759a57bd1c9" UUID_SUB="f29c6218-d040-4546-a227-4dd2d2142817" TYPE="btrfs" 22:29 borg:/ # losetup -d /dev/loop1 22:29 borg:/ #

# uname -a Linux dhcppc1 3.0.1-xxxx-std-ipv6-64 #1 SMP Sun Aug 14 17:06:21 CEST 2011 x86_64 x86_64 x86_64 GNU/Linux mkdir test5 cd test5 dd if=/dev/null of=img5 bs=1 seek=2G dd if=/dev/null of=img6 bs=1 seek=2G losetup /dev/loop2 img5 losetup /dev/loop3 img6 mkfs.btrfs -d raid1 -m raid1 /dev/loop2 /dev/loop3 btrfs device scan btrfs filesystem show Label: none uuid:

Hi all, we are running two servers with Ubuntu 8.04 LTS Server with Xen 3.2 and two dual-core CPUs: processor : {0-3} vendor_id : AuthenticAMD cpu family : 15 model : 65 model name : Dual-Core AMD Opteron(tm) Processor 2218 HE stepping : 3 cpu MHz : 2613.394 cache size : 1024 KB physical id : 0 siblings : 1 core id : 0 cpu cores : 1 fpu :

Hello, today I wanted to remove one drive from raid1, and people at #btrfs advised me to use ''-dconvert=single'' before ''btrfs device delete''. I thought of adding ''-mconvert=dup'' too, but the kernel does not let me do that. It looks like ''dup'' is disallowed for an array of multiple devices. So, to go back to a single-drive

I am trying to understand how btrfs works with Raid1. Is it possible to create the filesystem with -m raid1 -d raid1 in which there is only one device available when the filesystem is created. Is it possible to refer to a second device as "missing" The use case I am thinking of is converting an existing raid1 setup from mdm + lvm + ext4 to btrfs with raid1 and subvolumes. I would

Hi, I have setup a RAID1 using 3 devices (500G each) on separate disks. After removing one disk physically the filesystem cannot be mounted in degraded nor in recovery mode. When putting the disk back in the filesystem can be mounted without errors. I did a cold-swap (powercycle after removal/insertion of the disk). Here are the details: - latest kernel 3.2.1 and btrfs-tools on xubuntu

Hello, I had a raid1 btrfs (540GB) on vanilla 3.6.3, a disk failed, and removed it at power off, plugged in a new one, partitioned it (to 110GB, by error), and added it to btrfs. I tried to remove the missing device, and it said "Input/output error" after a while. Next attempts simply gave "Invalid argument". I repartitioned, rebooted the system, and made the partition grow:

Hi, When I install Oracle RAC on Xen VM, some problem occurred. How can I configure two NICs on a Xen''s DomU. You know, RAC''s installation requires two NICs on a node. I am a newbie about Xen. Please give me some advice. Thanks. Yaqiong lee Beijing,China -----邮件原件----- 发件人: xen-users-bounces@lists.xensource.com [mailto:xen-users-bounces@lists.xensource.com] 代表

we cannot use the loop device which has been connected to a file in the btrf The reproduce steps is following: # dd if=/dev/zero of=vdev0 bs=1M count=1024 # losetup /dev/loop0 vdev0 # mkfs.btrfs /dev/loop0 ... failed to zero device start -5 The reason is that the btrfs don''t implement either ->write_begin or ->write the VFS API, so we fix it by setting ->write to

Hallo, linux-btrfs, First I create an array of 2 disks with mkfs.btrfs -d raid0 -m raid1 /dev/sdb1 /dev/sdd1 and mount it at /srv/MM. Then I fill it with about 1,6 TByte. And then I add /dev/sde1 via btrfs device add /dev/sde1 /srv/MM btrfs filesystem balance /srv/MM (it run about 20 hours) Then I work on it, copy some new files, delete some old files - all works well. Only df

hi all, i have SCEVAddRec {{(32 + @edge.8265),+,32}<Loop0>,+,4}<Loop1> where Loop0 and Loop1 are brothers (loops at the same level of the loopnest), and Loop0 have a computable backedge taken count. when i call getSCEVAtScope({{(32 + @edge.8265),+,32}<Loop0>,+,4}<Loop1> , Loop1), it just give me a {{(32 + @edge.8265),+,32}<Loop0>,+,4}<Loop1>, instead of

I''m trying to create a multi-device filesystem on top of regular files (not actual disks), and mount that to a loopback device. For a filesystem created on a single file, it works fine, but for a filesystem across multiple files, it doesn''t. dd if=/dev/zero of=img1 bs=4096 count=65536 dd if=/dev/zero of=img2 bs=4096 count=65536 dd if=/dev/zero of=img3 bs=4096 count=65536 dd

centos 6 failed to create entries under /dev for newly created loopback devices. Any one know why? and how to fix/workaround it? The steps to duplicate is pretty simple dd if=/dev/zero of=/tmp/deleteme bs=1M count=100 losetup /dev/loop0 /tmp/deleteme fdisk /dev/loop0?? ## created partitions 1, 2, etc. fdisk -l /dev/loop0? ## confirmed that the partitions do exist mkfs.ext3 /dev/loop0p1 ## failed

I have problem with smbmount and losetup working together. The data seems to be corrupted. Description: I have an NT4 server with a share. On my linux box i use smbmount to mount the share. I have created a big file on the share and use losetup to configure a loop-back device on which i try to create/use a filesystem. It seems to work at first with ext2fs, but after copying some files to the

Hi, I'm trying to build a bootable MSDOS disk and put it on a ISO with floppy and hard disk emulation. I want to use commonly available Linux tools like dd, losetup, mkdosfs, memdisk etc. I have done the following: 1. dd if=/dev/zero of=myImage bs=1M count=50 [ Builds a 52MB image ] 2. losetup /dev/loop0 myImage [Links /dev/loop0 to myImage file ] 3. vi /grub/stage1; %!xxd; [ NULL the partion

Quick summary: Syslinux stops at "Boot failed". Which, from a quick look at the raw disk image, seems to indicate that the boot sector loads but it fails to load the .sys loader. The details: I've been trying to load Linux (or etherboot...or anything at all that is not NT embedded) into a set of Compaq Evo T20 48/64 for a while now. What I finally managed to do is using the