similar to: Btrfs and more compression algorithms

> -----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:

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

> On 7. Sep 2020, at 12.38, Miloslav H?la <miloslav.hula at gmail.com> wrote: > > Hello, > > I sent this into the Linux Kernel Btrfs mailing list and I got reply: "RAID-1 would be preferable" (https://lore.kernel.org/linux-btrfs/7b364356-7041-7d18-bd77-f60e0e2e2112 at lechevalier.se/T/). May I ask you for the comments as from people around the Dovecot? > >

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

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

Good day. I''m experiencing a kernel oops when systemd tries to fsck and mount several btrfs filesystems pretty much simultaneously on boot. Oops is highly reproducible for me and causes system to hang, sometimes triggering some kind of oops-loop, dumping backtraces into console until the power is killed. I''ve mentioned systemd (init system, like sysvinit or upstart), because I

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

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

>>>>> "Miloslav" == Miloslav H?la <miloslav.hula at gmail.com> writes: Miloslav> Hello, Miloslav> I sent this into the Linux Kernel Btrfs mailing list and I got reply: Miloslav> "RAID-1 would be preferable" Miloslav> (https://lore.kernel.org/linux-btrfs/7b364356-7041-7d18-bd77-f60e0e2e2112 at lechevalier.se/T/). Miloslav> May I ask you

The 9361-8i does support passthrough ( JBOD mode ). Make sure you have the latest firmware. On Wednesday, 09/09/2020 at 03:55 Miloslav H?la wrote: Hi, thank you for your reply. I'll continue inline... Dne 09.09.2020 v 3:15 John Stoffel napsal(a): > Miloslav> Hello, > Miloslav> I sent this into the Linux Kernel Btrfs mailing list and I got reply: > Miloslav> "RAID-1

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,

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:

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:

>>>>> "Miloslav" == Miloslav H?la <miloslav.hula at gmail.com> writes: Miloslav> Hi, thank you for your reply. I'll continue inline... Me too... please look for further comments. Esp about 'fio' and Netapp useage. Miloslav> Dne 09.09.2020 v 3:15 John Stoffel napsal(a): Miloslav> Hello, Miloslav> I sent this into the Linux Kernel Btrfs

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

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,

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

Mark Haney wrote: > On 09/08/2017 01:31 PM, hw wrote: >> Mark Haney wrote: >> >> I/O is not heavy in that sense, that?s why I said that?s not the application. >> There is I/O which, as tests have shown, benefits greatly from low latency, which >> is where the idea to use SSDs for the relevant data has arisen from. This I/O >> only involves a small amount of

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

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