I am trying to add some hooks to support different compression types
In end_compressed_bio_read(struct bio *bio, int err) (compression.c)
does anyone know how can i read the compression_type flag set for the
current extent being read for decompression.
I was looking at using
Hi,
I hope that ideas about btrfs are not off-topic for this mailing list.
The forwarded message below was written by me on fedora-users.
The thread is about the ability to link two files in a manner
similar to cat 1 2 3 rm 1 2 while avoiding any data
movement on the disk.
The implementation
On Wednesday 09 June 2010 13:53:00 Roberto Ragusa wrote:
Hi,
I hope that ideas about btrfs are not off-topic for this mailing list.
The forwarded message below was written by me on fedora-users.
The thread is about the ability to link two files in a manner
similar to cat 1 2 3 rm 1 2
I had a need to split a file into smaller files on a thumb drive with no
free space on it or anywhere else in the system. When the filesystem
supports sparse files(truncate_range), I could create files, while
punching holes in the original file. But when the underlying fs is FAT,
I couldn't. Also
Roberto Ragusa m...@robertoragusa.it writes:
I hope that ideas about btrfs are not off-topic for this mailing list.
The forwarded message below was written by me on fedora-users.
The thread is about the ability to link two files in a manner
similar to cat 1 2 3 rm 1 2 while avoiding any
On Wed, 9 Jun 2010, Roberto Ragusa wrote:
I hope that ideas about btrfs are not off-topic for this mailing list.
The forwarded message below was written by me on fedora-users.
The thread is about the ability to link two files in a manner
similar to cat 1 2 3 rm 1 2 while avoiding any data
i'm not a C developer, but i like to think i know enough to be
dangerous (pragmatic) :-D
building from git master failed with:
..
..
gcc -Wp,-MMD,./.btrfsck.o.d,-MT,btrfsck.o -Wall -D_FILE_OFFSET_BITS=64
-D_FORTIFY_SOURCE=2 -g -Werror -Os -c btrfsck.c
cc1: warnings being treated
I just finished a rough (but working) implementation of in-kernel
page cache compression backend (called zcache). During this work,
I found some issues with cleancache, mostly related to (lack of)
comments/documentation:
Great to hear! And excellent feedback on the missing
documentation... I
