From: Hadmut Danisch <hadmut@danisch.de>
To: Chester <somethingsome2000@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Setting options permanently?
Date: Sat, 28 Jan 2012 01:49:26 +0100 [thread overview]
Message-ID: <4F234616.6020407@danisch.de> (raw)
In-Reply-To: <CAAE6i0gSG4xuyJFQrmfFNh3ojF4GBbsgk7LsN+1XD=9Mp5rSUQ@mail.gmail.com>
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 wil=
l
> still be able to correctly read the data (but newly written data will
> not be compressed)
But having both compressed and uncompressed files in the filesystem is
exactly what I want to avoid. Not because of reading problems, but to
avoid wasting disk space. I don't have a reading problem. I have a
writing problem.
I want to pack some data onto USB hard disks, which exceed the plain
disk capacity. With btrfs it works exactly the way as I need it, except
for the fact that once the compress option was missed the file system i=
s
=84tainted=94 with uncompressed files, thus wasting disk capacity and m=
aybe
cause the files to not fit on the disk anymore.
I currently don't see how to repair this afterwards without removing th=
e
uncompressed files and writing new ones, which on the other hand spoils
hte memory saving effect of using snapshots instead of copies.
It would be much better if there was a way to set options like the
compression option permanently when initially creating the file system,
or later with the btrfs tools.
regards
Hadmut
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-01-28 0:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-27 15:03 Setting options permanently? Hadmut Danisch
2012-01-27 23:20 ` Chester
2012-01-28 0:49 ` Hadmut Danisch [this message]
2012-01-28 3:32 ` Duncan
2012-01-28 6:05 ` Ben Klein
2012-01-28 8:23 ` Roman Mamedov
2012-01-28 9:24 ` Ben Klein
2012-01-28 10:55 ` Duncan
2012-01-30 5:57 ` Li Zefan
2012-01-28 12:07 ` Fajar A. Nugraha
2012-01-30 7:18 ` Sander
2012-01-30 7:49 ` Li Zefan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F234616.6020407@danisch.de \
--to=hadmut@danisch.de \
--cc=linux-btrfs@vger.kernel.org \
--cc=somethingsome2000@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.