| 1 |
On 21 August 2011 03:46, Andrea Conti <alyf@××××.net> wrote: |
| 2 |
>> If you run man mke2fs, you should check out -N and -i. It was |
| 3 |
>> trial-and-error (for me, anyway) to find the right number. |
| 4 |
> |
| 5 |
> Consider using reiserfs for /usr/portage. No real performance advantage |
| 6 |
> over ext[234], but works well with lots of small files and there's no |
| 7 |
> inode count to worry about. |
| 8 |
> |
| 9 |
> In my experience the main downside of reiserfs is that fsck.reiserfs is |
| 10 |
> almost never able to recover cleanly if the filesystem metadata does get |
| 11 |
> corrupted in a non-trivial way. But for the portage snapshot this isn't |
| 12 |
> really a problem... |
| 13 |
|
| 14 |
I have always used ReiserFS for everything but /boot. That explains |
| 15 |
why I never ran into the inode issue, I guess. |
| 16 |
|
| 17 |
I'm trying to install AMD64 and the handbook says that ([1]) "JFS and |
| 18 |
ReiserFS may work but need more testing. If you're really adventurous |
| 19 |
you can try the other filesystems.". That didn't sound too promising |
| 20 |
so I went with ext3. :-) |
| 21 |
|
| 22 |
The X86 handbook doesn't have this text. Is ReiserFS on AMD64 really |
| 23 |
only for the adventurous? Or should this warning be removed? |
| 24 |
|
| 25 |
[1] http://www.gentoo.org/doc/en/handbook/handbook-amd64.xml?part=1&chap=4#filesystemsdesc |
Archives