1 |
Maxim Wexler schrieb: |
2 |
> On 5/28/09, Volker Armin Hemmann <volkerarmin@××××××××××.com> wrote: |
3 |
>> On Donnerstag 28 Mai 2009, Florian Philipp wrote: |
4 |
>>> Maxim Wexler schrieb: |
5 |
>>>> Hi group, |
6 |
>>>> |
7 |
>>>> For a netbook 4G SSD. Attempting to install mozilla-firefox. jdk |
8 |
>>>> fails: No space left on device. |
9 |
>>>> |
10 |
>>>> df -i reveals no more inodes. I reboot thinking this will help. Wrong. |
11 |
>>>> Lots of 'No space left on device messages' with reference to |
12 |
>>>> /var/lib/iinit.d/* in the boot console. And this gem: '*ERROR: local |
13 |
>>>> is already starting'. And: '*ERROR: netmount is already starting'. |
14 |
>>>> |
15 |
[...] |
16 |
>>>> |
17 |
>>>> I know 4G is pretty small by today's standards but apart from xorg and |
18 |
>>>> firefox everything else on this unit is command-line type utilities |
19 |
>>>> and such. That can't account for 4G already. |
20 |
>>>> |
21 |
>>>> Maxim |
22 |
>>> That you run out of inodes doesn't mean that you run out of physical (or |
23 |
>>> logical) space on your disk. It just means that you run out of what you |
24 |
>>> could call file descriptors. |
25 |
>>> |
26 |
>>> There is exactly one inode per file which stores meta information about |
27 |
>>> this file. Ext2-4 have a fixed amount of inodes set when you format the |
28 |
>>> partition. Reiserfs and JFS create them on the fly and therefore don't |
29 |
>>> have problems with running out of inodes or wasting space on unused ones. |
30 |
>>> |
31 |
>>> Most likely you have a bunch of very small files on our disk, for |
32 |
>>> example the portage tree. These don't consume much space but a lot of |
33 |
>>> inodes. |
34 |
>>> |
35 |
>>> My advice: Save everything to another disk and then reformat the |
36 |
>>> partition with a higher amount of inodes. If you use ext2, format it with |
37 |
>>> |
38 |
>>> mke2fs -N 732960 /dev/sda2 |
39 |
>>> |
40 |
>>> This will create a file system with three times as many indoes as you |
41 |
>>> had before. |
42 |
>>> |
43 |
>>> Hope this helps. |
44 |
>> or don't use extX. |
45 |
>> |
46 |
>> |
47 |
> Ok, thanks everybody, getting ready to dive in and fix this thing. Two |
48 |
> more questions please: |
49 |
> |
50 |
[...] |
51 |
> |
52 |
> What's the best fs for a 4G SSD? I picked ext3 because of another eee |
53 |
> forum post. |
54 |
> |
55 |
> Maxim |
56 |
> |
57 |
|
58 |
I just want to point to three blog posts from Theodore Ts'o: |
59 |
|
60 |
Partioning scheme and formatting tricks for optimal performance: |
61 |
http://thunk.org/tytso/blog/2009/02/20/aligning-filesystems-to-an-ssds-erase-block-size/ |
62 |
|
63 |
Talk about some general issues (ATA TRIM, mostly): |
64 |
http://thunk.org/tytso/blog/2009/02/22/should-filesystems-be-optimized-for-ssds/ |
65 |
|
66 |
Making an argument for using journalling filesystems: |
67 |
http://thunk.org/tytso/blog/2009/03/01/ssds-journaling-and-noatimerelatime/ |
68 |
|
69 |
Of course, T'so talks about an Intel X25-M which is a completely |
70 |
different beast from those cheap SSDs you find in netbooks. |
71 |
|
72 |
Delaying commits with ext4 and/or laptop-mode will reduce the wear-down |
73 |
of your SSD but it might as well freeze your system when the actual |
74 |
commit takes place because these things tend to have a terribly low |
75 |
write performance. |
76 |
|
77 |
In the end it will be a matter of playing with parameters. |