From: Michael Tokarev <mjt@tls.msk.ru>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] LILO configuration for LVM "boot" filesystem
Date: Mon, 11 Jun 2001 04:20:38 +0400 [thread overview]
Message-ID: <3B240ED6.F8951EE8@tls.msk.ru> (raw)
In-Reply-To: 20010611120459.A26558@mail.wave.co.nz
Mark van Walraven wrote:
>
> On Fri, Jun 08, 2001 at 03:30:36PM +0200, Jens Benecke wrote:
> > On Fri, Jun 08, 2001 at 01:08:24AM +0400, Michael Tokarev wrote:
> > > Another thing to consider if you run 2.4 kernel -- mount tmpfs on /tmp
> > > (and give some reasonable size restrictions). This way, /tmp works much
> > > faster, does not need to be cleaned on boot, and will not eat root's
> > > space. You should have reasonable swap space it you plan to use it
> > > heavily. Works very well here.
> >
> > tmpfs? I thought that existed only on Solaris, and the primary reason for
> > tmpfs is that Solaris's UFS is so ssllooww compared to other FS (e.g.
> > ext2, reiser, etc.)
>
> It's in Linux 2.4 also. It has the same unfortunate problem as on Solaris,
> that once someone fills /tmp, you run out swap and daemons start dying.
Hey, do not allow users to fill it up! ;) There is a mount option for
tmpfs on linux that allows you to specify max size of a filesystem to
create.
About tmpfs and a "real" filesystems. No, ufs isn't so slow on solaris,
it is comparable with ext2, and faster sometimes (and slow other times),
it is hard to say which is better (I prefer ufs on solaris, as it is
more reliable with almost the same speed). But with any real on-disk fs,
it is impossible to skip writing to disk (as fs designed to store data,
not to loose it), while tmpfs shurely can skip writing if there is
enouth memory, or with short files (ext2 will update directory at least,
maybe batching that update for many files, but it will not eliminate
update if a file will be created and deleted shortly).
BTW, this started to be offtopic... ;)
Regards,
Michael.
next prev parent reply other threads:[~2001-06-11 0:20 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-04 8:07 [linux-lvm] LILO configuration for LVM "boot" filesystem Brian J. Murrell
2001-06-04 14:21 ` Ben Lutgens
2001-06-05 2:01 ` Brian J. Murrell
2001-06-05 11:56 ` Steven Lembark
2001-06-05 15:48 ` Jack McKinney
2001-06-05 18:32 ` Andreas Dilger
2001-06-06 4:07 ` Brian J. Murrell
2001-06-07 15:30 ` Steven Lembark
2001-06-07 15:43 ` Jack McKinney
[not found] ` <20010607182636.H3232@jensbenecke.de>
2001-06-07 16:32 ` Jack McKinney
[not found] ` <20010607191649.R3232@jensbenecke.de>
2001-06-07 19:18 ` Jack McKinney
2001-06-07 16:39 ` Mario 'BitKoenig' Holbe
2001-06-07 21:20 ` Steven Lembark
2001-06-08 2:27 ` Russell Coker
2001-06-07 21:18 ` Steven Lembark
2001-06-07 21:36 ` Steve Wray
2001-06-07 21:37 ` Steven Lembark
2001-06-07 21:52 ` Steve Wray
2001-06-07 22:15 ` Jack McKinney
2001-06-07 22:24 ` Steve Wray
2001-06-07 22:27 ` Steven Lembark
2001-06-07 22:23 ` Steven Lembark
2001-06-08 2:28 ` Russell Coker
2001-06-08 2:26 ` Russell Coker
2001-06-07 22:29 ` Mark van Walraven
2001-06-07 22:38 ` Steve Wray
2001-06-07 21:08 ` Michael Tokarev
[not found] ` <20010608153036.G21909@jensbenecke.de>
2001-06-11 0:04 ` Mark van Walraven
2001-06-11 0:10 ` Steven Lembark
2001-06-11 0:20 ` Michael Tokarev [this message]
2001-06-11 11:39 ` Russell Coker
2001-06-07 15:26 ` Steven Lembark
2001-06-05 18:00 ` Andreas Dilger
2001-06-04 17:56 ` Andreas Dilger
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=3B240ED6.F8951EE8@tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=linux-lvm@sistina.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.