1 |
On Sat, Mar 10, 2012 at 07:36:07PM +0100, YoYo Siska wrote: |
2 |
> On Sat, Mar 10, 2012 at 03:35:05PM +0000, Neil Bothwick wrote: |
3 |
> > On Sat, 10 Mar 2012 14:30:15 +0100, Alex Schuster wrote: |
4 |
> > |
5 |
> > > Any tips on this? Does it make sense to use a special file system just |
6 |
> > > for the portage tree? What would be best? Would it help to re-create |
7 |
> > > this file system from time to time in case it gets slower with every |
8 |
> > > sync? |
9 |
> > |
10 |
> > I use an ext2 filesystem for portage, it's still the fastest out there. |
11 |
> > Journals are unnecessary because its such a small filesystem, and if it |
12 |
> > does get damaged I can just reformat and sync again. |
13 |
> |
14 |
> I use an ext2 partition in a 500MB file image on most of my computers. |
15 |
> Its important to check the inode count on such small filesytem, as |
16 |
> mke2fs' default inode ration for such size is 4096, which is too |
17 |
> low for portage: |
18 |
> |
19 |
> dd bs=$((500*1024*1024)) count=1 if=/dev/zero of=/usr/img_portage |
20 |
> mke2fs -f -b1024 -i2048 /usr/img_portage |
21 |
|
22 |
The -f option from mke2fs is to specify a fragment size and expects an |
23 |
argument. Do you -F (which forces mke2fs to create a filesystem, even if |
24 |
the specified device is not a partittion on a block special device)? |
25 |
|
26 |
> fstab: |
27 |
> /usr/img_portage /usr/portage/ ext2 loop,noatime 0 0 |
28 |
> (this is from desktop, on servers I usually only mount it manually when |
29 |
> emerging) |
30 |
> |
31 |
> # df -h |
32 |
> Filesystem Size Used Avail Use% Mounted on |
33 |
> /dev/loop0 469M 306M 139M 69% /usr/portage |
34 |
> |
35 |
> # df -i |
36 |
> Filesystem Inodes IUsed IFree IUse% Mounted on |
37 |
> /dev/loop0 256032 152044 103988 60% /usr/portage |
38 |
|
39 |
Romildo |