| 1 |
Ok, thanks everybody, getting ready to dive in and fix this thing. Two |
| 2 |
more questions please: |
| 3 |
|
| 4 |
I modified the bottom of /etc/fstab to look like this according to a |
| 5 |
post in the eee forum: |
| 6 |
... |
| 7 |
#shm /dev/shm tmpfs nodev,sosuid,noexec 0 0 |
| 8 |
tmpfs /tmp tmpfs defaults,noatime,mode=1777 0 0 |
| 9 |
|
| 10 |
Does this have anything to do with the inode issue? |
| 11 |
|
| 12 |
What's the best fs for a 4G SSD? I picked ext3 because of another eee |
| 13 |
forum post. |
| 14 |
|
| 15 |
Maxim |
| 16 |
|
| 17 |
On 5/28/09, Volker Armin Hemmann <volkerarmin@××××××××××.com> wrote: |
| 18 |
> On Donnerstag 28 Mai 2009, Florian Philipp wrote: |
| 19 |
>> Maxim Wexler schrieb: |
| 20 |
>> > Hi group, |
| 21 |
>> > |
| 22 |
>> > For a netbook 4G SSD. Attempting to install mozilla-firefox. jdk |
| 23 |
>> > fails: No space left on device. |
| 24 |
>> > |
| 25 |
>> > df -i reveals no more inodes. I reboot thinking this will help. Wrong. |
| 26 |
>> > Lots of 'No space left on device messages' with reference to |
| 27 |
>> > /var/lib/iinit.d/* in the boot console. And this gem: '*ERROR: local |
| 28 |
>> > is already starting'. And: '*ERROR: netmount is already starting'. |
| 29 |
>> > |
| 30 |
>> > df -i |
| 31 |
>> > |
| 32 |
>> > Filesytem Inodes Iused IFree IUse% Mounted on |
| 33 |
>> > /dev/sda2 244320 244301 19 100% / |
| 34 |
>> > udev 128448 612 127836 1% /dev |
| 35 |
>> > /dev/sda1 8032 39 7993 1% /boot |
| 36 |
>> > tmpfs 128448 3 1 28445 1% /tmp |
| 37 |
>> > |
| 38 |
>> > FYI sda2 is formatted ext3. |
| 39 |
>> > |
| 40 |
>> > I know 4G is pretty small by today's standards but apart from xorg and |
| 41 |
>> > firefox everything else on this unit is command-line type utilities |
| 42 |
>> > and such. That can't account for 4G already. |
| 43 |
>> > |
| 44 |
>> > Maxim |
| 45 |
>> |
| 46 |
>> That you run out of inodes doesn't mean that you run out of physical (or |
| 47 |
>> logical) space on your disk. It just means that you run out of what you |
| 48 |
>> could call file descriptors. |
| 49 |
>> |
| 50 |
>> There is exactly one inode per file which stores meta information about |
| 51 |
>> this file. Ext2-4 have a fixed amount of inodes set when you format the |
| 52 |
>> partition. Reiserfs and JFS create them on the fly and therefore don't |
| 53 |
>> have problems with running out of inodes or wasting space on unused ones. |
| 54 |
>> |
| 55 |
>> Most likely you have a bunch of very small files on our disk, for |
| 56 |
>> example the portage tree. These don't consume much space but a lot of |
| 57 |
>> inodes. |
| 58 |
>> |
| 59 |
>> My advice: Save everything to another disk and then reformat the |
| 60 |
>> partition with a higher amount of inodes. If you use ext2, format it with |
| 61 |
>> |
| 62 |
>> mke2fs -N 732960 /dev/sda2 |
| 63 |
>> |
| 64 |
>> This will create a file system with three times as many indoes as you |
| 65 |
>> had before. |
| 66 |
>> |
| 67 |
>> Hope this helps. |
| 68 |
> |
| 69 |
> or don't use extX. |
| 70 |
> |
| 71 |
> |
Archives