<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Announcing vmfs-tools version 0.1.0</title>
	<atom:link href="http://glandium.org/blog/?feed=rss2&#038;p=347" rel="self" type="application/rss+xml" />
	<link>http://glandium.org/blog/?p=347</link>
	<description>glandium.org</description>
	<lastBuildDate>Sun, 05 Sep 2010 12:27:46 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Tommy</title>
		<link>http://glandium.org/blog/?p=347&#038;cpage=1#comment-13273</link>
		<dc:creator>Tommy</dc:creator>
		<pubDate>Thu, 18 Jun 2009 12:34:45 +0000</pubDate>
		<guid isPermaLink="false">http://glandium.org/blog/?p=347#comment-13273</guid>
		<description>Hi glandium,

It worked! Thank you for explaining it for me.

For reference to others:
nas:~# modprobe fuse
nas:~# losetup -r /dev/loop0 /mnt/iscsi.img
nas:~# kpartx -a -v /dev/loop0
nas:~# vmfs-fuse /dev/mapper/loop0p1 /mnt/iscsi/</description>
		<content:encoded><![CDATA[<p>Hi glandium,</p>
<p>It worked! Thank you for explaining it for me.</p>
<p>For reference to others:<br />
nas:~# modprobe fuse<br />
nas:~# losetup -r /dev/loop0 /mnt/iscsi.img<br />
nas:~# kpartx -a -v /dev/loop0<br />
nas:~# vmfs-fuse /dev/mapper/loop0p1 /mnt/iscsi/</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: glandium</title>
		<link>http://glandium.org/blog/?p=347&#038;cpage=1#comment-13254</link>
		<dc:creator>glandium</dc:creator>
		<pubDate>Wed, 17 Jun 2009 15:23:58 +0000</pubDate>
		<guid isPermaLink="false">http://glandium.org/blog/?p=347#comment-13254</guid>
		<description>Tommy, if you&#039;re using a 2.6.x linux kernel, you can setup a loopback device with losetup and then use kpartx (from multipath-tools) to get devices mapping the partitions in the loopback device.</description>
		<content:encoded><![CDATA[<p>Tommy, if you&#8217;re using a 2.6.x linux kernel, you can setup a loopback device with losetup and then use kpartx (from multipath-tools) to get devices mapping the partitions in the loopback device.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: chris</title>
		<link>http://glandium.org/blog/?p=347&#038;cpage=1#comment-13251</link>
		<dc:creator>chris</dc:creator>
		<pubDate>Wed, 17 Jun 2009 12:14:12 +0000</pubDate>
		<guid isPermaLink="false">http://glandium.org/blog/?p=347#comment-13251</guid>
		<description>Hi Tommy,

Try with offset=65536</description>
		<content:encoded><![CDATA[<p>Hi Tommy,</p>
<p>Try with offset=65536</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tommy</title>
		<link>http://glandium.org/blog/?p=347&#038;cpage=1#comment-13246</link>
		<dc:creator>Tommy</dc:creator>
		<pubDate>Wed, 17 Jun 2009 07:42:39 +0000</pubDate>
		<guid isPermaLink="false">http://glandium.org/blog/?p=347#comment-13246</guid>
		<description>Can anyone tell me what the offset should be on my loopback device?

I&#039;ve created a 512MB file with dd, connected it via iSCSI to my ESXi server, created the VMFS and put up some test files.

If i try directly on the file:
nas:~# vmfs-fuse /mnt/iscsi.img
VMFS VolInfo: invalid magic number 0x00000000
VMFS: Unable to read volume information
Unable to open device/file &quot;/mnt/iscsi.img&quot;.

This obviously doesn&#039;t work. Then I tried to create a loopback device, but i don&#039;t know the offset.

losetup -o ???? -r /dev/loop1 /mnt/iscsi.img

Can anyone help me here?

Thank you in advance. :)
/Tommy</description>
		<content:encoded><![CDATA[<p>Can anyone tell me what the offset should be on my loopback device?</p>
<p>I&#8217;ve created a 512MB file with dd, connected it via iSCSI to my ESXi server, created the VMFS and put up some test files.</p>
<p>If i try directly on the file:<br />
nas:~# vmfs-fuse /mnt/iscsi.img<br />
VMFS VolInfo: invalid magic number 0&#215;00000000<br />
VMFS: Unable to read volume information<br />
Unable to open device/file &#8220;/mnt/iscsi.img&#8221;.</p>
<p>This obviously doesn&#8217;t work. Then I tried to create a loopback device, but i don&#8217;t know the offset.</p>
<p>losetup -o ???? -r /dev/loop1 /mnt/iscsi.img</p>
<p>Can anyone help me here?</p>
<p>Thank you in advance. :)<br />
/Tommy</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brien</title>
		<link>http://glandium.org/blog/?p=347&#038;cpage=1#comment-12938</link>
		<dc:creator>Brien</dc:creator>
		<pubDate>Wed, 03 Jun 2009 22:57:37 +0000</pubDate>
		<guid isPermaLink="false">http://glandium.org/blog/?p=347#comment-12938</guid>
		<description>This would be a very nice replacement for VCB dumping and then doing the loopback offset mount hack.  I guess getting to the VMFS is the first step, and then seeing if we can mount the snapshot file to perform the backup.  VMware is going to love that potentially naughty systems can now access the VMFS :-)</description>
		<content:encoded><![CDATA[<p>This would be a very nice replacement for VCB dumping and then doing the loopback offset mount hack.  I guess getting to the VMFS is the first step, and then seeing if we can mount the snapshot file to perform the backup.  VMware is going to love that potentially naughty systems can now access the VMFS :-)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
