Re: ZFS v28 is ready for wider testing.
2011/2/2 Christopher Olsen cwol...@itbuildersinc.com: Pawel, I have the latest current source and I patched with your zfs patch from zfs_20101213.patch and I am having trouble compiling my kernel.. Is there a more current patch to work with the latest –CURRENT source? An answer from yesterday (working for me too) : http://docs.freebsd.org/cgi/getmsg.cgi?fetch=184930+0+current/freebsd-current -- Olivier Smedts _ ASCII ribbon campaign ( ) e-mail: oliv...@gid0.org - against HTML email vCards X www: http://www.gid0.org - against proprietary attachments / \ Il y a seulement 10 sortes de gens dans le monde : ceux qui comprennent le binaire, et ceux qui ne le comprennent pas. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ZFS v28 is ready for wider testing.
2010/8/31 Pawel Jakub Dawidek p...@freebsd.org: Hello. I'd like to give you ZFS v28 for testing. If you are neither brave nor mad, you can stop here. The patchset is very experimental. It can eat your cookie and hurt your teddy bear, so be warned. Don't try it for anything except testing. This patchset is also a message we, as the FreeBSD project, would like to send to our users: Eventhough OpenSolaris is dead, the ZFS file system is going to stay in FreeBSD. At this point we have quite a few developers involved in ZFS on FreeBSD as well as serveral companies. We are also looking forward to work with IllumOS. So, what this new ZFS brings? - Data deduplication. Read more here: http://blogs.sun.com/bonwick/entry/zfs_dedup - Triple parity RAIDZ (RAIDZ3). Read more here: http://dtrace.org/blogs/ahl/2009/07/21/triple-parity-raid-z/ - zfs diff. Read more here: http://arc.opensolaris.org/caselog/PSARC/2010/105/20100328_tim.haley - zpool split. Read more here: http://arc.opensolaris.org/caselog/PSARC/2009/511/20090924_mark.musante - Snapshot holds. Read more here: http://arc.opensolaris.org/caselog/PSARC/2009/297/20090511_chris.kirby - zpool import -F. Allows to rewind corrupted pool to earlier transaction group. - Possibility to import pool in read-only mode. And much, much more, including plenty of preformance improvements and bug fixes. So test whatever you can and report back. Look for regressions, strange behaviour, missing features, deadlocks, livelocks, preformance degradation, etc. The boot code is not updated at all, so booting off of ZFS doesn't currently work. The patch is against today's FreeBSD HEAD. The patch enables (in sys/modules/zfs/Makefile) ZFS internal debugging, please don't turn it off. Also, compile your kernel with the following options: options KDB options DDB options INVARIANTS options INVARIANT_SUPPORT options WITNESS options WITNESS_SKIPSPIN options DEBUG_LOCKS options DEBUG_VFS_LOCKS Ignore all the LOR (Lock Order Reversal) reports from WITNESS. There will be plenty of those, and you'll desperately want to report them, but please don't. The best way to report a problem is to answer to this e-mail with as short as possible procedure of how to reproduce it and debugging info. I'd prefer textdump if possible. Below you can find quick procedure how to setup textdumps: Choose spare/swap disk/partition in your system, let's say it is /dev/ad0s1b. Add the following line to /etc/fstab: /dev/ad0s1b none swap sw 0 0 Add the following line to /etc/rc.conf: ddb_enable=YES Run the following commands: # /etc/rc.d/swap1 start # /etc/rc.d/dumpon start # /etc/rc.d/ddb start This will setup swap, mark it as dump device and setup some DDB scripts. Or you can just reboot. Now when your system panic or deadlock, enter DDB and call the following command: ddb run kdb.enter.panic It will execute all the commands I need, dump them in text format to your swap device and reboot machine. After the reboot, you should find textdump.tar.0 file in /var/crash/ directory. This is the debug info I need. End of textdumps procedure. Ok, now that I know you read everything carefully, here is the patch: http://people.freebsd.org/~pjd/patches/zfs_20100831.patch.bz2 Hello, Any status update on this ? I regularly check http://people.freebsd.org/~pjd/patches/ to see if there's an updated version of your patch. 2 months old is quite a bit for -CURRENT, which often receives commits on zfsco parts. Thanks for all your work on FreeBSD (not only ZFS). Good luck! : -- Pawel Jakub Dawidek http://www.wheelsystems.com p...@freebsd.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! -- Olivier Smedts _ ASCII ribbon campaign ( ) e-mail: oliv...@gid0.org - against HTML email vCards X www: http://www.gid0.org - against proprietary attachments / \ Il y a seulement 10 sortes de gens dans le monde : ceux qui comprennent le binaire, et ceux qui ne le comprennent pas. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ZFS v28 is ready for wider testing.
On Wed, Nov 03, 2010 at 07:28:15PM +0100, Olivier Smedts wrote: http://people.freebsd.org/~pjd/patches/zfs_20100831.patch.bz2 Hello, Any status update on this ? I regularly check http://people.freebsd.org/~pjd/patches/ to see if there's an updated version of your patch. 2 months old is quite a bit for -CURRENT, which often receives commits on zfsco parts. Thanks for all your work on FreeBSD (not only ZFS). It took a while, but I should have something new shortly. I recently finished boot support for v28 (the most missing feature in the previous patch?) and will work on new patch soon. I'm heading to meetBSD California tomorrow and I'll be back in a week, so nothing will happen till then for sure. -- Pawel Jakub Dawidek http://www.wheelsystems.com p...@freebsd.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! pgpPnD9csrFCZ.pgp Description: PGP signature
Re: ZFS v28 is ready for wider testing.
On 09/02/10 17:48, Pawel Jakub Dawidek wrote: On Tue, Aug 31, 2010 at 11:59:15PM +0200, Pawel Jakub Dawidek wrote: [...] Ok, now that I know you read everything carefully, here is the patch: http://people.freebsd.org/~pjd/patches/zfs_20100831.patch.bz2 Now it is even easier to test new ZFS! :) Here you can find VirtualBox Appliance (113MB) with FreeBSD 9-CURRENT and ZFSv28: http://people.freebsd.org/~pjd/misc/FreeBSD9_ZFSv28_0.1.tgz Untar it, import it (zfsv28.ovf) to VirtualBox and have fun. Wheee! Is there anyway to simulate a disk failure on VBox? Does one simply rm/mv the .vmdk files on the host system? Inside the virtual machine I'm unable to get camcontrol to do anything (the SATA drives are AHCI so we don't want atacontrol correct?) that would simulate this. Great work putting this together. Thanks. cheers ps: I'm pretty sure it worked once but now I am not having much luck with zpool split. Possibly a PEBKAC. I think there are manual page patches for all the new features include with each of Sunoracle's PSARCs but they don't all appear on the manual pages included with the vbox image (??) ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ZFS v28 is ready for wider testing.
Wiadomość napisana przez Anonymous w dniu 2010-09-05, o godz. 20:56: Pawel Jakub Dawidek p...@freebsd.org writes: Hello. I'd like to give you ZFS v28 for testing. If you are neither brave nor mad, you can stop here. [...] So test whatever you can and report back. Look for regressions, strange behaviour, I wonder why new files tend to have different ACLs than old ones. $ ls -lh foo -rw-r--r-- 1 holo holo17K Aug 19 11:43 foo $ cp foo bar $ ls -lh bar -rw-r--r--+ 1 holo holo17K Sep 5 21:20 bar $ getfacl foo bar # file: foo # owner: holo # group: holo owner@:--x---:--:deny owner@:rw-p---A-W-Co-:--:allow group@:-wxp--:--:deny group@:r-:--:allow everyone@:-wxp---A-W-Co-:--:deny everyone@:r-a-R-c--s:--:allow See http://arc.opensolaris.org/caselog/PSARC/2010/029/20100126_mark.shellenbaum. -- If you cut off my head, what would I say? Me and my head, or me and my body? ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ZFS v28 is ready for wider testing.
The atomic.h patch does not apply anymore and buildworld fails without it. At work so can't post results On Sep 6, 2010 6:09 PM, Martin Matuska m...@freebsd.org wrote: To avoid user and developer confusion, my patch was just a chain of pjd's patch + pjd's atomic.h fix + my v19 boot patch. I have removed (= split) the chained patch in my posting and altered my blog article with updated build instructions that actually just summarize what has been written on this list. Thanks for understanding! Dňa 6. 9. 2010 13:50, Martin Matuska wrote / napísal(a): Hi everyone, I have put together a slightly improved patch of Pawel's that compiles correctly and supports booting from ZFS v19 pools. You can download the patch here: http://people.freebsd.org/~mm/patches/zfs/head-zfs-v28-20100831.patch For users who don't want to compile I have created a mfsBSD ISO image with a zfs-only install of 9-CURRENT-amd64: http://mfsbsd.vx.sk/iso/mfsbsd-se-head-zfsv28-amd64.iso You can read more about all of this here: http://blog.vx.sk/archives/9-Help-testing-ZFS-v28-in-FreeBSD.html More information about ZFS pool and filesystem versions: http://blog.vx.sk/archives/4-ZFS-pool-and-filesystem-versions.html Thanks to everybody participating in testing, mm ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ZFS v28 is ready for wider testing.
Hi everyone, I have put together a slightly improved patch of Pawel's that compiles correctly and supports booting from ZFS v19 pools. You can download the patch here: http://people.freebsd.org/~mm/patches/zfs/head-zfs-v28-20100831.patch For users who don't want to compile I have created a mfsBSD ISO image with a zfs-only install of 9-CURRENT-amd64: http://mfsbsd.vx.sk/iso/mfsbsd-se-head-zfsv28-amd64.iso You can read more about all of this here: http://blog.vx.sk/archives/9-Help-testing-ZFS-v28-in-FreeBSD.html More information about ZFS pool and filesystem versions: http://blog.vx.sk/archives/4-ZFS-pool-and-filesystem-versions.html Thanks to everybody participating in testing, mm ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ZFS v28 is ready for wider testing.
To avoid user and developer confusion, my patch was just a chain of pjd's patch + pjd's atomic.h fix + my v19 boot patch. I have removed (= split) the chained patch in my posting and altered my blog article with updated build instructions that actually just summarize what has been written on this list. Thanks for understanding! Dňa 6. 9. 2010 13:50, Martin Matuska wrote / napísal(a): Hi everyone, I have put together a slightly improved patch of Pawel's that compiles correctly and supports booting from ZFS v19 pools. You can download the patch here: http://people.freebsd.org/~mm/patches/zfs/head-zfs-v28-20100831.patch For users who don't want to compile I have created a mfsBSD ISO image with a zfs-only install of 9-CURRENT-amd64: http://mfsbsd.vx.sk/iso/mfsbsd-se-head-zfsv28-amd64.iso You can read more about all of this here: http://blog.vx.sk/archives/9-Help-testing-ZFS-v28-in-FreeBSD.html More information about ZFS pool and filesystem versions: http://blog.vx.sk/archives/4-ZFS-pool-and-filesystem-versions.html Thanks to everybody participating in testing, mm ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ZFS v28 is ready for wider testing.
Pawel Jakub Dawidek p...@freebsd.org writes: Hello. I'd like to give you ZFS v28 for testing. If you are neither brave nor mad, you can stop here. [...] So test whatever you can and report back. Look for regressions, strange behaviour, I wonder why new files tend to have different ACLs than old ones. $ ls -lh foo -rw-r--r-- 1 holo holo17K Aug 19 11:43 foo $ cp foo bar $ ls -lh bar -rw-r--r--+ 1 holo holo17K Sep 5 21:20 bar $ getfacl foo bar # file: foo # owner: holo # group: holo owner@:--x---:--:deny owner@:rw-p---A-W-Co-:--:allow group@:-wxp--:--:deny group@:r-:--:allow everyone@:-wxp---A-W-Co-:--:deny everyone@:r-a-R-c--s:--:allow # file: bar # owner: holo # group: holo owner@:rw-p--aARWcCos:--:allow group@:r-a-R-c--s:--:allow everyone@:r-a-R-c--s:--:allow $ zfs get aclinherit h$PWD NAME PROPERTYVALUE SOURCE h/home/holo aclinherit restricted default Note, I didn't upgrade the pool to v28. missing features, deadlocks, livelocks, preformance degradation, etc. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ZFS v28 is ready for wider testing.
On 09/03/2010 13:02, Pawel Jakub Dawidek wrote: On Fri, Sep 03, 2010 at 04:50:44PM +0100, Peter Molnar, BSD wrote: Hi, I would like to try ZFS + VirtualBox but I have got problems: 1) Linux 2.6.32-24-generic #42-Ubuntu SMP Fri Aug 20 14:21:58 UTC 2010 x86_64 GNU/Linux I tried import that file in my VirtualBox but I have got error: Failed to import appliance. /home/peter/FreeBSD/zfsv28.ovf Too many IDE controllers in OVF; import facility only supports one. Which VirtualBox version do you use? 3.2.8? Exporting appliances is a bit broken (if you have more than one disk, it will point all disks at the last one from configuration), so I had to edit .ovf file manually to fix this. Maybe I messed something up, but I was able to successfully import it before publishing it. PS. I waited for so long for decent virtualization software for FreeBSD, and I must say VirtualBox is really great, and free, and open-source Are you reading this, VMWare? They will only read it if it comes with a disclaimer and they're license attached to the top along with a contract signed by you so when they disagree with it they can hand you a pink-slip with they're license attached to the top. As for VirtualBox, which is a Sun thing, gone Oratorically wrong... How long does anyone expect this technology to stick around?. -- jhell,v ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ZFS v28 is ready for wider testing.
I got this compile error agains todays current patched with patch -p0 -E /usr/src9/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_ioctl.c: In function 'zfs_ioc_recv': /usr/src9/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_ioctl.c:3586: error: too few arguments to function 'getf' cc1: warnings being treated as errors /usr/src9/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_ioctl.c:3761: warning: passing argument 1 of 'releasef' makes pointer from integer without a cast /usr/src9/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_ioctl.c: In function 'zfs_ioc_send': /usr/src9/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_ioctl.c:3831: error: too few arguments to function 'getf' /usr/src9/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_ioctl.c:3844: warning: passing argument 1 of 'releasef' makes pointer from integer without a cast /usr/src9/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_ioctl.c: In function 'zfs_ioc_diff': /usr/src9/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_ioctl.c:4356: error: too few arguments to function 'getf' /usr/src9/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_ioctl.c:4369: warning: passing argument 1 of 'releasef' makes pointer from integer without a cast /usr/src9/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_ioctl.c: In function 'zfsdev_ioctl': /usr/src9/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_ioctl.c:4930: error: 'FKIOCTL' undeclared (first use in this function) *** Error code 1 /usr/src9/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_onexit.c: In function 'zfs_onexit_fd_hold': /usr/src9/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_onexit.c:127: error: too few arguments to function 'getf' cc1: warnings being treated as errors /usr/src9/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_onexit.c: In function 'zfs_onexit_fd_rele': /usr/src9/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_onexit.c:145: warning: passing argument 1 of 'releasef' makes pointer from integer without a cast *** Error code 1 2 errors *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ZFS v28 is ready for wider testing.
On 09/02/2010 04:55, Rob Farmer wrote:
I tried applying the patch to r212087 to rule out recent changes to
dtrace, but it made no difference. I used patch -E -p0 patch.
Hi Rob,
I see that in your build error are a bunch of things to do with atomic.h
and I recalled a patch from pjd@ on current@ that he sent in the same
thread. I attached the downloaded patch. Maybe you can write back and
site if it helped at all so people have a reference.
Regards,
--
jhell,v
--- sys/cddl/compat/opensolaris/sys/atomic.h
+++ sys/cddl/compat/opensolaris/sys/atomic.h
@@ -39,10 +39,9 @@
#ifndef __LP64__
extern void atomic_add_64(volatile uint64_t *target, int64_t delta);
extern void atomic_dec_64(volatile uint64_t *target);
-extern void *atomic_cas_ptr(volatile void *target, void *cmp, void *newval);
#endif
#ifndef __sparc64__
-extern uint64_t atomic_cas_32(volatile uint32_t *target, uint32_t cmp,
+extern uint32_t atomic_cas_32(volatile uint32_t *target, uint32_t cmp,
uint32_t newval);
extern uint64_t atomic_cas_64(volatile uint64_t *target, uint64_t cmp,
uint64_t newval);
@@ -119,21 +118,19 @@
}
#ifndef COMPAT_32BIT
-#if defined(__LP64__)
+#ifdef __LP64__
static __inline void *
atomic_cas_ptr(volatile void *target, void *cmp, void *newval)
{
- return ((void *)atomic_cas_64((volatile uint64_t *)target,
(uint64_t)cmp,
- (uint64_t)newval));
+ return ((void *)atomic_cas_64(target, (uint64_t)cmp, (uint64_t)newval));
}
#else
static __inline void *
atomic_cas_ptr(volatile void *target, void *cmp, void *newval)
{
- return ((void *)atomic_cas_32((volatile uint64_t *)target,
(uint64_t)cmp,
- (uint64_t)newval));
+ return ((void *)atomic_cas_32(target, (uint32_t)cmp, (uint32_t)newval));
}
#endif
-#endif
+#endif /* !COMPAT_32BIT */
#endif /* !_OPENSOLARIS_SYS_ATOMIC_H_ */
signature.asc
Description: OpenPGP digital signature
Re: ZFS v28 is ready for wider testing.
On Thu, Sep 2, 2010 at 23:57, jhell jh...@dataix.net wrote: On 09/02/2010 04:55, Rob Farmer wrote: I tried applying the patch to r212087 to rule out recent changes to dtrace, but it made no difference. I used patch -E -p0 patch. Hi Rob, I see that in your build error are a bunch of things to do with atomic.h and I recalled a patch from pjd@ on current@ that he sent in the same thread. I attached the downloaded patch. Maybe you can write back and site if it helped at all so people have a reference. Yes, it worked. Since this is just a testing thing and pjd alredy knew about the problem and seemed confident about the solution I didn't bother to reply. -- Rob Farmer Regards, -- jhell,v ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ZFS v28 is ready for wider testing.
On 02/09/10 22:48, Pawel Jakub Dawidek wrote:
On Tue, Aug 31, 2010 at 11:59:15PM +0200, Pawel Jakub Dawidek wrote:
[...]
Ok, now that I know you read everything carefully, here is the patch:
http://people.freebsd.org/~pjd/patches/zfs_20100831.patch.bz2
Now it is even easier to test new ZFS! :)
Here you can find VirtualBox Appliance (113MB) with
FreeBSD 9-CURRENT and ZFSv28:
http://people.freebsd.org/~pjd/misc/FreeBSD9_ZFSv28_0.1.tgz
Untar it, import it (zfsv28.ovf) to VirtualBox and have fun.
You can log in as root with no password (via virtual console or via SSH).
The system IP address is IP 192.168.56.66/24.
There are 16 ada(4) disks to play with. For example:
zfsv28:root:~# zpool create tank raidz3 ada{0,1,2,3,4,5,6,7} raidz3
ada{8,9,10,11,12,13,14,15}
zfsv28:root:~# zpool status
pool: tank
state: ONLINE
scan: none requested
config:
NAMESTATE READ WRITE CKSUM
tankONLINE 0 0 0
raidz3-0 ONLINE 0 0 0
ada0ONLINE 0 0 0
ada1ONLINE 0 0 0
ada2ONLINE 0 0 0
ada3ONLINE 0 0 0
ada4ONLINE 0 0 0
ada5ONLINE 0 0 0
ada6ONLINE 0 0 0
ada7ONLINE 0 0 0
raidz3-1 ONLINE 0 0 0
ada8ONLINE 0 0 0
ada9ONLINE 0 0 0
ada10 ONLINE 0 0 0
ada11 ONLINE 0 0 0
ada12 ONLINE 0 0 0
ada13 ONLINE 0 0 0
ada14 ONLINE 0 0 0
ada15 ONLINE 0 0 0
errors: No known data errors
Hi,
I would like to try ZFS + VirtualBox but I have got problems:
1) Linux 2.6.32-24-generic #42-Ubuntu SMP Fri Aug 20 14:21:58 UTC 2010
x86_64 GNU/Linux
I tried import that file in my VirtualBox but I have got error:
Failed to import appliance.
/home/peter/FreeBSD/zfsv28.ovf
Too many IDE controllers in OVF; import facility only supports one.
2) I tried to install VirtualBox under 64-bit FreeBSD 9.0-CURRENT #2
[r...@server /usr/ports/emulators/virtualbox-ose]# make
Requires 32-bit libraries installed under /usr/lib32.
Do: cd /usr/src; make build32 install32; ldconfig -v -m -R /usr/lib32
*** Error code 1
Stop in /usr/ports/emulators/virtualbox-ose.
*** Error code 1
Stop in /usr/ports/emulators/virtualbox-ose.
How can I fix that error in FreeBSD?
Peter
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ZFS v28 is ready for wider testing.
On 03/09/10 16:50, Peter Molnar, BSD wrote:
On 02/09/10 22:48, Pawel Jakub Dawidek wrote:
On Tue, Aug 31, 2010 at 11:59:15PM +0200, Pawel Jakub Dawidek wrote:
[...]
Ok, now that I know you read everything carefully, here is the patch:
http://people.freebsd.org/~pjd/patches/zfs_20100831.patch.bz2
Now it is even easier to test new ZFS! :)
Here you can find VirtualBox Appliance (113MB) with
FreeBSD 9-CURRENT and ZFSv28:
http://people.freebsd.org/~pjd/misc/FreeBSD9_ZFSv28_0.1.tgz
Untar it, import it (zfsv28.ovf) to VirtualBox and have fun.
You can log in as root with no password (via virtual console or via
SSH).
The system IP address is IP 192.168.56.66/24.
There are 16 ada(4) disks to play with. For example:
zfsv28:root:~# zpool create tank raidz3 ada{0,1,2,3,4,5,6,7}
raidz3 ada{8,9,10,11,12,13,14,15}
zfsv28:root:~# zpool status
pool: tank
state: ONLINE
scan: none requested
config:
NAMESTATE READ WRITE CKSUM
tankONLINE 0 0 0
raidz3-0 ONLINE 0 0 0
ada0ONLINE 0 0 0
ada1ONLINE 0 0 0
ada2ONLINE 0 0 0
ada3ONLINE 0 0 0
ada4ONLINE 0 0 0
ada5ONLINE 0 0 0
ada6ONLINE 0 0 0
ada7ONLINE 0 0 0
raidz3-1 ONLINE 0 0 0
ada8ONLINE 0 0 0
ada9ONLINE 0 0 0
ada10 ONLINE 0 0 0
ada11 ONLINE 0 0 0
ada12 ONLINE 0 0 0
ada13 ONLINE 0 0 0
ada14 ONLINE 0 0 0
ada15 ONLINE 0 0 0
errors: No known data errors
Hi,
I would like to try ZFS + VirtualBox but I have got problems:
1) Linux 2.6.32-24-generic #42-Ubuntu SMP Fri Aug 20 14:21:58 UTC 2010
x86_64 GNU/Linux
I tried import that file in my VirtualBox but I have got error:
Failed to import appliance.
/home/peter/FreeBSD/zfsv28.ovf
Too many IDE controllers in OVF; import facility only supports one.
2) I tried to install VirtualBox under 64-bit FreeBSD 9.0-CURRENT #2
[r...@server /usr/ports/emulators/virtualbox-ose]# make
Requires 32-bit libraries installed under /usr/lib32.
Do: cd /usr/src; make build32 install32; ldconfig -v -m -R /usr/lib32
*** Error code 1
Stop in /usr/ports/emulators/virtualbox-ose.
*** Error code 1
Stop in /usr/ports/emulators/virtualbox-ose.
How can I fix that error in FreeBSD?
Peter
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to
freebsd-current-unsubscr...@freebsd.org
I forgot reading sorry for bother...
cd /usr/src; make build32 install32; ldconfig -v -m -R /usr/lib32
Peter
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ZFS v28 is ready for wider testing.
On 09/03/2010 11:50, Peter Molnar, BSD wrote: Requires 32-bit libraries installed under /usr/lib32. Do: cd /usr/src; make build32 install32; ldconfig -v -m -R /usr/lib32 Did you happen to see the above ? -- jhell,v ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ZFS v28 is ready for wider testing.
On Fri, Sep 03, 2010 at 04:50:44PM +0100, Peter Molnar, BSD wrote: Hi, I would like to try ZFS + VirtualBox but I have got problems: 1) Linux 2.6.32-24-generic #42-Ubuntu SMP Fri Aug 20 14:21:58 UTC 2010 x86_64 GNU/Linux I tried import that file in my VirtualBox but I have got error: Failed to import appliance. /home/peter/FreeBSD/zfsv28.ovf Too many IDE controllers in OVF; import facility only supports one. Which VirtualBox version do you use? 3.2.8? Exporting appliances is a bit broken (if you have more than one disk, it will point all disks at the last one from configuration), so I had to edit .ovf file manually to fix this. Maybe I messed something up, but I was able to successfully import it before publishing it. PS. I waited for so long for decent virtualization software for FreeBSD, and I must say VirtualBox is really great, and free, and open-source Are you reading this, VMWare? -- Pawel Jakub Dawidek http://www.wheelsystems.com p...@freebsd.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! pgppp5WIVDzjJ.pgp Description: PGP signature
Re: ZFS v28 is ready for wider testing.
On Fri, Sep 03, 2010 at 07:02:41PM +0200, Pawel Jakub Dawidek wrote: Exporting appliances is a bit broken (if you have more than one disk, it will point all disks at the last one from configuration), so I had to edit .ovf file manually to fix this. Maybe I messed something up, but I was able to successfully import it before publishing it. I tried VirtualBox 3.2.4 on Windows, and was able to import this appliance without any major trouble. The only problem was a complaint about an Inexistent host networking interface, which I solved by going into the network settings and updating Network - Adapter 1. I guess it's just an issue with the way the interface is named on Windows vs. FreeBSD. Thanks for all of the work on this pjd! -Ed ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ZFS v28 is ready for wider testing.
On Thu, Sep 02, 2010 at 01:55:51AM -0700, Rob Farmer wrote:
On Tue, Aug 31, 2010 at 2:59 PM, Pawel Jakub Dawidek p...@freebsd.org wrote:
Ok, now that I know you read everything carefully, here is the patch:
http://people.freebsd.org/~pjd/patches/zfs_20100831.patch.bz2
buildworld on i386 (yes I know ZFS isn't ideal there):
[...]
Yes, I know about this problem, You can use attached patch or wait for
full patch, which I'll be sending later today.
--
Pawel Jakub Dawidek http://www.wheelsystems.com
p...@freebsd.org http://www.FreeBSD.org
FreeBSD committer Am I Evil? Yes, I Am!
--- sys/cddl/compat/opensolaris/sys/atomic.h
+++ sys/cddl/compat/opensolaris/sys/atomic.h
@@ -39,10 +39,9 @@
#ifndef __LP64__
extern void atomic_add_64(volatile uint64_t *target, int64_t delta);
extern void atomic_dec_64(volatile uint64_t *target);
-extern void *atomic_cas_ptr(volatile void *target, void *cmp, void *newval);
#endif
#ifndef __sparc64__
-extern uint64_t atomic_cas_32(volatile uint32_t *target, uint32_t cmp,
+extern uint32_t atomic_cas_32(volatile uint32_t *target, uint32_t cmp,
uint32_t newval);
extern uint64_t atomic_cas_64(volatile uint64_t *target, uint64_t cmp,
uint64_t newval);
@@ -119,21 +118,19 @@
}
#ifndef COMPAT_32BIT
-#if defined(__LP64__)
+#ifdef __LP64__
static __inline void *
atomic_cas_ptr(volatile void *target, void *cmp, void *newval)
{
- return ((void *)atomic_cas_64((volatile uint64_t *)target, (uint64_t)cmp,
- (uint64_t)newval));
+ return ((void *)atomic_cas_64(target, (uint64_t)cmp, (uint64_t)newval));
}
#else
static __inline void *
atomic_cas_ptr(volatile void *target, void *cmp, void *newval)
{
- return ((void *)atomic_cas_32((volatile uint64_t *)target, (uint64_t)cmp,
- (uint64_t)newval));
+ return ((void *)atomic_cas_32(target, (uint32_t)cmp, (uint32_t)newval));
}
#endif
-#endif
+#endif /* !COMPAT_32BIT */
#endif /* !_OPENSOLARIS_SYS_ATOMIC_H_ */
pgppo82knRdQW.pgp
Description: PGP signature
Re: ZFS v28 is ready for wider testing.
On Tue, Aug 31, 2010 at 2:59 PM, Pawel Jakub Dawidek p...@freebsd.org wrote: Ok, now that I know you read everything carefully, here is the patch: http://people.freebsd.org/~pjd/patches/zfs_20100831.patch.bz2 buildworld on i386 (yes I know ZFS isn't ideal there): === cddl/lib/libdtrace (all) cc -O2 -fno-strict-aliasing -pipe -march=prescott -I/usr/obj/usr/src/cddl/lib/libdtrace -I/usr/src/cddl/lib/libdtrace -I/usr/src/cddl/lib/libdtrace/../../../sys/cddl/dev/dtrace/i386 -I/usr/src/cddl/lib/libdtrace/../../../sys/cddl/compat/opensolaris -I/usr/src/cddl/lib/libdtrace/../../../cddl/compat/opensolaris/include -I/usr/src/cddl/lib/libdtrace/../../../cddl/contrib/opensolaris/head -I/usr/src/cddl/lib/libdtrace/../../../cddl/contrib/opensolaris/lib/libctf/common -I/usr/src/cddl/lib/libdtrace/../../../cddl/contrib/opensolaris/lib/libdtrace/common -I/usr/src/cddl/lib/libdtrace/../../../sys/cddl/contrib/opensolaris/uts/common -I/usr/src/cddl/lib/libdtrace/../../../sys/cddl/contrib/opensolaris/uts/intel -DDIS_MEM -DNEED_SOLARIS_BOOLEAN -std=gnu89 -fstack-protector -Wsystem-headers -Werror -Wno-pointer-sign -Wno-unknown-pragmas -c /usr/src/cddl/lib/libdtrace/../../../cddl/contrib/opensolaris/lib/libdtrace/common/dt_aggregate.c In file included from /usr/src/cddl/lib/libdtrace/../../../sys/cddl/compat/opensolaris/sys/bitmap.h:36, from /usr/src/cddl/lib/libdtrace/../../../cddl/contrib/opensolaris/lib/libdtrace/common/dt_impl.h:33, from /usr/src/cddl/lib/libdtrace/../../../cddl/contrib/opensolaris/lib/libdtrace/common/dt_aggregate.c:33: /usr/src/cddl/lib/libdtrace/../../../sys/cddl/compat/opensolaris/sys/atomic.h:132: error: static declaration of 'atomic_cas_ptr' follows non-static declaration /usr/src/cddl/lib/libdtrace/../../../sys/cddl/compat/opensolaris/sys/atomic.h:42: error: previous declaration of 'atomic_cas_ptr' was here cc1: warnings being treated as errors /usr/src/cddl/lib/libdtrace/../../../sys/cddl/compat/opensolaris/sys/atomic.h: In function 'atomic_cas_ptr': /usr/src/cddl/lib/libdtrace/../../../sys/cddl/compat/opensolaris/sys/atomic.h:133: warning: cast from pointer to integer of different size /usr/src/cddl/lib/libdtrace/../../../sys/cddl/compat/opensolaris/sys/atomic.h:134: warning: cast from pointer to integer of different size /usr/src/cddl/lib/libdtrace/../../../sys/cddl/compat/opensolaris/sys/atomic.h:134: warning: passing argument 1 of 'atomic_cas_32' from incompatible pointer type /usr/src/cddl/lib/libdtrace/../../../sys/cddl/compat/opensolaris/sys/atomic.h:134: warning: cast to pointer from integer of different size *** Error code 1 I tried applying the patch to r212087 to rule out recent changes to dtrace, but it made no difference. I used patch -E -p0 patch. -- Rob Farmer ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ZFS v28 is ready for wider testing.
On Tue, Aug 31, 2010 at 11:59:15PM +0200, Pawel Jakub Dawidek wrote:
[...]
Ok, now that I know you read everything carefully, here is the patch:
http://people.freebsd.org/~pjd/patches/zfs_20100831.patch.bz2
Now it is even easier to test new ZFS! :)
Here you can find VirtualBox Appliance (113MB) with
FreeBSD 9-CURRENT and ZFSv28:
http://people.freebsd.org/~pjd/misc/FreeBSD9_ZFSv28_0.1.tgz
Untar it, import it (zfsv28.ovf) to VirtualBox and have fun.
You can log in as root with no password (via virtual console or via SSH).
The system IP address is IP 192.168.56.66/24.
There are 16 ada(4) disks to play with. For example:
zfsv28:root:~# zpool create tank raidz3 ada{0,1,2,3,4,5,6,7} raidz3
ada{8,9,10,11,12,13,14,15}
zfsv28:root:~# zpool status
pool: tank
state: ONLINE
scan: none requested
config:
NAMESTATE READ WRITE CKSUM
tankONLINE 0 0 0
raidz3-0 ONLINE 0 0 0
ada0ONLINE 0 0 0
ada1ONLINE 0 0 0
ada2ONLINE 0 0 0
ada3ONLINE 0 0 0
ada4ONLINE 0 0 0
ada5ONLINE 0 0 0
ada6ONLINE 0 0 0
ada7ONLINE 0 0 0
raidz3-1 ONLINE 0 0 0
ada8ONLINE 0 0 0
ada9ONLINE 0 0 0
ada10 ONLINE 0 0 0
ada11 ONLINE 0 0 0
ada12 ONLINE 0 0 0
ada13 ONLINE 0 0 0
ada14 ONLINE 0 0 0
ada15 ONLINE 0 0 0
errors: No known data errors
--
Pawel Jakub Dawidek http://www.wheelsystems.com
p...@freebsd.org http://www.FreeBSD.org
FreeBSD committer Am I Evil? Yes, I Am!
pgp3nDIzwUUuC.pgp
Description: PGP signature
Re: ZFS v28 is ready for wider testing.
Pawel Jakub Dawidek p...@freebsd.org writes: I'd like to give you ZFS v28 for testing. If you are neither brave nor mad, you can stop here. [...] So test whatever you can and report back. Look for regressions, strange behaviour, missing features, deadlocks, livelocks, preformance degradation, etc. [...] The boot code is not updated at all, so booting off of ZFS doesn't currently work. This only apply when one's upgrading the pool's metadata. Besides, I think bootcode doesn't support gzip-compressed pools, too. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ZFS v28 is ready for wider testing.
On Tuesday 31 August 2010 16:59:15 Pawel Jakub Dawidek wrote: Hello. I'd like to give you ZFS v28 for testing. If you are neither brave nor mad, you can stop here. The patchset is very experimental. It can eat your cookie and hurt your teddy bear, so be warned. Don't try it for anything except testing. This patchset is also a message we, as the FreeBSD project, would like to send to our users: Eventhough OpenSolaris is dead, the ZFS file system is going to stay in FreeBSD. At this point we have quite a few developers involved in ZFS on FreeBSD as well as serveral companies. We are also looking forward to work with IllumOS. So, what this new ZFS brings? - Data deduplication. Read more here: http://blogs.sun.com/bonwick/entry/zfs_dedup - Triple parity RAIDZ (RAIDZ3). Read more here: http://dtrace.org/blogs/ahl/2009/07/21/triple-parity-raid-z/ - zfs diff. Read more here: http://arc.opensolaris.org/caselog/PSARC/2010/105/20100328_tim.haley - zpool split. Read more here: http://arc.opensolaris.org/caselog/PSARC/2009/511/20090924_mark.musante - Snapshot holds. Read more here: http://arc.opensolaris.org/caselog/PSARC/2009/297/20090511_chris.kirby - zpool import -F. Allows to rewind corrupted pool to earlier transaction group. - Possibility to import pool in read-only mode. And much, much more, including plenty of preformance improvements and bug fixes. So test whatever you can and report back. Look for regressions, strange behaviour, missing features, deadlocks, livelocks, preformance degradation, etc. The boot code is not updated at all, so booting off of ZFS doesn't currently work. The patch is against today's FreeBSD HEAD. The patch enables (in sys/modules/zfs/Makefile) ZFS internal debugging, please don't turn it off. Also, compile your kernel with the following options: options KDB options DDB options INVARIANTS options INVARIANT_SUPPORT options WITNESS options WITNESS_SKIPSPIN options DEBUG_LOCKS options DEBUG_VFS_LOCKS Ignore all the LOR (Lock Order Reversal) reports from WITNESS. There will be plenty of those, and you'll desperately want to report them, but please don't. The best way to report a problem is to answer to this e-mail with as short as possible procedure of how to reproduce it and debugging info. I'd prefer textdump if possible. Below you can find quick procedure how to setup textdumps: Choose spare/swap disk/partition in your system, let's say it is /dev/ad0s1b. Add the following line to /etc/fstab: /dev/ad0s1b noneswapsw 0 0 Add the following line to /etc/rc.conf: ddb_enable=YES Run the following commands: # /etc/rc.d/swap1 start # /etc/rc.d/dumpon start # /etc/rc.d/ddb start This will setup swap, mark it as dump device and setup some DDB scripts. Or you can just reboot. Now when your system panic or deadlock, enter DDB and call the following command: ddb run kdb.enter.panic It will execute all the commands I need, dump them in text format to your swap device and reboot machine. After the reboot, you should find textdump.tar.0 file in /var/crash/ directory. This is the debug info I need. End of textdumps procedure. Ok, now that I know you read everything carefully, here is the patch: http://people.freebsd.org/~pjd/patches/zfs_20100831.patch.bz2 Good luck! : I get the following error from make buildworld after applying the patch. I checked twice to make sure the patch applied cleanly, which it did. cc -O2 -pipe - I/usr/src/cddl/usr.bin/ctfconvert/../../../sys/cddl/compat/opensolaris - I/usr/src/cddl/usr.bin/ctfconvert/../../../cddl/compat/opensolaris/include - I/usr/src/cddl/usr.bin/ctfconvert/../../../cddl/contrib/opensolaris - I/usr/src/cddl/usr.bin/ctfconvert/../../../sys/cddl/contrib/opensolaris - I/usr/src/cddl/usr.bin/ctfconvert/../../../cddl/contrib/opensolaris/head - I/usr/src/cddl/usr.bin/ctfconvert/../../../cddl/contrib/opensolaris/tools/ctf/common - I/usr/src/cddl/usr.bin/ctfconvert/../../../cddl/contrib/opensolaris/tools/ctf/cvt - I/usr/src/cddl/usr.bin/ctfconvert/../../../sys/cddl/contrib/opensolaris/uts/common -DNEED_SOLARIS_BOOLEAN -g -std=gnu89 -Wno-unknown-pragmas - I/usr/obj/usr/src/tmp/legacy/usr/include -static - L/usr/obj/usr/src/tmp/legacy/usr/lib -o ctfconvert alist.o ctf.o ctfconvert.o dwarf.o fixup_tdescs.o hash.o iidesc.o input.o list.o memory.o merge.o output.o st_parse.o stabs.o stack.o strtab.o symbol.o tdata.o traverse.o util.o -lctf -ldwarf -lelf -lz -lpthread -legacy strtab.o(.text+0x109): In function `strtab_print':
Re: ZFS v28 is ready for wider testing.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 08/31/2010 17:59, Pawel Jakub Dawidek wrote: Hello. I'd like to give you ZFS v28 for testing. If you are neither brave nor mad, you can stop here. The patchset is very experimental. It can eat your cookie and hurt your teddy bear, so be warned. Don't try it for anything except testing. This patchset is also a message we, as the FreeBSD project, would like to send to our users: Eventhough OpenSolaris is dead, the ZFS file system is going to stay in FreeBSD. At this point we have quite a few developers involved in ZFS on FreeBSD as well as serveral companies. We are also looking forward to work with IllumOS. So, what this new ZFS brings? - Data deduplication. Read more here: http://blogs.sun.com/bonwick/entry/zfs_dedup - Triple parity RAIDZ (RAIDZ3). Read more here: http://dtrace.org/blogs/ahl/2009/07/21/triple-parity-raid-z/ - zfs diff. Read more here: http://arc.opensolaris.org/caselog/PSARC/2010/105/20100328_tim.haley - zpool split. Read more here: http://arc.opensolaris.org/caselog/PSARC/2009/511/20090924_mark.musante - Snapshot holds. Read more here: http://arc.opensolaris.org/caselog/PSARC/2009/297/20090511_chris.kirby - zpool import -F. Allows to rewind corrupted pool to earlier transaction group. - Possibility to import pool in read-only mode. And much, much more, including plenty of preformance improvements and bug fixes. So test whatever you can and report back. Look for regressions, strange behaviour, missing features, deadlocks, livelocks, preformance degradation, etc. The boot code is not updated at all, so booting off of ZFS doesn't currently work. The patch is against today's FreeBSD HEAD. The patch enables (in sys/modules/zfs/Makefile) ZFS internal debugging, please don't turn it off. Also, compile your kernel with the following options: options KDB options DDB options INVARIANTS options INVARIANT_SUPPORT options WITNESS options WITNESS_SKIPSPIN options DEBUG_LOCKS options DEBUG_VFS_LOCKS Ignore all the LOR (Lock Order Reversal) reports from WITNESS. There will be plenty of those, and you'll desperately want to report them, but please don't. The best way to report a problem is to answer to this e-mail with as short as possible procedure of how to reproduce it and debugging info. I'd prefer textdump if possible. Below you can find quick procedure how to setup textdumps: Choose spare/swap disk/partition in your system, let's say it is /dev/ad0s1b. Add the following line to /etc/fstab: /dev/ad0s1b noneswapsw 0 0 Add the following line to /etc/rc.conf: ddb_enable=YES Run the following commands: # /etc/rc.d/swap1 start # /etc/rc.d/dumpon start # /etc/rc.d/ddb start This will setup swap, mark it as dump device and setup some DDB scripts. Or you can just reboot. Now when your system panic or deadlock, enter DDB and call the following command: ddb run kdb.enter.panic It will execute all the commands I need, dump them in text format to your swap device and reboot machine. After the reboot, you should find textdump.tar.0 file in /var/crash/ directory. This is the debug info I need. End of textdumps procedure. Ok, now that I know you read everything carefully, here is the patch: http://people.freebsd.org/~pjd/patches/zfs_20100831.patch.bz2 Good luck! : 293 files changed, 54587 insertions(+), 19525 deletions(-) Yikes! I certainly commend you for this work. As for how to explain it I do not think the words exist in the English dictionary. Though it is unlikely that I will be attempting to use this ATM I logged some things for giggles. http://bit.ly/d20tML At that URL you will find a patch.log reject-files.log and a directory 'reject-files' with non-other than the reject files from the patch tar bzip2'd for convenience. Just for being curious found out that only 14 of the 293 files that were changed had rejects against a stable/8 that was patched to ZFSv15 + metaslab_v2 + abe_stat_rrwlock. My Hats off to the developers and everyone involved with keeping this all together, it says A LOT!. This is impressive. Not to mention this easily read and understandable email to top it off. Regards! - -- Again here is the link: http://bit.ly/d20tML jhell,v -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.16 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJMfrfqAAoJEJBXh4mJ2FR+gscH/3tXKOTa2/eVt5Ev9ovpEbS3 n3EiMe6b8G8jxWaynoccNFWi6IywTzDhuKQxM/o4I1RnUJe50fSF00IQqwVo3QDm rcju0RKFw6jFgLar+1qq2prssAWQZ4DLC9VQY5CxZ/NY6MgEoWWqaV91RkOqLu5a
Re: ZFS v28 is ready for wider testing.
On Tue, Aug 31, 2010 at 11:59:15PM +0200, Pawel Jakub Dawidek wrote: Ok, now that I know you read everything carefully, here is the patch: http://people.freebsd.org/~pjd/patches/zfs_20100831.patch.bz2 Important note. Please patch with the following command: # patch -E -p0 zfs_20100831.patch If you don't use -E option, patch(1) won't remove empty files and you won't be able to compile it. -- Pawel Jakub Dawidek http://www.wheelsystems.com p...@freebsd.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! pgplMh4YH3ZOH.pgp Description: PGP signature
Re: ZFS v28 is ready for wider testing.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 2010/09/01 07:28, Josh Paetzel wrote: On Tuesday 31 August 2010 16:59:15 Pawel Jakub Dawidek wrote: Hello. I'd like to give you ZFS v28 for testing. If you are neither brave nor mad, you can stop here. The patchset is very experimental. It can eat your cookie and hurt your teddy bear, so be warned. Don't try it for anything except testing. This patchset is also a message we, as the FreeBSD project, would like to send to our users: Eventhough OpenSolaris is dead, the ZFS file system is going to stay in FreeBSD. At this point we have quite a few developers involved in ZFS on FreeBSD as well as serveral companies. We are also looking forward to work with IllumOS. So, what this new ZFS brings? - Data deduplication. Read more here: http://blogs.sun.com/bonwick/entry/zfs_dedup - Triple parity RAIDZ (RAIDZ3). Read more here: http://dtrace.org/blogs/ahl/2009/07/21/triple-parity-raid-z/ - zfs diff. Read more here: http://arc.opensolaris.org/caselog/PSARC/2010/105/20100328_tim.haley - zpool split. Read more here: http://arc.opensolaris.org/caselog/PSARC/2009/511/20090924_mark.musante - Snapshot holds. Read more here: http://arc.opensolaris.org/caselog/PSARC/2009/297/20090511_chris.kirby - zpool import -F. Allows to rewind corrupted pool to earlier transaction group. - Possibility to import pool in read-only mode. And much, much more, including plenty of preformance improvements and bug fixes. So test whatever you can and report back. Look for regressions, strange behaviour, missing features, deadlocks, livelocks, preformance degradation, etc. The boot code is not updated at all, so booting off of ZFS doesn't currently work. The patch is against today's FreeBSD HEAD. The patch enables (in sys/modules/zfs/Makefile) ZFS internal debugging, please don't turn it off. Also, compile your kernel with the following options: options KDB options DDB options INVARIANTS options INVARIANT_SUPPORT options WITNESS options WITNESS_SKIPSPIN options DEBUG_LOCKS options DEBUG_VFS_LOCKS Ignore all the LOR (Lock Order Reversal) reports from WITNESS. There will be plenty of those, and you'll desperately want to report them, but please don't. The best way to report a problem is to answer to this e-mail with as short as possible procedure of how to reproduce it and debugging info. I'd prefer textdump if possible. Below you can find quick procedure how to setup textdumps: Choose spare/swap disk/partition in your system, let's say it is /dev/ad0s1b. Add the following line to /etc/fstab: /dev/ad0s1b noneswapsw 0 0 Add the following line to /etc/rc.conf: ddb_enable=YES Run the following commands: # /etc/rc.d/swap1 start # /etc/rc.d/dumpon start # /etc/rc.d/ddb start This will setup swap, mark it as dump device and setup some DDB scripts. Or you can just reboot. Now when your system panic or deadlock, enter DDB and call the following command: ddb run kdb.enter.panic It will execute all the commands I need, dump them in text format to your swap device and reboot machine. After the reboot, you should find textdump.tar.0 file in /var/crash/ directory. This is the debug info I need. End of textdumps procedure. Ok, now that I know you read everything carefully, here is the patch: http://people.freebsd.org/~pjd/patches/zfs_20100831.patch.bz2 Good luck! : I get the following error from make buildworld after applying the patch. I checked twice to make sure the patch applied cleanly, which it did. cc -O2 -pipe - I/usr/src/cddl/usr.bin/ctfconvert/../../../sys/cddl/compat/opensolaris - I/usr/src/cddl/usr.bin/ctfconvert/../../../cddl/compat/opensolaris/include - I/usr/src/cddl/usr.bin/ctfconvert/../../../cddl/contrib/opensolaris - I/usr/src/cddl/usr.bin/ctfconvert/../../../sys/cddl/contrib/opensolaris - I/usr/src/cddl/usr.bin/ctfconvert/../../../cddl/contrib/opensolaris/head - I/usr/src/cddl/usr.bin/ctfconvert/../../../cddl/contrib/opensolaris/tools/ctf/common - I/usr/src/cddl/usr.bin/ctfconvert/../../../cddl/contrib/opensolaris/tools/ctf/cvt - I/usr/src/cddl/usr.bin/ctfconvert/../../../sys/cddl/contrib/opensolaris/uts/common -DNEED_SOLARIS_BOOLEAN -g -std=gnu89 -Wno-unknown-pragmas - I/usr/obj/usr/src/tmp/legacy/usr/include -static - L/usr/obj/usr/src/tmp/legacy/usr/lib -o ctfconvert alist.o ctf.o ctfconvert.o dwarf.o fixup_tdescs.o hash.o iidesc.o input.o list.o memory.o merge.o output.o st_parse.o stabs.o stack.o strtab.o symbol.o tdata.o traverse.o util.o -lctf -ldwarf -lelf -lz -lpthread -legacy strtab.o(.text+0x109): In function
Re: ZFS v28 is ready for wider testing.
On 09/01/2010 10:28, Josh Paetzel wrote: On Tuesday 31 August 2010 16:59:15 Pawel Jakub Dawidek wrote: Hello. I'd like to give you ZFS v28 for testing. If you are neither brave nor mad, you can stop here. The patchset is very experimental. It can eat your cookie and hurt your teddy bear, so be warned. Don't try it for anything except testing. This patchset is also a message we, as the FreeBSD project, would like to send to our users: Eventhough OpenSolaris is dead, the ZFS file system is going to stay in FreeBSD. At this point we have quite a few developers involved in ZFS on FreeBSD as well as serveral companies. We are also looking forward to work with IllumOS. So, what this new ZFS brings? - Data deduplication. Read more here: http://blogs.sun.com/bonwick/entry/zfs_dedup - Triple parity RAIDZ (RAIDZ3). Read more here: http://dtrace.org/blogs/ahl/2009/07/21/triple-parity-raid-z/ - zfs diff. Read more here: http://arc.opensolaris.org/caselog/PSARC/2010/105/20100328_tim.haley - zpool split. Read more here: http://arc.opensolaris.org/caselog/PSARC/2009/511/20090924_mark.musante - Snapshot holds. Read more here: http://arc.opensolaris.org/caselog/PSARC/2009/297/20090511_chris.kirby - zpool import -F. Allows to rewind corrupted pool to earlier transaction group. - Possibility to import pool in read-only mode. And much, much more, including plenty of preformance improvements and bug fixes. So test whatever you can and report back. Look for regressions, strange behaviour, missing features, deadlocks, livelocks, preformance degradation, etc. The boot code is not updated at all, so booting off of ZFS doesn't currently work. The patch is against today's FreeBSD HEAD. The patch enables (in sys/modules/zfs/Makefile) ZFS internal debugging, please don't turn it off. Also, compile your kernel with the following options: options KDB options DDB options INVARIANTS options INVARIANT_SUPPORT options WITNESS options WITNESS_SKIPSPIN options DEBUG_LOCKS options DEBUG_VFS_LOCKS Ignore all the LOR (Lock Order Reversal) reports from WITNESS. There will be plenty of those, and you'll desperately want to report them, but please don't. The best way to report a problem is to answer to this e-mail with as short as possible procedure of how to reproduce it and debugging info. I'd prefer textdump if possible. Below you can find quick procedure how to setup textdumps: Choose spare/swap disk/partition in your system, let's say it is /dev/ad0s1b. Add the following line to /etc/fstab: /dev/ad0s1b noneswapsw 0 0 Add the following line to /etc/rc.conf: ddb_enable=YES Run the following commands: # /etc/rc.d/swap1 start # /etc/rc.d/dumpon start # /etc/rc.d/ddb start This will setup swap, mark it as dump device and setup some DDB scripts. Or you can just reboot. Now when your system panic or deadlock, enter DDB and call the following command: ddb run kdb.enter.panic It will execute all the commands I need, dump them in text format to your swap device and reboot machine. After the reboot, you should find textdump.tar.0 file in /var/crash/ directory. This is the debug info I need. End of textdumps procedure. Ok, now that I know you read everything carefully, here is the patch: http://people.freebsd.org/~pjd/patches/zfs_20100831.patch.bz2 Good luck! : I get the following error from make buildworld after applying the patch. I checked twice to make sure the patch applied cleanly, which it did. cc -O2 -pipe - I/usr/src/cddl/usr.bin/ctfconvert/../../../sys/cddl/compat/opensolaris - I/usr/src/cddl/usr.bin/ctfconvert/../../../cddl/compat/opensolaris/include - I/usr/src/cddl/usr.bin/ctfconvert/../../../cddl/contrib/opensolaris - I/usr/src/cddl/usr.bin/ctfconvert/../../../sys/cddl/contrib/opensolaris - I/usr/src/cddl/usr.bin/ctfconvert/../../../cddl/contrib/opensolaris/head - I/usr/src/cddl/usr.bin/ctfconvert/../../../cddl/contrib/opensolaris/tools/ctf/common - I/usr/src/cddl/usr.bin/ctfconvert/../../../cddl/contrib/opensolaris/tools/ctf/cvt - I/usr/src/cddl/usr.bin/ctfconvert/../../../sys/cddl/contrib/opensolaris/uts/common -DNEED_SOLARIS_BOOLEAN -g -std=gnu89 -Wno-unknown-pragmas - I/usr/obj/usr/src/tmp/legacy/usr/include -static - L/usr/obj/usr/src/tmp/legacy/usr/lib -o ctfconvert alist.o ctf.o ctfconvert.o dwarf.o fixup_tdescs.o hash.o iidesc.o input.o list.o memory.o merge.o output.o st_parse.o stabs.o stack.o strtab.o symbol.o tdata.o traverse.o util.o -lctf -ldwarf -lelf -lz -lpthread -legacy strtab.o(.text+0x109): In function `strtab_print':
Re: ZFS v28 is ready for wider testing.
On Tue, Aug 31, 2010 at 2:59 PM, Pawel Jakub Dawidek p...@freebsd.org wrote: Hello. I'd like to give you ZFS v28 for testing. If you are neither brave nor mad, you can stop here. Woohoo! Thanks for all your hard work on this! Matt ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ZFS v28 is ready for wider testing.
This is awesome. Thank you! -J On Tue, Aug 31, 2010 at 3:59 PM, Pawel Jakub Dawidek p...@freebsd.org wrote: Hello. I'd like to give you ZFS v28 for testing. If you are neither brave nor mad, you can stop here. The patchset is very experimental. It can eat your cookie and hurt your teddy bear, so be warned. Don't try it for anything except testing. This patchset is also a message we, as the FreeBSD project, would like to send to our users: Eventhough OpenSolaris is dead, the ZFS file system is going to stay in FreeBSD. At this point we have quite a few developers involved in ZFS on FreeBSD as well as serveral companies. We are also looking forward to work with IllumOS. So, what this new ZFS brings? - Data deduplication. Read more here: http://blogs.sun.com/bonwick/entry/zfs_dedup - Triple parity RAIDZ (RAIDZ3). Read more here: http://dtrace.org/blogs/ahl/2009/07/21/triple-parity-raid-z/ - zfs diff. Read more here: http://arc.opensolaris.org/caselog/PSARC/2010/105/20100328_tim.haley - zpool split. Read more here: http://arc.opensolaris.org/caselog/PSARC/2009/511/20090924_mark.musante - Snapshot holds. Read more here: http://arc.opensolaris.org/caselog/PSARC/2009/297/20090511_chris.kirby - zpool import -F. Allows to rewind corrupted pool to earlier transaction group. - Possibility to import pool in read-only mode. And much, much more, including plenty of preformance improvements and bug fixes. So test whatever you can and report back. Look for regressions, strange behaviour, missing features, deadlocks, livelocks, preformance degradation, etc. The boot code is not updated at all, so booting off of ZFS doesn't currently work. The patch is against today's FreeBSD HEAD. The patch enables (in sys/modules/zfs/Makefile) ZFS internal debugging, please don't turn it off. Also, compile your kernel with the following options: options KDB options DDB options INVARIANTS options INVARIANT_SUPPORT options WITNESS options WITNESS_SKIPSPIN options DEBUG_LOCKS options DEBUG_VFS_LOCKS Ignore all the LOR (Lock Order Reversal) reports from WITNESS. There will be plenty of those, and you'll desperately want to report them, but please don't. The best way to report a problem is to answer to this e-mail with as short as possible procedure of how to reproduce it and debugging info. I'd prefer textdump if possible. Below you can find quick procedure how to setup textdumps: Choose spare/swap disk/partition in your system, let's say it is /dev/ad0s1b. Add the following line to /etc/fstab: /dev/ad0s1b none swap sw 0 0 Add the following line to /etc/rc.conf: ddb_enable=YES Run the following commands: # /etc/rc.d/swap1 start # /etc/rc.d/dumpon start # /etc/rc.d/ddb start This will setup swap, mark it as dump device and setup some DDB scripts. Or you can just reboot. Now when your system panic or deadlock, enter DDB and call the following command: ddb run kdb.enter.panic It will execute all the commands I need, dump them in text format to your swap device and reboot machine. After the reboot, you should find textdump.tar.0 file in /var/crash/ directory. This is the debug info I need. End of textdumps procedure. Ok, now that I know you read everything carefully, here is the patch: http://people.freebsd.org/~pjd/patches/zfs_20100831.patch.bz2 Good luck! : -- Pawel Jakub Dawidek http://www.wheelsystems.com p...@freebsd.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ZFS v28 is ready for wider testing.
Pawel, Pawel Jakub Dawidek wrote: I'd like to give you ZFS v28 for testing. If you are neither brave nor mad, you can stop here. The patchset is very experimental. It can eat your cookie and hurt your teddy bear, so be warned. Don't try it for anything except testing. Thank you very much - now that there are a couple of major steps feature-wise we're going to give the experimental version a try. This patchset is also a message we, as the FreeBSD project, would like to send to our users: Eventhough OpenSolaris is dead, the ZFS file system is going to stay in FreeBSD. At this point we have quite a few developers involved in ZFS on FreeBSD as well as serveral companies. We are also looking forward to work with IllumOS. Fine. FYI: http://www.h-online.com/open/news/item/ZFS-as-a-Linux-kernel-module-1069056.html Too bad FreeBSD still lacks Infiniband support. Currently we use ZFS on FreeBSD and Infiniband on Linux. If Linux supports both, we will (be forced to) switch. Cheers, vt -- Volker T. Mueller Continum AG Bismarckallee 7d 79098 Freiburg i. Br. Tel. +49 761 21711171 Fax. +49 761 21711198 http://www.continum.net Sitz der Gesellschaft: Freiburg im Breisgau Registergericht: Amtsgericht Freiburg, HRB 6866 Vorstand: Rolf Mathis, Volker T. Mueller Vorsitzender d. Aufsichtsrats: Prof. Dr. Karl-F. Fischbach ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ZFS v28 is ready for wider testing.
Infiniband is currently being worked on, sponsored by Panasas, Isilon and someone else. It's coming along pretty well. http://www.h-online.com/open/news/item/ZFS-as-a-Linux-kernel-module-1069056.html Too bad FreeBSD still lacks Infiniband support. Currently we use ZFS on FreeBSD and Infiniband on Linux. If Linux supports both, we will (be forced to) switch. Cheers, vt ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ZFS v28 is ready for wider testing.
That's cool. Thank you for your work on it. best regards, hanzhu On Wed, Sep 1, 2010 at 5:59 AM, Pawel Jakub Dawidek p...@freebsd.org wrote: Hello. I'd like to give you ZFS v28 for testing. If you are neither brave nor mad, you can stop here. The patchset is very experimental. It can eat your cookie and hurt your teddy bear, so be warned. Don't try it for anything except testing. This patchset is also a message we, as the FreeBSD project, would like to send to our users: Eventhough OpenSolaris is dead, the ZFS file system is going to stay in FreeBSD. At this point we have quite a few developers involved in ZFS on FreeBSD as well as serveral companies. We are also looking forward to work with IllumOS. So, what this new ZFS brings? - Data deduplication. Read more here: http://blogs.sun.com/bonwick/entry/zfs_dedup - Triple parity RAIDZ (RAIDZ3). Read more here: http://dtrace.org/blogs/ahl/2009/07/21/triple-parity-raid-z/ - zfs diff. Read more here: http://arc.opensolaris.org/caselog/PSARC/2010/105/20100328_tim.haley - zpool split. Read more here: http://arc.opensolaris.org/caselog/PSARC/2009/511/20090924_mark.musante - Snapshot holds. Read more here: http://arc.opensolaris.org/caselog/PSARC/2009/297/20090511_chris.kirby - zpool import -F. Allows to rewind corrupted pool to earlier transaction group. - Possibility to import pool in read-only mode. And much, much more, including plenty of preformance improvements and bug fixes. So test whatever you can and report back. Look for regressions, strange behaviour, missing features, deadlocks, livelocks, preformance degradation, etc. The boot code is not updated at all, so booting off of ZFS doesn't currently work. The patch is against today's FreeBSD HEAD. The patch enables (in sys/modules/zfs/Makefile) ZFS internal debugging, please don't turn it off. Also, compile your kernel with the following options: options KDB options DDB options INVARIANTS options INVARIANT_SUPPORT options WITNESS options WITNESS_SKIPSPIN options DEBUG_LOCKS options DEBUG_VFS_LOCKS Ignore all the LOR (Lock Order Reversal) reports from WITNESS. There will be plenty of those, and you'll desperately want to report them, but please don't. The best way to report a problem is to answer to this e-mail with as short as possible procedure of how to reproduce it and debugging info. I'd prefer textdump if possible. Below you can find quick procedure how to setup textdumps: Choose spare/swap disk/partition in your system, let's say it is /dev/ad0s1b. Add the following line to /etc/fstab: /dev/ad0s1b noneswapsw 0 0 Add the following line to /etc/rc.conf: ddb_enable=YES Run the following commands: # /etc/rc.d/swap1 start # /etc/rc.d/dumpon start # /etc/rc.d/ddb start This will setup swap, mark it as dump device and setup some DDB scripts. Or you can just reboot. Now when your system panic or deadlock, enter DDB and call the following command: ddb run kdb.enter.panic It will execute all the commands I need, dump them in text format to your swap device and reboot machine. After the reboot, you should find textdump.tar.0 file in /var/crash/ directory. This is the debug info I need. End of textdumps procedure. Ok, now that I know you read everything carefully, here is the patch: http://people.freebsd.org/~pjd/patches/zfs_20100831.patch.bz2http://people.freebsd.org/%7Epjd/patches/zfs_20100831.patch.bz2 Good luck! : -- Pawel Jakub Dawidek http://www.wheelsystems.com p...@freebsd.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ZFS v28 is ready for wider testing.
Cool, but i may try this on a VM and maybe try this on a expermential production system after I test it on VM since a real system may help the progress of the new ZFS sinc On Tue, Aug 31, 2010 at 8:09 PM, Zhu Han schumi@gmail.com wrote: That's cool. Thank you for your work on it. best regards, hanzhu On Wed, Sep 1, 2010 at 5:59 AM, Pawel Jakub Dawidek p...@freebsd.org wrote: Hello. I'd like to give you ZFS v28 for testing. If you are neither brave nor mad, you can stop here. The patchset is very experimental. It can eat your cookie and hurt your teddy bear, so be warned. Don't try it for anything except testing. This patchset is also a message we, as the FreeBSD project, would like to send to our users: Eventhough OpenSolaris is dead, the ZFS file system is going to stay in FreeBSD. At this point we have quite a few developers involved in ZFS on FreeBSD as well as serveral companies. We are also looking forward to work with IllumOS. So, what this new ZFS brings? - Data deduplication. Read more here: http://blogs.sun.com/bonwick/entry/zfs_dedup - Triple parity RAIDZ (RAIDZ3). Read more here: http://dtrace.org/blogs/ahl/2009/07/21/triple-parity-raid-z/ - zfs diff. Read more here: http://arc.opensolaris.org/caselog/PSARC/2010/105/20100328_tim.haley - zpool split. Read more here: http://arc.opensolaris.org/caselog/PSARC/2009/511/20090924_mark.musante - Snapshot holds. Read more here: http://arc.opensolaris.org/caselog/PSARC/2009/297/20090511_chris.kirby - zpool import -F. Allows to rewind corrupted pool to earlier transaction group. - Possibility to import pool in read-only mode. And much, much more, including plenty of preformance improvements and bug fixes. So test whatever you can and report back. Look for regressions, strange behaviour, missing features, deadlocks, livelocks, preformance degradation, etc. The boot code is not updated at all, so booting off of ZFS doesn't currently work. The patch is against today's FreeBSD HEAD. The patch enables (in sys/modules/zfs/Makefile) ZFS internal debugging, please don't turn it off. Also, compile your kernel with the following options: options KDB options DDB options INVARIANTS options INVARIANT_SUPPORT options WITNESS options WITNESS_SKIPSPIN options DEBUG_LOCKS options DEBUG_VFS_LOCKS Ignore all the LOR (Lock Order Reversal) reports from WITNESS. There will be plenty of those, and you'll desperately want to report them, but please don't. The best way to report a problem is to answer to this e-mail with as short as possible procedure of how to reproduce it and debugging info. I'd prefer textdump if possible. Below you can find quick procedure how to setup textdumps: Choose spare/swap disk/partition in your system, let's say it is /dev/ad0s1b. Add the following line to /etc/fstab: /dev/ad0s1b none swap sw 0 0 Add the following line to /etc/rc.conf: ddb_enable=YES Run the following commands: # /etc/rc.d/swap1 start # /etc/rc.d/dumpon start # /etc/rc.d/ddb start This will setup swap, mark it as dump device and setup some DDB scripts. Or you can just reboot. Now when your system panic or deadlock, enter DDB and call the following command: ddb run kdb.enter.panic It will execute all the commands I need, dump them in text format to your swap device and reboot machine. After the reboot, you should find textdump.tar.0 file in /var/crash/ directory. This is the debug info I need. End of textdumps procedure. Ok, now that I know you read everything carefully, here is the patch: http://people.freebsd.org/~pjd/patches/zfs_20100831.patch.bz2http://people.freebsd.org/%7Epjd/patches/zfs_20100831.patch.bz2 Good luck! : -- Pawel Jakub Dawidek http://www.wheelsystems.com p...@freebsd.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
