All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jim Salter <jim@jrs-s.net>
To: linux-btrfs@vger.kernel.org, "dhan.war" <wardhan.v.1.0@gmail.com>
Subject: Re: how to properly mount an external usb hard drive & other questions
Date: Sun, 05 Jan 2014 13:09:33 -0500	[thread overview]
Message-ID: <52C99FDD.4090709@jrs-s.net> (raw)
In-Reply-To: <52C99E19.8020106@jrs-s.net>

On 01/05/2014 01:02 PM, Jim Salter wrote:
> If you want LZO compression, as you specified:
>
>           /dev/sdc /path/to/mountpoint compress=lzo,noauto,users,user 0 0
>
> Better yet, if your btrfs is actually on /dev/sdc right now, let's get 
> that fstab entry mounting it by UUID instead.
>
>           ls -l /dev/disk/by-uuid | grep sdc
>           lrwxrwxrwx 1 root root 10 Jan  3 09:40 
> 12345678-9abc0-1234-5678-9a0123456789 -> ../../sdc
>
> So then:
>
>           # this is not a real UUID, you need to check 
> /dev/disk/by-uuid on your machine for a real UUID
>           UUID=12345678-9abc0-1234-5678-9a0123456789 
> /path/to/mountpoint   compress=lzo,noauto,users,user   0   0
>
> This is EXTRA important with a USB drive, since it's HIGHLY likely it 
> won't always be on the same physical devicename.

One other note: in this particular case, you might actually be better 
served setting compression by mounting the drive normally, then:

          cd /path/to/drive
          chattr +c . ; chattr +c * ; chattr +c .*

This will set compression on by default for any future files stored on 
that USB drive, *without* needing any special mount options.

Why might this be a better idea? Well, if it's a USB drive, presumably 
you might want to mount it on foreign systems from time to time. This 
way, even if you mount the drive on a foreign system that doesn't know 
anything about your preferences, it will see the +c on the root 
directory of the drive, and store any new data on the drive compressed.

The only caveat: +c won't set the compression algorithm to LZO. It'll be 
gzip, which is the default algorithm. (And, of course, this won't 
compress any EXISTING data already stored there - only NEW data written 
to it after you set the +c attribute.)

      reply	other threads:[~2014-01-05 18:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-05  4:34 how to properly mount an external usb hard drive & other questions dhan.war
2014-01-05 17:43 ` Justus Seifert
2014-01-05 17:50   ` Justus Seifert
2014-01-05 18:02     ` Jim Salter
2014-01-05 18:09       ` Jim Salter [this message]

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=52C99FDD.4090709@jrs-s.net \
    --to=jim@jrs-s.net \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=wardhan.v.1.0@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.