public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alexander Skwar <listen@alexander.skwar.name>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Gentoo LVM Newbie Question
Date: Sat, 25 Feb 2006 12:11:02 +0100	[thread overview]
Message-ID: <44003B46.1040707@mid.email-server.info> (raw)
In-Reply-To: <4400350B.4030104@gmx.net>

Jarry wrote:
> Alexander Skwar wrote:
> 
>>>I could not resize /usr or /var off-line,
>> 
>> That's wrong. I suppose that those are your ext* fs?
>> If so, you can perfectly fine resize those fs while
>> they are offline.
> 
> I mean I can not resize them off-line because I can not unmount them
> while system is running :-)

Ah, okay, that's how you meant it. In that case, you're right.

>>>Then maybe I should get rid of lvm2...
>> 
>> No. Get rid of ext*. reiser3 and xfs are mature, use those instead.
> 
> Hm, about half year ago I asked which fs to use. I counted
> votes, and ext3 won (reiser was 2nd).

Did I vote? If not, I probably would not have voted for
ext*. Well, actually, I *DO* use ext*. ext2 for /boot and
ext3 for /, as those are FS, which I will close to never ever
resize.

> Nobody mentioned that
> reiserfs can be resized on-line,

I must have missed that thread back then :)

> ext3 not (only off-line).

Well, ext3 *CAN* be resized online, with the appropriate
patches. Would I recommend that? No, I wouldn't, because
I have got no experience with those patches. For the same
reason, I wouldn't recommend to NOT use it.

Alexander Skwar
-- 
There are never any bugs you haven't found yet.
-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2006-02-25 11:14 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-23 20:22 [gentoo-user] Gentoo LVM Newbie Question CR Little
2006-02-23 20:41 ` Boyd Stephen Smith Jr.
2006-02-23 20:59 ` Alexander Skwar
2006-02-23 21:15 ` Qv6
2006-02-23 21:59 ` John Jolet
2006-02-23 22:35   ` Boyd Stephen Smith Jr.
2006-02-24  6:03   ` Alexander Skwar
2006-02-25  3:35     ` Zac Slade
2006-02-25  4:13       ` John Jolet
2006-02-25  4:32         ` Zac Slade
2006-02-25  5:14           ` John Jolet
2006-02-25  6:52             ` Alexander Skwar
2006-02-25  6:44         ` Alexander Skwar
2006-02-25  6:43       ` Alexander Skwar
2006-02-25 11:24         ` Holly Bostick
2006-02-25 12:21           ` Alexander Skwar
2006-02-25  7:55       ` Jarry
2006-02-25 10:26         ` Alexander Skwar
2006-02-25 10:44           ` Jarry
2006-02-25 11:11             ` Alexander Skwar [this message]
2006-02-25 15:01             ` [gentoo-user] [OT] " Boyd Stephen Smith Jr.
2006-02-27  6:48             ` [gentoo-user] " Dirk Heinrichs
2006-02-28  5:01               ` Zac Slade
2006-02-28  9:03                 ` Dirk Heinrichs
2006-02-28  9:23                   ` Zac Slade
2006-02-28  9:29                 ` Boyd Stephen Smith Jr.
2006-02-28 13:53                   ` Dirk Heinrichs
  -- strict thread matches above, loose matches on Subject: below --
2006-02-23 20:58 CR Little
2006-02-23 21:36 ` Boyd Stephen Smith Jr.
2006-02-23 21:41 CR Little
2006-02-23 23:29 CR Little
2006-02-23 23:57 ` Boyd Stephen Smith Jr.
2006-02-24 14:40 CR Little

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=44003B46.1040707@mid.email-server.info \
    --to=listen@alexander.skwar.name \
    --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