Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
hard task, not enough files ?
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Gentoo on Alternative Architectures
View previous topic :: View next topic  
Author Message
der_maddin
Apprentice
Apprentice


Joined: 22 Feb 2004
Posts: 209
Location: somewhere between my systems ..

PostPosted: Tue Jul 19, 2005 5:07 pm    Post subject: hard task, not enough files ? Reply with quote

i'm trying to install gentoo on a hppa system.

after i finally managed to get emerge working
(thanks to the changed profiles it took quite a while)
now i experience problems unpacking things
while emerging.

after some time emerge is running
(actually, i'm still trying to emerge hppa-sources)
tar starts shouting there was no file or directory
where it wants to extract to.

the message is like:
tar: [some dir/file or mkdir command] Cannot open: file or directory does'nt exist.

and in fact, observing things in /var/portage,
there is no directory named as the one tar wants to
dive into...

weird ?


a possible reason maybe a limited number of files,
fsck.ext3 tells me i do have ~ 209000 / 215936 files ...

if this is the reason for this weird behavior, how can i change it ??

i'm confused ...

[edit:]

Yes, after checking it twice, it seems like i'm running out of inodes ...
hmm, how should i get it running, if i can't even emerge the
sources ??

any suggestions what filesystem i should use ?

it's an old 2 GB scsi harddrive, 1.7G for /
_________________
neoCortex maddin # uname -a
Linux neoCortex 2.6.14-gentoo-r5 #2 SMP Fri Jan 13 04:40:02 CET 2006 x86_64 AMD Athlon(tm) 64 Processor 3400+ AuthenticAMD GNU/Linux
Back to top
View user's profile Send private message
jmbsvicetto
Moderator
Moderator


Joined: 27 Apr 2005
Posts: 4730
Location: Angra do Heroísmo (PT)

PostPosted: Tue Jul 19, 2005 6:13 pm    Post subject: Reply with quote

Hi.

Have you looked at the mkfs.ext3 man page?
Code:
NAME
       mke2fs - create an ext2/ext3 filesystem

SYNOPSIS
       mke2fs  [  -c | -l filename ] [ -b block-size ] [ -f fragment-size ] [ -g blocks-per-group ] [ -i bytes-per-inode ] [
       -j ] [ -J journal-options ] [ -N number-of-inodes ] [ -n ] [ -m reserved-blocks-percentage ] [ -o creator-os ]  [  -O
       feature[,...]   ]  [  -q  ] [ -r fs-revision-level ] [ -R raid-options ] [ -v ] [ -F ] [ -L volume-label ] [ -M last-
       mounted-directory ] [ -S ] [ -T filesystem-type ] [ -V ] device [ blocks-count ]

       mke2fs -O journal_dev [ -b block-size ] [ -L volume-label ] [ -n ] [ -q ] [ -v ] external-journal [ blocks-count ]

       -b block-size
              Specify  the  size  of  blocks  in bytes.  Valid block size vales are 1024, 2048 and 4096 bytes per block.  If
              omitted, mke2fs block-size is hueristically determined by the file system size and the expected usage  of  the
              filesystem  (see  the -T option).  If block-size is negative, then mke2fs will use hueristics to determine the
              appropriate block size, with the constraint that the block size will be at least block-size  bytes.   This  is
              useful for certain hardware devices which require that the blocksize be a multiple of 2k.

       -i bytes-per-inode
              Specify  the bytes/inode ratio.  mke2fs creates an inode for every bytes-per-inode bytes of space on the disk.
              The larger the bytes-per-inode ratio, the fewer inodes will be created.  This  value  generally  shouldn't  be
              smaller  than the blocksize of the filesystem, since then too many inodes will be made.  Be warned that is not
              possible to expand the number of inodes on a filesystem after it is created, so be careful deciding  the  cor‐
              rect value for this parameter.

       -N number-of-inodes
              overrides the default calculation of the number of inodes that should be reserved for the filesystem (which is
              based on the number of blocks and the bytes-per-inode ratio).  This allows the user to specify the  number  of
              desired inodes directly.

       -T fs-type
              Specify how the filesystem is going to be used, so that mke2fs can chose  optimal  filesystem  parameters  for
              that use.  The supported filesystem types are:

                   news        one inode per 4kb block
                   largefile   one inode per megabyte
                   largefile4  one inode per 4 megabytes

I think you will have to recreate your ext3 partition and imposing a minimum number of inodes to be created or perhaps use the -T news option. However, if you're getting out of inodes, how full is your disk? Do you think you'll be able to install into that disk?
Have you also considered using other filesystem? I think that reiserfs might be able to define the number of inodes dinamically and doubt if jfs or xfs will have such limits. On the other hand, I don't know if thinking about another filesystem is secondary to thinking about a new disk.
Hope this helps.
_________________
Jorge.

Your twisted, but hopefully friendly daemon.
AMD64 / x86 / Sparc Gentoo
Help answer || emwrap.sh
Back to top
View user's profile Send private message
der_maddin
Apprentice
Apprentice


Joined: 22 Feb 2004
Posts: 209
Location: somewhere between my systems ..

PostPosted: Wed Jul 20, 2005 9:27 am    Post subject: Reply with quote

thanks for the reply.

no, i won't be able to use another disk.
as you may have noticed, the system is
a hp 712/60, hppa architecture.

so the only disk i've got here that would
run in that system is the 2G disk i'm using.

but i did solve the inodes problem for now
by cleaning up /var/tmp/portage
(had some files in there no longer needed)
so i could emerge the kernel-sources and still
have some ( ~ 50.000 ) inodes free.

my aim would be to
- compile a kernel
- install grub, system logger, cron, whatever
- emerge samba

if i could succeed in emerging samba i plan to
move some of the disks contents
(esp. the /usr/portage tree )
to a samba share.


still i'm interested in getting to know if
it would be possible to

- change inodes of exisiting filesystem without loosing the data
- convert filesystem to maybe reiserFS without loosing the data
_________________
neoCortex maddin # uname -a
Linux neoCortex 2.6.14-gentoo-r5 #2 SMP Fri Jan 13 04:40:02 CET 2006 x86_64 AMD Athlon(tm) 64 Processor 3400+ AuthenticAMD GNU/Linux
Back to top
View user's profile Send private message
pilla
Administrator
Administrator


Joined: 07 Aug 2002
Posts: 7214
Location: Pelotas, BR

PostPosted: Wed Jul 20, 2005 2:04 pm    Post subject: Reply with quote

Moved from IG.
_________________
"I'm just very selective about the reality I choose to accept." -- Calvin
Back to top
View user's profile Send private message
HPRichard
Tux's lil' helper
Tux's lil' helper


Joined: 02 Feb 2005
Posts: 94
Location: KA, Germany

PostPosted: Wed Jul 20, 2005 9:56 pm    Post subject: Reply with quote

Out of my experience with Microsoft filesystems in Linux I do not believe in moving /usr/portage to a smb share being a good idea, I very often had problems with the access rights and file ownerships, no idea if this went better with recent samba versions.
I believe that using NFS is the much better option. A friend of mine is on the way of installing a diskless Gecko (712/60) using only NFS, at the moment he is working through the TFTP things. But as you have a disk, you can use palo, which should be much easier. If you want to use /usr/portage via NFS, you can even share the same directory across multiple machines, even when they have different architectures, there are some threads explaining this. This yields in you having to
Code:
emerge --sync
only once for all machines, and you only have to
Code:
emerge metadata
on all the other machines.
But again, there are other threads explaining this much better.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Gentoo on Alternative Architectures All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum