public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] lvm problem -- is timing?
Date: Mon, 22 Jun 2009 23:25:02 +0100	[thread overview]
Message-ID: <20090622232502.1bdba464@zaphod.digimed.co.uk> (raw)
In-Reply-To: <a0811460906221109i69cdd2fdq9006c3df13c94ff6@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1215 bytes --]

On Mon, 22 Jun 2009 12:09:52 -0600, Maxim Wexler wrote:

> >> Necessary? Don't know but is meant to spare the SSD too much r/w
> >> strain.  
> >
> > How? By spanning an LVM across the two, you have no control over
> > which is written to the most. I'd put / on the SSD then mount
> > write-heavy directories, like /var and /home, on the SD card. I'd
> > also set $PORTDIR to /var/portage (/usr is a daft place to put the
> > portage tree anyway).  
> 
> That's what I have, I think,  sda1 is /boot approx 50M , sda2 is /
> approx 1G,  then the rest of the SSD is spanned with the SD card,
> approx 11G, and committed to /usr /home /opt /var and /tmp just as in
> the gentoo doc LVM2.

How does that spare the SSD when frequently written directories,
like /var and /usr/portage on partially on the SSD? If you want to keep
them off the SSD, you must not use LVM like this.

Forget LVM, forget a separate /boot, just stick / on the SSD and mount
the likes of /var on the SD card. I use LVM on my Eee, but that's because
it has two SSDs, I wouldn't dream of including the SD card in there.


-- 
Neil Bothwick

C&W music backward: get yer dog, wife, job, truck, kids, and sobriety
back.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2009-06-22 22:25 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-20  4:15 [gentoo-user] lvm problem -- is timing? Maxim Wexler
2009-06-20  5:33 ` Mike Kazantsev
2009-06-20  7:08   ` Dirk Heinrichs
2009-06-20  7:37     ` Mike Kazantsev
2009-06-20  9:01       ` Dirk Heinrichs
2009-06-20 11:56         ` Mike Kazantsev
2009-06-20 12:46           ` Dirk Heinrichs
2009-06-20 19:23     ` Maxim Wexler
2009-06-20 20:26       ` Dirk Heinrichs
2009-06-20 20:34         ` Dirk Heinrichs
2009-06-20 19:14   ` Maxim Wexler
2009-06-20 20:23     ` Dirk Heinrichs
2009-06-20 20:48       ` Dirk Heinrichs
2009-06-20 23:51         ` Maxim Wexler
2009-06-21  7:57           ` Dirk Heinrichs
2009-06-21 21:16             ` Maxim Wexler
2009-06-21 21:32               ` Maxim Wexler
2009-06-21 21:49               ` Neil Bothwick
2009-06-21 22:17                 ` Ian Lee
2009-06-22  1:20                   ` Maxim Wexler
2009-06-22 16:43                     ` Dirk Heinrichs
2009-06-22 17:23                       ` Maxim Wexler
2009-06-22  1:13                 ` Maxim Wexler
2009-06-22  7:12                   ` Neil Bothwick
2009-06-22 17:42                     ` Maxim Wexler
2009-06-22 22:20                       ` Neil Bothwick
2009-06-22 18:09                     ` Maxim Wexler
2009-06-22 22:25                       ` Neil Bothwick [this message]
2009-06-23  2:12                         ` Maxim Wexler
2009-06-23  7:32                           ` Neil Bothwick
2009-06-23 19:15                             ` Maxim Wexler
2009-06-23 21:09                               ` Alan McKinnon
2009-06-23 21:36                               ` Neil Bothwick
2009-06-23 21:59                                 ` Maxim Wexler
2009-06-23 22:03                                   ` Neil Bothwick
2009-06-24 20:10                                     ` Maxim Wexler
2009-06-22 16:49               ` Dirk Heinrichs
2009-06-22 17:33                 ` Maxim Wexler
2009-06-22 22:21                   ` Neil Bothwick

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=20090622232502.1bdba464@zaphod.digimed.co.uk \
    --to=neil@digimed.co.uk \
    --cc=gentoo-user@lists.gentoo.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