Hi everyone,
Recently an article was posted on LinuxWorld about ZFS-FUSE. See also the Slashdot article.
In case you're wondering why the ZFS-FUSE website is down, it's because I have been without Internet access since Monday. I never thought I'd say this again but I'm using a 33Kb dial-up connection right now (I think this might be slower than this)..
As a consequence, the Mercurial repositories are also down, and I might not receive some of your emails..
On another note, there has been recent reports of corruption in Raid-Z pools, so please backup your data before trying ZFS-FUSE!
skip to main |
skip to sidebar
This blog is about the Google Summer of Code project "ZFS filesystem for FUSE/Linux"
14 comments:
Started using zfs through fuse for backup storage and I am constantly impressed by it. Good going - well done!
Achei muito interessante o ZFS, estou interessado sobre este filesystem.
Queria mais informações, saber como utiliza-lo em conjunto com o linux.
Quais são as principais falhas, e tudo mais.
Ta em portugues, mais sei que tu é de portugal, precisa exercitar o portugues.
Grato
anónimo: Veja a página principal em http://www.wizy.org/wiki/ZFS_on_FUSE ou junte-se ao grupo de discussão em http://groups.google.com/group/zfs-fuse/about
Maybe with such an important project, someone could sponsor you a better connection to the Internet!
John, I definitely agree.
Let me know if you need it hosted still. Just email me and we can either host it off our T1 or on one of our hosted servers.
-Mike
Please post some status updates!
i'm trying zfs-fuse (0.40b1)on an
usb hd (20gb), but after i have
copied some files, i receive this
errors:
[pi@spock ~]$ sudo zpool status hd20 -v
pool: hd20
state: ONLINE
status: One or more devices has experienced an error resulting in data
corruption. Applications may be affected.
action: Restore the file in question if possible. Otherwise restore the
entire pool from backup.
see: http://www.sun.com/msg/ZFS-8000-8A
scrub: scrub completed with 3 errors on Sat Sep 8 23:39:30 2007
config:
NAME STATE READ WRITE CKSUM
hd20 ONLINE 0 0 12
disk/by-id/usb-HTC42602_0G7AT00-0:0 ONLINE 0 0 12
*** glibc detected *** zpool: double free or corruption (!prev): 0x080917c8 ***
======= Backtrace: =========
/lib/libc.so.6[0xb7e2fc06]
/lib/libc.so.6(cfree+0x89)[0xb7e318c9]
zpool[0x8060bee]
zpool[0x804cea5]
zpool[0x804a2af]
zpool[0x804a4ff]
zpool[0x804e26a]
zpool[0x804dbec]
/lib/libc.so.6(__libc_start_main+0xe0)[0xb7ddff90]
zpool[0x804a091]
======= Memory map: ========
08048000-08075000 r-xp 00000000 03:03 140908 /usr/sbin/zpool
08075000-08076000 rw-p 0002d000 03:03 140908 /usr/sbin/zpool
08076000-08097000 rw-p 08076000 00:00 0 [heap]
b7a00000-b7a21000 rw-p b7a00000 00:00 0
b7a21000-b7b00000 ---p b7a21000 00:00 0
b7be5000-b7bef000 r-xp 00000000 03:03 68751 /usr/lib/libgcc_s.so.1
b7bef000-b7bf0000 rw-p 00009000 03:03 68751 /usr/lib/libgcc_s.so.1
b7c15000-b7dc7000 r--p 00000000 03:03 68629 /usr/lib/locale/locale-archive
b7dc7000-b7dca000 rw-p b7dc7000 00:00 0
b7dca000-b7ef5000 r-xp 00000000 03:03 500845 /lib/libc-2.6.1.so
b7ef5000-b7ef6000 r--p 0012b000 03:03 500845 /lib/libc-2.6.1.so
b7ef6000-b7ef8000 rw-p 0012c000 03:03 500845 /lib/libc-2.6.1.so
b7ef8000-b7efb000 rw-p b7ef8000 00:00 0
b7efb000-b7efd000 r-xp 00000000 03:03 500813 /lib/libdl-2.6.1.so
b7efd000-b7eff000 rw-p 00001000 03:03 500813 /lib/libdl-2.6.1.so
b7eff000-b7f22000 r-xp 00000000 03:03 500842 /lib/libm-2.6.1.so
b7f22000-b7f24000 rw-p 00022000 03:03 500842 /lib/libm-2.6.1.so
b7f24000-b7f37000 r-xp 00000000 03:03 500817 /lib/libpthread-2.6.1.so
b7f37000-b7f39000 rw-p 00013000 03:03 500817 /lib/libpthread-2.6.1.so
b7f39000-b7f3c000 rw-p b7f39000 00:00 0
b7f60000-b7f61000 rw-p b7f60000 00:00 0
b7f61000-b7f62000 r-xp b7f61000 00:00 0 [vdso]
b7f62000-b7f7c000 r-xp 00000000 03:03 500849 /lib/ld-2.6.1.so
b7f7c000-b7f7d000 r--p 00019000 03:03 500849 /lib/ld-2.6.1.so
b7f7d000-b7f7e000 rw-p 0001a000 03:03 500849 /lib/ld-2.6.1.so
bfc5f000-bfc74000 rw-p bfc5f000 00:00 0 [stack]
thanks !
Tuxie:
I will post a status update next Wednesday (2007-09-12).
Anonymous:
That bug has already been fixed in the latest development code - please try the latest mercurial revision (see instructions in the ZFS-FUSE website).
it work ok now, thanks !
'problem' with removable devices ?
ok, we have 2 usb-hd,sda and sdb,
i plug sda and i create a pool with the command:
zpool create usb1 /dev/disk/by-id/usb-HTC42602_0G7AT00-0:0
now if i export the pool usb1,zfs store ONLY sda instead of the unique id "disk/by-id/usb-HTC42602_0G7AT00-0:0"
(you can et this id whith "udevinfo --query all --name /dev/sda")
the problem is that if i plug other usb disk and than sda and than i try to import the pool usb1, it fail because it try to import 'sda' only and not the entire unique id that i have used to create the pool.
I thin zfs must store the unique id or i think there are problems with removable device.
or am i doing something wrong ? :D
(sorry for my bad english)
"zfs umount -a" try to umount also 'encfs'
mounte partitions.
and obiouvsly "zfs mount" show also encfs mounted partition(s)
To the last 2 anonymous comments - yes, known bug :(
To the disk by-id problem:
I'm not sure if I'm following you. Can you please provide a bug report with step-by-step instructions?
FYI, if you use "zpool import", it will by default scan all the devices in the top-level /dev directory for pools, and so it will use /dev/sda, /dev/sdb, etc..
If you want to import the pool by id, you can use "zpool import -d /dev/disk/by-id"
Post a Comment