> Is there a way to set options like compression on a btrfs permanently to
> activate them even when mounted automatically by the desktop or manually
> by a third person?
Actually there is.
Btrfs supports per file compression flag, and if this flag is set to a
directory, all files in that directo
Hadmut Danisch wrote (ao):
> I currently don't see how to repair this afterwards without removing the
> uncompressed files and writing new ones, which on the other hand spoils
> hte memory saving effect of using snapshots instead of copies.
As also mentioned by Li Zefan, you can use defrag. But th
>> I currently don't see how to repair this afterwards without removing the
>> uncompressed files and writing new ones, which on the other hand spoils
>> hte memory saving effect of using snapshots instead of copies.
>
> A rebalance is the usual way of handling such things, since that rewrites
>
Roman Mamedov posted on Sat, 28 Jan 2012 14:23:44 +0600 as excerpted:
> On Sat, 28 Jan 2012 17:05:41 +1100 Ben Klein
> wrote:
>
>> If the compression routine changes in a later kernel/filesystem
>> revision,
>
> There are already two different algorithms, zlib and lzo, and a third
> one - snapp
On Sat, Jan 28, 2012 at 7:49 AM, Hadmut Danisch wrote:
> Am 28.01.2012 00:20, schrieb Chester:
>> It should be okay to mount with compress or without compress. Even if
>> you mount a volume with compressed data without '-o compress' you will
>> still be able to correctly read the data (but newly w
On 28 January 2012 19:23, Roman Mamedov wrote:
> On Sat, 28 Jan 2012 17:05:41 +1100
> Ben Klein wrote:
>
>> If the compression routine changes in a later kernel/filesystem revision,
>
> There are already two different algorithms, zlib and lzo, and a third one -
> snappy - planned for inclusion.
>
On Sat, 28 Jan 2012 17:05:41 +1100
Ben Klein wrote:
> If the compression routine changes in a later kernel/filesystem revision,
There are already two different algorithms, zlib and lzo, and a third one -
snappy - planned for inclusion.
> then you could end up with some files using one routine a
On 28 January 2012 14:32, Duncan <1i5t5.dun...@cox.net> wrote:
> Hadmut Danisch posted on Sat, 28 Jan 2012 01:49:26 +0100 as excerpted:
>
>> Am 28.01.2012 00:20, schrieb Chester:
>>> It should be okay to mount with compress or without compress. Even if
>>> you mount a volume with compressed data wi
Hadmut Danisch posted on Sat, 28 Jan 2012 01:49:26 +0100 as excerpted:
> Am 28.01.2012 00:20, schrieb Chester:
>> It should be okay to mount with compress or without compress. Even if
>> you mount a volume with compressed data without '-o compress' you will
>> still be able to correctly read the d
Am 28.01.2012 00:20, schrieb Chester:
> It should be okay to mount with compress or without compress. Even if
> you mount a volume with compressed data without '-o compress' you will
> still be able to correctly read the data (but newly written data will
> not be compressed)
But having both compre
On Fri, Jan 27, 2012 at 9:03 AM, Hadmut Danisch wrote:
> Hi,
>
> just a question:
>
> Mounting options for file systems are usually given on the command line
> or in /etc/fstab.
>
> Both do not work with mobile storage devices like usb hard disks, since
> they are either mounted automatically thro
Hi,
just a question:
Mounting options for file systems are usually given on the command line
or in /etc/fstab.
Both do not work with mobile storage devices like usb hard disks, since
they are either mounted automatically through the desktop, or manually
by a user who does not know or remember th
12 matches
Mail list logo
