Re: RFH: zfs-fuse
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Mike...
There you go, I hope it can be of some help.
Paolo.
sun:/tmp# uname -a
Linux sun 2.6.26-1-sparc64 #1 Mon Dec 15 17:04:34 UTC 2008 sparc64 GNU/Linux
sun:/tmp# dd of=foo bs=1024 count=0 seek=500000
0+0 records in
0+0 records out
0 bytes (0 B) copied, 7.4265e-05 s, 0.0 kB/s
sun:/tmp# zpool create foo $(pwd)/foo
sun:/tmp# zfs create foo/bar
sun:/tmp# touch /foo/bar/baz
sun:/tmp# ls -l /foo/bar/baz
- -rw-r--r-- 1 root root 0 2008-12-29 03:49 /foo/bar/baz
sun:/tmp# zpool destroy foo
sun:/tmp# rm foo
Mike Hommey wrote:
> Hi,
>
> I'm currently giving a try to zfs-fuse (ITP #419746) and it has support
> for sparc64. My understanding of the debian port is that it is mostly a
> 32 bits port, with a 64 bits kernel. The zfs-fuse build scripts only
> deal with sparc64 as returned by uname -m, but builds as 32-bits
> application with the current toolchain. Also, it builds with
> -mcpu=ultrasparc, which I'm unsure is allowed for the debian sparc port
> (as well as expecting uname -m to always return sparc64), but the code
> does use ultrasparc specific opcodes, most notably "cas".
>
> For those interested in the code, they can lookup
> src/lib/libsolcompat/sparc64/atomic.S which contains most sparc specific
> assembly in http://prdownload.berlios.de/zfs-fuse/zfs-fuse-0.5.0.tar.bz2
>
> I'm not sure the resulting package works properly either (as I'm unable
> to test it on porter machines), so if someone could check out
> http://people.debian.org/~glandium/zfs-fuse_0.5.0-1_sparc.deb
> and see if the following sequence of commands work (as root):
> dd of=foo bs=1024 count=0 seek=500000
> zpool create foo $(pwd)/foo
> zfs create foo/bar
> touch /foo/bar/baz
> ls /foo/bar/baz
>
> You can cleanup with:
> zpool destroy foo
> rm foo
>
> before removing the package.
>
> Thanks for your help.
>
> Mike
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAklX2l8ACgkQqAaEpZvj+VOZhQCfTBe8qJMgph47cdcC1qlktDsQ
oi8AoJgf9S8oErI+pi2QUnJ+xMmYUo02
=Yjxm
-----END PGP SIGNATURE-----
Reply to: