public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Freeing up disk space problem!!
Date: Wed, 29 Feb 2012 11:19:56 +0200	[thread overview]
Message-ID: <20120229111956.21612f0d@khamul.example.com> (raw)
In-Reply-To: <4F4D8F95.7050307@gmail.com>

On Tue, 28 Feb 2012 20:38:13 -0600
Dale <rdalek1967@gmail.com> wrote:

> Alex Schuster wrote:
> > Dale writes:
> > 
> >> I have a question on this.  I have a drive that I use for movies
> >> and such.  There is nothing OS related on that drive.  Would it be
> >> safe to set this to say 1% or even 0? 
> > 
> > I'd say 1% is okay. For 0% I'm not sure, I avoid that, but maybe
> > there will be no noticeable difference at all. 
> > 
> >> Also, it is already set up with LVM and
> >> ext4.  Can I change it even while there is data on there?
> > 
> > Sure! Cool, isn't it. Just call lvresize -L
> > +1G /dev/mapper/whatever or something, and then
> > resize2fs /dev/mapper/whatever.
> 
> 
> I was talking about the command to change the superuser reserves.  I
> know how to make LVM bigger but wanted to make sure this can be run
> even when there is data on there.  Basically, can I run:
> 
> tune2fs -m 1 /dev/data/data1
> 
> Which is where the ext4 file system is on the LVM.  After I run that
> then I can expand LVM from there, I hope it works that easy.

They don't interfere with each other.

LVM and the size of the filesystem is one thing. Reserved space is
something else, completely unrelated.


> 
> 
> > 	Wonko
> > 
> > 
> 
> Dale
> 
> :-)  :-)
> 



-- 
Alan McKinnnon
alan.mckinnon@gmail.com




  parent reply	other threads:[~2012-02-29  9:21 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-28 11:37 [gentoo-user] Freeing up disk space problem!! trevor donahue
2012-02-28 11:52 ` Alan McKinnon
2012-02-28 13:37   ` William Kenworthy
2012-02-28 11:57 ` Mick
2012-02-28 11:59 ` [gentoo-user] " Nikos Chantziaras
2012-02-28 12:24 ` [gentoo-user] " YoYo Siska
2012-02-28 12:50   ` trevor donahue
2012-02-28 13:25     ` Neil Bothwick
2012-02-28 13:01 ` Alex Schuster
2012-02-28 13:27   ` Neil Bothwick
2012-02-28 23:25     ` Alex Schuster
2012-02-29  0:32       ` Neil Bothwick
2012-02-29  1:05         ` Alex Schuster
2012-02-29  6:22           ` Neil Bothwick
2012-02-29  9:29       ` Alan McKinnon
2012-02-29  9:57         ` Neil Bothwick
2012-02-29 10:40           ` Alan McKinnon
2012-02-29 11:08             ` Neil Bothwick
2012-02-29 12:11               ` Alan McKinnon
2012-03-01  0:59                 ` Frank Steinmetzger
2012-03-01  9:54                   ` Neil Bothwick
2012-02-29 23:59             ` [gentoo-user] " walt
2012-03-01  0:43               ` Pandu Poluan
2012-02-29  0:48   ` [gentoo-user] " Dale
2012-02-29  1:01     ` Alex Schuster
2012-02-29  2:38       ` Dale
2012-02-29  6:17         ` Neil Bothwick
2012-02-29  7:10           ` Dale
2012-02-29  7:49             ` J. Roeleveld
2012-02-29  9:23             ` Alan McKinnon
2012-03-01  1:09               ` Frank Steinmetzger
2012-03-01  8:26                 ` Alan McKinnon
2012-02-29  9:53             ` Neil Bothwick
2012-02-29  9:19         ` Alan McKinnon [this message]
2012-02-29 14:44           ` Dale
2012-02-29  7:43       ` J. Roeleveld
2012-02-29 13:06         ` Daddy
2012-02-29 14:44         ` Dale
2012-02-28 16:14 ` James Broadhead

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=20120229111956.21612f0d@khamul.example.com \
    --to=alan.mckinnon@gmail.com \
    --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