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 08:12:28 +0100 [thread overview]
Message-ID: <20090622081228.5306c157@zaphod.digimed.co.uk> (raw)
In-Reply-To: <a0811460906211813r2eda5207qd89dc288d8d4ea68@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1686 bytes --]
On Sun, 21 Jun 2009 19:13:19 -0600, Maxim Wexler wrote:
> >> mount: /dev/vg/tmp already mounted on /tmp
> >> mount: tmpfs already mounted on /tmp
> >
> > It's nothing to do with your problem, but why are you mounting two
> > filesystems on /tmp?
>
> fstab:
> ...
> shm /dev/shm tmpfs nodev,nosuid,noexec 0 0
> tmpfs /tmp tmpfs nodev,nosuid,noexec 0 0 #suggested in a forum,
> seems harmless enough
It is, but you're also mounting /dev/fg/tmp on /tmp.
> > I still think there may be a delay in the kernel seeing the SD card,
> > this used to happen with my Eee. Have you tried adding a sleep
> > command to the relevant part of init.d/bootmisc?
>
> Not yet. What is the 'relevant' part? Is this the same thing as adding
> a delay to the kernel line in grub?
Actually, it's /etc/init.d/localmount, not bootmisc. Add a sleep command
just before No, you'de need to edit the bootmisc script and add a sleep
command just before
ebegin "Mounting local filesystems"
> > How large is the SSD in your Eee? Is it really necessary to have a
> > volume group spanning the SSD and SD card, two very different devices?
>
> Asus SSD, 4G SD card 8G
Ah, I thought only the 701 had the small SSD.
> 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).
--
Neil Bothwick
Windows to 486/50 mhz cpu: Don't rush me, don't rush me...
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2009-06-22 7:12 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 [this message]
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
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=20090622081228.5306c157@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