similar to: testing that volumes are not currently attached to loopback devices

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

Is there something special about filesystems mounted via the loop device, which prevents Samba from sharing them? I have a small LAN with several PCs on it. It has a few Windows machines, and a Linux machine running Mandrake 10 (kernel 2.6.3), which shares out its root ("/") read-only as "c". (Temporarily, for testing, it is shared with full write permissions, which I know

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

Here's the problem. We perform full tar backups of our CentOS 4/5 machines in real-time at regular intervals. And when a disaster happens, we are able to restore those backups onto virgin filesystems, make the /dev/null, /dev/zero and /dev/console devices .. and boot the machine. This has worked well on standalone systems, and also on Xen 3.0.3 guests on CentOS 4.4 machines, where each guest

Hello, there is a "fdboot.img" floppy drive image included with FreeDOS ISO file. It's a floppy image file: root at debian64:~# file -s /home/martin/FreeDOS/isolinux/fdboot.img /home/martin/FreeDOS/isolinux/fdboot.img: x86 boot sector, FREE-DOS BEta 0.9 Bootloader KERNEL.SYS, code offset 0x40, OEM-ID "FreeDOS ", sectors/cluster 2, root entries 112, sectors 720 (volumes

Hi, I am aware that it is impossible to netboot ISO files through pxelinux/memdisk and that there are multiple reasons for not even attempting it (like the operating system which will try to access a physical optical drive through its own drivers anyway, BIOS issues etc.). When people ask questions regarding ISO support in pxelinux/memdisk, they're mostly told to convert the ISO into a

I am trying to install CentOS from an ISO image file but the installer does not see a CD-ROM drive. The VNC viewer works but the CentOS installer indicates "Unable to find any devices of the type needed for this installation type." Then it prompts with "[Select driver] [Use a driver disk] [Back]". I have tried several variations of the "disk" paramater, all

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

Hi all, This small patch enables you to loopback disk image files on readonly nfs filesystem on some system. When we losetup a file on readonly nfs filesystem, it fails with: # losetup /dev/loop7 /data/vm/xen_el5_i386_para/system.raw /data/vm/xen_el5_i386_para/system.raw: Permission denied New version of losetup has add a "-r" option for readonly loop, which Linux kernel has

Hi all. I''ve got a domU that exists in a sparse file image, I''d like to now use this on a physical partition (loopback performance issues). Is there an a easy way to do this ? Thanks Stuart _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Hi list! I'm trying to make a hd image with can boot from memdisk over PXE. So this is what i did: - Created a new VM [VMware] -Installed DOS on a 100MB HD from a floppy -bootet Linux over PXE [DamnSmallLinux] -in terminal: dd if=/dev/hda of=dos.img This image [dos.img] isn't working! Memdisk loads the Image and boots the HD! The error message is something like this: I/O Device

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:/ #

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

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

Hi, I get the following error when I try to mount lustre on the clients. Permanent disk data: Target: lustre-OSTffff Index: unassigned Lustre FS: lustre Mount type: ldiskfs Flags: 0x72 (OST needs_index first_time update ) Persistent mount opts: errors=remount-ro,extents,mballoc Parameters: mgsnode=164.107.119.231 at tcp sh: losetup: command not found mkfs.lustre: error 32512 on losetup:

Thanks for Remko for his help to solve the fractional cylinder problem. But there is the second problem, the boot disk failure (see below << [B]) ... command line: initrd=disk.img harddisk c=2 h=256 s=63 BOOT_IMAGE=memdisk Disk is hard disk, 16128K CHS=2/256/63 <<<< [A] ... Loading boot sector... booting... SYSLINUX 2.04 welcome! boot: 1 [single dot]

How do I mount a partition that is in an image file? I have a file called centos.img that has 3 partitions in the file. I need to copy data to the third partition on that image file. I have seen things about a loop back device (which is fine) but then it talked about an offset parameter and I dont know what that is or more importantly what number to use. I hope I'm on the right track. How

Hi, I''ve been trying to boot from a RHEL4 install iso without much luck (the xen way). The Host is: RHEL 5.1 xen-3.0.3-41.el5 Here is my guest config: # -*- mode: python; -*- #============================================================================ # Python configuration setup for ''xm create''. # This script sets the parameters used when a domain is created using

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