similar to: zlib vs lzo uncompress speed, ssd vs nossd

Unfortunately my laptop deadlocks from time to time, and too often it triggers this bug in btrfs which is quite hard to recover from. The bigger problem is that all the user sees (if anything) is seemingly unrelated info, namely, "RIP: btrfs_num_copies+0x42/0x0b" or somesuch http://marc.merlins.org/tmp/btrfs_num_copies.jpg It''s only if you have serial console, or netconsole,

Is this useful to anyone? Got this after a crash/reboot: if (block_rsv) { WARN_ON(block_rsv->size > 0); <<<<<<<<<<<<<<<<<<<<<< btrfs_free_block_rsv(root, block_rsv); } ------------[ cut here ]------------ WARNING: at fs/btrfs/inode.c:2165 btrfs_orphan_commit_root+0xcb/0xdf() Hardware name: 2429A78 Modules linked in:

Hi everybody, I am using btrfs as my main fs for some time now, but I am experiencing severe performance drawbacks. I can''t qualify the circumstances, but sometimes during disc access the whole system freezes for some time. Maybe somebody could suggest some general things I could try to search for the problem? Thanks in advance, Florian --- Some background information: $ mount |

In btrfs if we mount with "compress" we have no way to disable compressing by remounting (mount -o remount /mnt/btrfs), only by unmounting and mounting without "compress". This patch adds "nocompress" mount option which can be used to remount the filesystem without compression: # mount -o remount,nocompress /mnt/btrfs This option is usefull in cases when we have a

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

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

Since I heard absolutely nothing on my last but and corruption report, I''m not sure if they are useful or wanted (please let me know). The last thing I''ve seen with 3.4.4 is this: kernel: [116130.309667] btrfs: unlinked 25 orphans kernel: [117951.440823] BUG: Bad rss-counter state mm:ffff8801e2a4c080 idx:1 val:-1 kernel: [117951.440832] BUG: Bad rss-counter state

- 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

I asked the debian maintainer to add btrfs-zero-log to the initramfs since I unfortunately have to use it from time to time. It still fixes the problem for me when btrfs won''t mount, but it errors at the end. See screenshot Marc -- "A mouse is a device used to point at the xterm you want to type in" - A.S.R. Microsoft is to operating systems ....

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(-)

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

I don't know if this has been requested before, but I would really like for rsync to compute an md5sum for each file at the source and destination (with a flag turned off by default of course), and it would realize that I renamed files at the source by noticing a matching md5sum between different filenames It would then rename the destination instead of deleting it and resending the entire

Hi, I was hoping to use wine to run one of those stupid windows binaries that generate a floppy (at least IBM has a clue, and also offers the raw floppy image for dd-ing) In this case, the culprit is seagate's seatools: http://www.seagate.com/support/seatools/ I installed wine under debian unstable (Version: 0.0.20010824-1) and when I run the windows binary under wine, it runs but

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

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.

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