Re: [uml-user] COW files and block devices

2005-08-05 Thread Jason Clark
BTW, Im a bonehead and forgot to derefernce the pointer for those offset vars. The actual values are below. Im looking into it. [EMAIL PROTECTED]:~/tools/moo# ./uml_mkcow -f /dev/md1 /dev/md2 cow bitmap lseek failed : errno = 22 bitmap_offset_out 8192, data_offset_out 1232896 write_cow_header:

Re: [uml-user] COW files and block devices

2005-08-05 Thread Jason Clark
will do, thanks for the pointers. -- Jason The place where you made your stand never mattered. Only that you were there.. And still on your feet. On Fri, 5 Aug 2005, Blaisorblade wrote: On Thursday 04 August 2005 22:02, Jason Clark wrote: md1 and md2 are both 5 gig. md2 will eventually b

Re: [uml-user] COW files and block devices

2005-08-05 Thread Blaisorblade
On Thursday 04 August 2005 22:02, Jason Clark wrote: > md1 and md2 are both 5 gig. > md2 will eventually be much smaller. Guess it won't, it must be 5G long. On normal files you can use sparse ones, not on block devices... and if that seems stupid, yeah, COW files were designed for sparse files

Re: [uml-user] COW files and block devices

2005-08-04 Thread Jason Clark
md1 and md2 are both 5 gig. md2 will eventually be much smaller. Changing lseek to lseek64 in cow_sys.h results in the same error. [EMAIL PROTECTED]:~# uml_mkcow -f /dev/md1 /dev/md2 cow bitmap lseek failed : errno = 22 write_cow_header: Invalid argument Here is the results of the same command

Re: [uml-user] COW files and block devices

2005-08-04 Thread Blaisorblade
On Wednesday 03 August 2005 23:01, Jason Clark wrote: > Here is the output trying to use /dev/md1 as my cow file and > /mnt/cow/rootfs.cow as my backing file > > [EMAIL PROTECTED]:/mnt# linux ubd0=/dev/md1,/mnt/cow/rootfs.cow > ... > [42949373.53] Console initialized on /dev/tty0 > [42949373.53

Re: [uml-user] COW files and block devices

2005-08-03 Thread Jason Clark
Here is the output trying to use /dev/md1 as my cow file and /mnt/cow/rootfs.cow as my backing file [EMAIL PROTECTED]:/mnt# linux ubd0=/dev/md1,/mnt/cow/rootfs.cow ... [42949373.53] Console initialized on /dev/tty0 [42949373.53] Initializing software serial port version 1 [42949373.57000

Re: [uml-user] COW files and block devices

2005-08-03 Thread Jeff Dike
On Wed, Aug 03, 2005 at 02:23:58PM -0500, Jason Clark wrote: > Neither of these seem to work, just get a kernel panic about not being > able to find a rootfs. THe backing file will boot on its own as will the > md0 device, but I cant seem to get the cow file relationship working. Any > thought

[uml-user] COW files and block devices

2005-08-03 Thread Jason Clark
I have been using linux software RAID block devices as my files for my UML hosts. Instead of using linux ubd0=file.fs I use linux ubd0=/dev/md0 The performance increase is outstanding, but I have run into one small snag. I am trying to migrate over to using COW files on a fresh server, but I