similar to: flag day: ZFS on-disk format change

Author: ahrens Repository: /hg/zfs-crypto/gate Revision: 0fdac67554fe0f4938120fb4f0cb35cbbcd38c0b Log message: 6389368 fat zap should use 16k blocks (with backwards compatability) Files: update: usr/src/uts/common/fs/zfs/dbuf.c update: usr/src/uts/common/fs/zfs/dmu_tx.c update: usr/src/uts/common/fs/zfs/dnode.c update: usr/src/uts/common/fs/zfs/sys/zap_impl.h update:

Dear helpers, I have strange results with levelplot: The following lines of code produce a figure with a strange gray horizontal line. Changing n to 9 the line vanishes almost - it stays in the colorbar. Any ideas? The pixel geometry of the lower half of the figure is wrong? ############################## n<-8 xyz<-expand.grid(x=seq(1,n),y=seq(1,n)) z<-matrix(0,n,n)

The time has come to review the current Contributor and Core contributor grants for ZFS. Since all of the ZFS core contributors grants are set to expire on 02-24-2009 we need to renew the members that are still contributing at core contributor levels. We should also add some new members to both Contributor and Core contributor levels. First the current list of Core contributors: Bill

Dear r-helpers, we have installation problems: Successful installation of R-0.63 base package on Solaris 2.5.1 with the SunSoft compilers f77, c version 4.2. We habe problems with the installation of further packages e.g. integrate from CRAN. R code works but the shared objects built from fortran code do not find the appropriate libs with functions like __pow_ii or __epx at runtime. We tried

Hi, working with R, version 0.63.0, I was successful to dyn.load fortran90 subroutines on a Solaris 2.6, as long as they are more or less in conformity with f77. It was not possible to work with statements like REAL,DIMENSION(:) :: d or x=SUM(y). REAL,DIMENSION(1:10) :: d is possible. We compiled R with f77. Is it possible with real f90 routines or is is in any conflict with the shared

Hello zfs-discuss, Is someone actually working on it? Or any other algorithms? Any dates? -- Best regards, Robert mailto:rmilkowski at task.gda.pl http://milek.blogspot.com

I have been playing around with osol-nv-b114 version, and the ZFS user and group quotas. First of all, it is fantastic. Thank you all! (Sun, Ahrens and anyone else involved). I''m currently copying over one of the smaller user areas, and setting up their quotas, so I have yet to start large scale testing. But the initial work is very promising. (Just 90G data, 341694 accounts) Using

In my testing, I''ve found the following error: zpool status -v pool: local 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: none requested

I started three new threads recently, "Feature proposal: differential pools" "Feature proposal: trashcan via auto-snapshot with every txg commit" "Flushing synchronous writes to mirrors" Matthew Ahrens and Henk Langeveld both replied to my first thread by sending their messages to both me and to zfs-discuss at opensolaris.org, and Matt did likewise for my second

Dear helpers, thanks. Installation of R and packages (like integrate) successful done. The LD_LIBRARY_PATH wasn't set in the correct order: system libs ahead of the compiler lib. Cross checks provided by Brian Ripley, Oxford, helped a lot. Yours Bodo gordon.harrington at uni.edu wrote: > Without tracing the loader system calls and knowing where the functions are > located I can

> Bug ID: 6398177 > Synopsis: zfs: poor nightly build performance in 32-bit mode (high disk activity) Part of the problem appear to be these kmem_caches: # mdb -k ... > ::kmastat cache buf buf buf memory alloc alloc name size in use total in use succeed fail ------------------------- ------ ------ ------ ---------

I''m playing around with snv_128 on one of my systems, and trying to see what kinda of benefits enabling dedup will give me. The standard practice for reprocessing data that''s already stored to add compression and now dedup seems to be a send / receive pipe similar to: zfs send -R <old fs>@snap | zfs recv -d <new fs> However, according to the man page,

> Matthew Ahrens wrote: > > Ross Newell wrote: > >> What are this issues preventing the root directory being stored on > >> raidz? > >> I''m talking specifically about root, and not boot which I can see > >> would be > >> difficult. > >> > >> Would it be something an amateur programmer could address in a > >>

Hi, I recently took a closer look at the implementations of sampling algorithms for all basic distributions in R. Two seemed inefficient (slow) to me: 1) rgeom() 2) rexp() Obviously, Geo(p) and Exp(lambda) have very simple stochastic representations (floor(Y) for Y ~ Exp(-log(1-p)) and (-log U)/lambda for U ~ U[0,1]). I thought I could easily beat the (more complicated) algorithms that R uses for

I contacted the author of ''lsof'' regarding the missing ZFS support. The command works but fails to display any files that are opened by the process in a ZFS filesystem. He indicates that the required ZFS kernel structure definitions (header files) are not shipped with the OS. He further indicated that he rummaged through the OpenSolaris source tree and the files doesn''t

Hi Some developers here said a long time ago that someone should show the code for LZO compression support for ZFS before talking about the next step. I made that code with a friend and we also made a little benchmark to give a first impression: http://denisy.dyndns.org/lzo_vs_lzjb/ I hope we made no technical error, but if you find something not accurate, we will correct it. Denis -- This

Hi matt, I have some problems about understanding zfs COW implemention. Suppose b and c are both children dir of a, if c changes, there will be new versions of both a and c, namely c'' and a''. a a'' b c c'' Because ''..'' in b points to a before this change, shall we modify b to let ''..'' point to a''? If yes,

Not sure how technically feasible it is, but something I thought of while shuffling some files around my home server. My poor understanding of ZFS internals is that the entire pool is effectivly a tree structure, with nodes either being data or metadata. Given that, couldnt ZFS just change a directory node to a filesystem with little effort, allowing me do everything ZFS does with filesystems on

Here is a proposal for a new ''copies'' property which would allow different levels of replication for different filesystems. Your comments are appreciated! --matt A. INTRODUCTION ZFS stores multiple copies of all metadata. This is accomplished by storing up to three DVAs (Disk Virtual Addresses) in each block pointer. This feature is known as "Ditto Blocks". When

Here is a proposal for a new ''copies'' property which would allow different levels of replication for different filesystems. Your comments are appreciated! --matt A. INTRODUCTION ZFS stores multiple copies of all metadata. This is accomplished by storing up to three DVAs (Disk Virtual Addresses) in each block pointer. This feature is known as "Ditto Blocks". When