Displaying 20 results from an estimated 9000 matches similar to: "Btrfs and more compression algorithms"
2011 Feb 16
2
RE: [PATCH V2 0/3] drivers/staging: zcache: dynamic page cache/swap compression
> -----Original Message-----
> From: Matt [mailto:jackdachef@gmail.com]
> Sent: Tuesday, February 15, 2011 5:12 PM
> To: Minchan Kim
> Cc: Dan Magenheimer; gregkh@suse.de; Chris Mason; linux-
> kernel@vger.kernel.org; linux-mm@kvack.org; ngupta@vflare.org; linux-
> btrfs@vger.kernel.org; Josef Bacik; Dan Rosenberg; Yan Zheng;
> miaox@cn.fujitsu.com; Li Zefan
> Subject:
2009 Aug 03
1
DO NOT REPLY [Bug 6603] New: Improve --skip-compress default values
https://bugzilla.samba.org/show_bug.cgi?id=6603
Summary: Improve --skip-compress default values
Product: rsync
Version: 3.0.6
Platform: Other
OS/Version: Windows XP
Status: NEW
Severity: normal
Priority: P3
Component: core
AssignedTo: wayned at samba.org
ReportedBy: jari.aalto at cante.net
2014 May 06
1
WG: on High Load using IMAPSYNC : Panic: file ostream-lzma.c: line 147: unreached. Dovecot 2.2.12 with zlib/XZ compression
when syncing Mailboxes with IMAPSYNC, using xz compression the dbox file
gets corrupted.
the same configuration was working ok on low load with xz compression.
Dovecot Version 2.2.12
Linux Mint 16
EXT4 Filesystem
another dovecot user already reported the same problem on the mailinglist,
using dsync. That user switched to bz2 compression what worked for him.
the answer was :
> are you on
2014 May 06
0
on High Load using IMAPSYNC : Panic: file ostream-lzma.c: line 147: unreached. Dovecot 2.2.12 with zlib/XZ compression
when syncing Mailboxes with IMAPSYNC, using xz compression the dbox file
gets corrupted.
the same configuration was working ok on low load with xz compression.
Dovecot Version 2.2.12
Linux Mint 16
EXT4 Filesystem
another dovecot user already reported the same problem on the mailinglist,
using dsync. That user switched to bz2 compression what worked for him.
the answer was :
> are you on
2012 Nov 03
0
btrfs kernel threads producing high load and slow system down
Hello,
I habe the problems described in here
https://btrfs.wiki.kernel.org/index.php/Gotchas:
Files with a lot of random writes can become heavily fragmented
(10000+ extents) causing trashing on HDDs and excessive multi-second
spikes of CPU load on systems with an SSD or large amount a RAM.
On servers and workstations this affects databases and virtual machine images.
The nodatacow mount option
2015 Mar 02
2
[LLVMdev] clang change function name
Hi,
I compile a .cpp with cmd:
clang++ -emit-llvm -c -g -O0 -w pbzip2.cpp -o pbzip2.bc -lbz2
llvm-dis pbzip2.bc
One function in .cpp is consumer_decompress. However, I look inside
pbzip2.ll. The function name is changed to "define i8*
@_Z19consumer_decompressPv(i8* %q) #0 {"
Why clang adds a "_Z19" prefix and "Pv" suffix?
Thanks,
2014 Mar 28
1
Panic: file ostream-lzma.c: line 147: unreached. Dovecot 2.2.12 with zlib/XZ compression
While migrating users from Cyrus IMAP v2.3.14 to Dovecot 2.2.12
(compiled from source) dsync aborts with a backtrace on some (maybe 15
out of 800) mail accounts:
(same error happens wiht or without -f flag)
dsync -D -v -o mail_fsync=never mirror -f -R -u user at domain imapc:
<snip>
dsync(user at domain.com): Debug: brain M: in state=sync_mails
dsync(user at domain.com): Debug: brain M:
2013 Dec 12
1
error with xz compression
i have enabled the zlib plugin with xz compression but on some new
mails i got now a segfault and the following lines in dovecot error.log
Dec 12 08:51:23 imap(tester at domain.com): Error:
lzma.read(/srv/vmail/mail/domain.com/root/storage/m.3): unexpected EOF
at 136004
Dec 12 08:51:23 imap(tester at domain.com): Error:
read(zlib(/srv/vmail/mail/domain.com/root/storage/m.3)) failed:
2015 Mar 02
2
[LLVMdev] clang change function name
Got it, thanks. But in my pass, I use function name to locate. Can I
disable mangling in clang?
Best,
Haopeng
On 3/1/15 10:44 PM, John Criswell wrote:
> On 3/1/15 11:38 PM, Haopeng Liu wrote:
>> Hi,
>>
>> I compile a .cpp with cmd:
>> clang++ -emit-llvm -c -g -O0 -w pbzip2.cpp -o pbzip2.bc -lbz2
>> llvm-dis pbzip2.bc
>>
>> One function in .cpp is
2015 Jan 15
0
Request to speed up save()
In addition to the major points that others made: if you care about speed, don't use compression. With today's fast disks it's an order of magnitude slower to use compression:
> d=lapply(1:10, function(x) as.integer(rnorm(1e7)))
> system.time(saveRDS(d, file="test.rds.gz"))
user system elapsed
17.210 0.148 17.397
> system.time(saveRDS(d,
2013 Jun 15
1
Bug#712366: xen: FTBFS: configure: error: Could not find libcrypto
Source: xen
Version: 4.2.1-2
Severity: serious
Tags: jessie sid
User: debian-qa at lists.debian.org
Usertags: qa-ftbfs-20130609 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part:
> make[2]: Entering directory `/?PKGBUILDDIR?'
> mkdir -p debian/build/build-utils_amd64
> cp -al CODING_STYLE COPYING
2015 Jan 15
4
Request to speed up save()
Hi,
I am dealing with very large datasets and it takes a long time to save a
workspace image.
The options to save compressed data are: "gzip", "bzip2" or "xz", the
default being gzip. I wonder if it's possible to include the pbzip2
(http://compression.ca/pbzip2/) algorithm as an option when saving.
"PBZIP2 is a parallel implementation of the bzip2
2011 Jun 23
0
Using compression on SSD
Hi!
I scanned for relevant topics in the last two years but except for putting
a swap file on compress=lzo this march I didnĀ“t found anything.
Does compression make sense on SSD? Or more specifically:
1) In what chunk sizes does BTRFS compress? How much data is affected when
a byte is changed in a 2 GB file or so? Can compression cause more writes
to the SSD in extreme circumstances?
2) It
2012 Oct 21
3
unrecognized mount option 'compression=lzo' and defragment -c errors
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
2018 Jan 31
0
How is initrd.img packed and compressed?
Don't archive as lzma if you don't want lzma, remove the "--format=lzma" parameter.
hth
Lucian
--
Sent from the Delta quadrant using Borg technology!
Nux!
www.nux.ro
----- Original Message -----
> From: "Mircea Husz" <mirceahusz at yahoo.com>
> To: "CentOS mailing list" <centos at centos.org>
> Sent: Wednesday, 31 January, 2018
2015 Aug 30
2
[OFFTOPIC] integrated LSI 3008 :: number of hdd support
Hi guys! Unfortunately there is no offtopic list but the subject
is somehow related to centos as the OS is/will be centos :)
So, under this thin cover i ask :
Is it possible that for a SAS controler like LSI 3008 that in specs
says that : "This high-performance I/O controller supports T-10
data protection model and optical support, PCIe hot plugging,
and up to 1,000 connected devices"
2012 Jul 24
1
[PATCH v4] Btrfs: Check INCOMPAT flags on remount and add helper function
In support of the recently added capability to remount with lzo
compression, provide a helper function to check the compression
INCOMPAT flags when remounting with lzo compression, and set
the flags if necessary.
Also, implement the new helper function when defragmenting with
explicit lzo compression and when setting the default subvolume.
Signed-off-by: Mitch Harder
2015 Aug 30
0
[OFFTOPIC] integrated LSI 3008 :: number of hdd support
In my experience the mass market HBAs and RAID cards typically do support
only 8 or 16 drives. For the internal variety in a standard rack-mount
server you'll usually see either 2 or 4 iPass cables (each of which support
4 drives) connected to the backplane. The marketing material you've
referenced has a white lie in it: supporting more than 16 drives on a
single card is very likely only
2009 Jan 11
1
lzma and bzip compressed kernels, initrds and images
hpa, will there be support for lzma and bzip compressed kernels, initrds and images in one of the following releases of syslinux?
I saw that you want lzma and bzip2 compression included in the kernel:
http://groups.google.com/group/linux.kernel/browse_thread/thread/f415aa765c09c9f7/dae008992e14840f?lnk=raot&pli=1
Gert Hulselmans
2010 Aug 05
0
[LLVMdev] a problem when using postDominatorTree
I'll try the trunk, as well as check my code again. If indeed it's not
fixed, I'll try to post a triggering case here.
Thanks for the advice~
Best,
--Wenbin
----- Original Message -----
From: "Tobias Grosser" <grosser at fim.uni-passau.de>
To: "Wenbin Zhang" <zhangwen at cse.ohio-state.edu>
Cc: <llvmdev at cs.uiuc.edu>
Sent: Thursday, August