similar to: LZO versus LZJB

Deduplication was committed last night by Mr. Bonwick: > Log message: > PSARC 2009/571 ZFS Deduplication Properties > 6677093 zfs should have dedup capability http://mail.opensolaris.org/pipermail/onnv-notify/2009-November/010683.html Via c0t0d0s0.org.

Hi, I don''t know if this has been discussed before, but have you thought about adding LZO compression to ZFS? One zfs-fuse user has provided a patch which implements LZO compression, and he claims better compression ratios *and* better speed than lzjb. The miniLZO library is licensed under the GPL, but the author specifically says that other licenses are available by request. Has this

I just setup a new SSD with my laptop root filesystem, and at the time I though, "eh, I''ll just use zlib compression during the first copy, and then switch to lzo afterwards to maintain write speed when I''m using the laptop after the copy and reboot". Now, I rebooted with the new ssd and zlib compressed rootfs, and it seemed to boot slower than it did before with the

Hi all, as suggested on the mailing list I have converted the updated LZO code into git, so please pull my "lzo-update" branch from git://github.com/markus-oberhumer/linux.git lzo-update You can browse the branch at https://github.com/markus-oberhumer/linux/compare/lzo-update I''d ask some official kernel maintainer for review and to push this into linux-next so that it

Hello, I try to install tinc under cygwin. When I make an ./configure with tinc-1.0.1 I get the error-message checking for lzo1x_1_compress in -llzo... no configure: error:"lzo libraries not found" I have installed lzo-1.08. But it was not from the cygwin-Homepage and so I think that there was a wrong installation-path for the lzo-libraries. How can I find out where to install the

Hi, I planned to boost my btrfs performance today. here some errors I met: my ''btrfs filesystem show'' result: ~ # btrfs filesystem show failed to read /dev/sr0 Label: none uuid: 9b9aa9d9-760e-445c-a0ab-68e102d9f02e Total devices 1 FS bytes used 36.59GB devid 1 size 49.52GB used 49.52GB path /dev/sda6 Label: none uuid: 559dec06-4fd0-47c1-97b8-cc4fa6153fa0

- Add incompat flag, otherwise btrfs-progs will report error when operating on btrfs filesystems mounted with lzo option. - Allow to turn on lzo compression for defrag operation: # btrfs filesystem defragment -c[zlib, lzo] <file> Note: "-c zlib" will fail, because that''s how getopt() works for optional arguments. Signed-off-by: Li Zefan

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

The prescription for Boot Info Table says that checksumming begins at byte 64 of isolinux.bin. When prepcore writes isolinux.bin it begins copying bytes from the input file at the offset given by variable "start". But it begins checksumming at offset 64 of the input file. The problem exists since introduction of prepcore by release 4.00. ISO 9660 programs usually fix it when they write

The size of de/compress buffer and LZO1X_MEM_COMPRESS is small enough. Allocating it with kmalloc rather than vmalloc is preferred. This patch depends on my previous patch, “btrfs: fix decompress buffer size”. Signed-off-by: Kyungsik Lee <kyungsik.lee@lge.com> Cc: David Sterba <dsterba@suse.cz> --- fs/btrfs/lzo.c | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-)

I''ve noticed that: - with x86-64 Fedora 15 DVD install images: - du -sh <ROOT VOLUME> was 36 GB - btrfs df | grep -i data have shown over 40 GB used - without - du -sh <ROOT VOLUME> is 34 GB - btrfs df | grep -i data have shown less then 34 GB used It seems that iso files are considered compressable while they may not be (and penalty is severe - 3x). Regards

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

CentOS Errata and Security Advisory 2014:0861 Moderate Upstream details at : https://rhn.redhat.com/errata/RHSA-2014-0861.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 5573a762c075a0d03f070c6bd0b47c41311fff66e21e034863d514ee65d8c081 lzo-2.03-3.1.el6_5.1.i686.rpm

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I've added lzo compression support for tinc 1.0pre8. Lzo is a very fast compressor (see http://www.oberhumer.com/opensource/lzo/). I've implemented it by using two new compression levels. Compression level 10 is for fast compression using lzo1x-1 algorithm. Compression level 11 is for slow compression using lzo1x-999 algorithm.

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

CentOS Errata and Security Advisory 2014:0861 Moderate Upstream details at : https://access.redhat.com/errata/RHSA-2014:0861 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 898c40521dfa677aa2217a083a9f382618b359d7a1a0361167427123f3397632 lzo-2.06-6.el7_0.2.i686.rpm

[adding libguestfs list, for nbdkit reference below] On 10/4/18 8:39 AM, Stefan Fröberg wrote: > Hello. > Is it possible to improve NBD throughtput with LZO compression ? As in, have a way for the client and server to negotiate that both understand an LZO extension, at which point the client can request a read or write with a flag set to mark that the data is LZO-compressed, for less

Summary: If you use ZFS, do not downgrade from build 35 or later to build 34 or earlier. This putback (into Solaris Nevada build 35) introduced a backwards- compatable change to the ZFS on-disk format. Old pools will be seamlessly accessed by the new code; you do not need to do anything special. However, do *not* downgrade from build 35 or later to build 34 or earlier. If you do so, some of

Originated/took from Steffen Winterfeldt and Michael Matz in opensuse's Syslinux package: https://bugzilla.opensuse.org/show_bug.cgi?id=1125616 "fix lzo memory aliasing issue" --- lzo/Makefile +++ lzo/Makefile @@ -19,6 +19,8 @@ LIB = lzo.a BINS = prepcore +OPTFLAGS += -fno-strict-aliasing + all : makeoutputdirs $(BINS) makeoutputdirs: -- -Ady

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