public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Hilco Wijbenga <hilco.wijbenga@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] [Gentoo install] Disk full at 35%?
Date: Sat, 20 Aug 2011 20:30:00 -0700	[thread overview]
Message-ID: <CAE1pOi2pWhv4BCvPL08rO8cWdbn487q9s5QGfcS2p_CP=d_9GQ@mail.gmail.com> (raw)
In-Reply-To: <6772.1313891543@ccs.covici.com>

On 20 August 2011 18:52,  <covici@ccs.covici.com> wrote:
> Hilco Wijbenga <hilco.wijbenga@gmail.com> wrote:
>
>> Hi all,
>>
>> It's been quite a few years but I decided to try another Gentoo
>> install (on a VirtualBox instance). I wanted to try out some new
>> things...
>>
>> I created a ton of partitions including /usr (I want to see if I can
>> get that to work), /portage, and /distfiles. The idea was to mount
>> /portage on top of /usr and /distfiles on top of /portage. This all
>> works fine.
>>
>> However, when I try to extract the Portage snapshot, I get "No space
>> left on device" a long way into the untar process. According to df
>> /portage (i.e. /mnt/gentoo/usr/portage) is only 35% full. In fact, not
>> a single partition or mount is even close to full (except for
>> /mnt/static, the DVD).
>>
>> If I untar directly to /usr (after unmounting /portage), everything
>> works fine. If I then try to copy or move to /portage, I get the "No
>> space left on device" again. And at the same place.
>>
>> Does anyone know what's going on here? I didn't realize I was doing
>> such strange things. At least not this early on. :-)
>
> See if  you are out of inodes. The only way to get the inodes that I am
> aware of is to  debugfs to the partition and do stat from within -- if
> there is a better way please let me know.  But why not use lvm?

Yes, df -i says /portage is out of inodes. I've never run into that
before. I reran mke2fs to increase the inode count and that fixed
things.

Would LVM somehow prevent these sort of things from happening? LVM
doesn't affect inode usage, does it? What exactly are the advantages
of LVM? Is it just that it's easier to resize LVM partitions after the
fact? (That would, of course, already be very useful.)



  reply	other threads:[~2011-08-21  3:31 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-21  1:41 [gentoo-user] [Gentoo install] Disk full at 35%? Hilco Wijbenga
2011-08-21  1:52 ` covici
2011-08-21  3:30   ` Hilco Wijbenga [this message]
2011-08-21  4:21     ` Nilesh Govindarajan
2011-08-21  4:47       ` Hilco Wijbenga
2011-08-21 10:13         ` Mick
2011-08-21 10:30           ` Adam Carter
2011-08-21 10:49           ` Alan McKinnon
2011-08-21 10:46         ` Andrea Conti
2011-08-21 18:14           ` Hilco Wijbenga
2011-08-21 21:24             ` Peter Humphrey
2011-08-21 12:03     ` Alex Schuster
2011-08-21 13:45       ` Andrea Conti
2011-08-21 17:09         ` Alex Schuster
2011-08-21 19:23           ` Andrea Conti
2011-08-21 21:46             ` Alan McKinnon
2011-08-21  3:05 ` Paul Hartman
2011-08-21  3:30   ` Hilco Wijbenga

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='CAE1pOi2pWhv4BCvPL08rO8cWdbn487q9s5QGfcS2p_CP=d_9GQ@mail.gmail.com' \
    --to=hilco.wijbenga@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