From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: compression on external hard drive?
Date: Sun, 26 May 2013 02:23:09 +0000 (UTC) [thread overview]
Message-ID: <pan$a1b3e$c3ed264b$c0ac127c$7262bed0@cox.net> (raw)
In-Reply-To: 51A1372B.6060402@gnata.eu
Xavier Gnata posted on Sun, 26 May 2013 00:11:55 +0200 as excerpted:
> Nowdays, external hard drives are mounted automagically by kde, gnome or
> whatever else.
> How is it suppose to work with external hard drives using btrfs with
> compression?
> If a btrfs filesystem lzo-compressed is mounted without the
> |compress=|xxx option then all the newly created files are uncompressed,
> aren't then?
> Would it be possible to detect if a file system is compressed and to
> mount it *automatically* and accordingly (except otherwise explicitly
> stated by the user) with/without the lzo/gzip option?
There's a proposal to do something like ext3/4's default options as set
by tune2fs, at some point, presumably before btrfs loses the "unstable
disk format" and under heavy development warnings. However, there's
nothing like that yet, AFAIK, so most options must be set per-mount.
There's a lot you can do with udev events, however, and strongly suspect
either compression-detection, or match-against-a-list-and-compress (or
don't compress if the default is compression otherwise) if the UUID/LABEL
is listed.
Alternatively, at least kde can be set not to automount specific UUIDs/
LABELs, and then there's always the traditional fstab option, and I think
either fstab entered drives are ignored by the automount system or
they're automounted with options from fstab (I have that kde subsystem
entirely disabled here so it doesn't automount anything, so I'm not sure
which it actually does).
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2013-05-26 2:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-25 22:11 compression on external hard drive? Xavier Gnata
2013-05-26 2:23 ` Duncan [this message]
2013-05-26 12:03 ` xavier.gnata
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='pan$a1b3e$c3ed264b$c0ac127c$7262bed0@cox.net' \
--to=1i5t5.duncan@cox.net \
--cc=linux-btrfs@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).