1 |
This One Time, at Band Camp, Florian Philipp <lists@f_philipp.fastmail.net> said, On Sat, Feb 16, 2008 at 01:50:04AM +0100: |
2 |
|
3 |
> On Sat, 2008-02-16 at 00:32 +0100, Wael Nasreddine wrote: |
4 |
|
5 |
|
6 |
> > > To your filesystem scheme: Why do you use xfs for usr? AFAIK XFS is good |
7 |
> > > at write speed but not worth the trouble when reading data and data in |
8 |
> > > usr is usually written once, updated every few months and read many |
9 |
> > > times a week (on rebooting Desktop PCs maybe once a day). I'd use |
10 |
> > > reiserfs3.6, maybe even without notail to make it more space efficient. |
11 |
> > I don't use XFS, curently I only have / and /home and I want to split |
12 |
> > it to more smaller partitions, I'm on LVM so it's easy, anyway I'm |
13 |
> > going with ReiserFS for /usr /var, would you please suggest |
14 |
> > mkfs.reiserfs options as I have nerver used ReiserFS-3 before (yep 5 |
15 |
> > years using linux and I've always used ext3...) also You didn't mention |
16 |
> > /var, would you say ReiserFS-3 is a good choice as well? |
17 |
|
18 |
> I don't think there's alot to do when creating a reiserfs. You could |
19 |
> change the number of blocks for the journal. A bigger journal allows |
20 |
> larger transactions which speed up write actions but might waste space. |
21 |
> If you've got a second hard drive you could use an external journal but |
22 |
> I've never done any benchmarking on that issue although I use it on my |
23 |
> personal wannabe server (a raid1 and a single disk for the journal and |
24 |
> unimportant data). |
25 |
|
26 |
> I didn't comment on /var because I don't know how you use it. I suspect |
27 |
> it to hold alot of temporal data like lock files, spools and so on. So |
28 |
> there's a lot of creating and removing files going on, possibly in |
29 |
> parallel. XFS is good in parallel and in creating files but terrible in |
30 |
> removing files. Reiserfs with notail seems a good choice if you ask me |
31 |
> (what you did ;) ) |
32 |
|
33 |
|
34 |
> > > I'd also use ext2 on /usr/portage. These data don't need journaling. |
35 |
> > > Everything's got an MD5-sum to make sure it's unchanged after a crash |
36 |
> > > and you can easily resync. I found ext2 with 2k blocks to be faster than |
37 |
> > > reiserfs3.6, even on read-performance. |
38 |
> > I've already made the partition as suggested in [1] I used this |
39 |
> > command: |
40 |
> > $ mke2fs -b 1024 -N 200000 -m 0 -O dir_index |
41 |
|
42 |
> > I guess 1K block size would be faster?? |
43 |
|
44 |
> I'm not sure. 2K blocks might reduce fragmentation. |
45 |
|
46 |
> If you look at the output of |
47 |
> find /usr/portage/ -type f | xargs du -h --apparent-size |
48 |
> you'll see that there are quiet a few files larger than 1K but most are |
49 |
> smaller and might stay that small. So yes, I think 1K is a good choice |
50 |
> but you won't loose much with 2K, maybe you even gain some speed. |
51 |
|
52 |
|
53 |
|
54 |
> > > If I were you, I'd also use separate volumes for /tmp and /var/tmp |
55 |
> > > (without ccache) with xfs. |
56 |
> > What did you mean by 'without ccache'? I have ccache and I use it... |
57 |
|
58 |
> I meant that you should keep ccache on a separate partition. I just |
59 |
> think: Less stuff in the FS, less work on allocation and lookup, more |
60 |
> speed. And there's a lot of stuff in 2GB ccache. |
61 |
|
62 |
> By the way: I don't think /var/tmp is a good place for ccache (not |
63 |
> technically, just for the sake of layout). I've moved it to /var/db |
64 |
> since it's not really a bunch of temporary data but more like a changing |
65 |
> database. |
66 |
|
67 |
|
68 |
> > > /home could use data=journal. Those data are precious and if I remember |
69 |
> > > correctly, this setting even brings an obscure (i.e. undocumented) speed |
70 |
> > > improvement with many parallel disk accesses, for example in a |
71 |
> > > multi-user environment. |
72 |
> > it's done, thanks, BTW what's your home partition FS? your choice is |
73 |
> > ext3 or reiserFS?? |
74 |
|
75 |
|
76 |
> I use reiserfs3.6 without notail but that doesn't mean that it would be |
77 |
> a good choice for you. I'm on laptop and disk space efficiency is a big |
78 |
> topic for me so I use tail-packing wherever suitable. And yes, I am a |
79 |
> fan of ReiserFS-3.6. I think it's the best multipurpose FS. You can |
80 |
> easily adapt it for high performance or high disk space efficiency. If |
81 |
> its journaling would be as good as Ext3's data=journal I'd use it |
82 |
> everywhere except for small partitions (ext2) and big files (ext3 and |
83 |
> xfs). |
84 |
|
85 |
> > One last thing, since I'm on LVM resizing the partition is a must |
86 |
> > feature, in ext3 I use resize2fs which works quite nicely, is |
87 |
> > resize_reiserfs as reliable as resize2fs is?? |
88 |
|
89 |
|
90 |
> Yes, it's just as good and the sky's the limit for resizing :) |
91 |
> Oh, by the way: If you choose to use XFS somewhere, keep in mind that |
92 |
> you can't shrink and XFS-FS. Neither online nor offline. |
93 |
|
94 |
> One last thing: It's a bit old but I think it's still interesting, |
95 |
> especially for XFS-users: |
96 |
|
97 |
> http://everything2.com/index.pl?node_id=1479435 |
98 |
|
99 |
Thank you for your detailed answer it helped a lot, I just finished |
100 |
resizing/migrating all partitions, Though I still have the Storage |
101 |
partition, which is for my Mp3z and is almost 70Gb, with ext3, I'll |
102 |
see later if I do migrate to ReiserFS or not but the rest is done, |
103 |
please take a look at the file attached... and if you have any more |
104 |
suggestions please do tell me. |
105 |
|
106 |
Thanks a lot guys.... |
107 |
|
108 |
-- |
109 |
Wael Nasreddine |
110 |
http://wael.nasreddine.com |
111 |
PGP: 1024D/C8DD18A2 06F6 1622 4BC8 4CEB D724 DE12 5565 3945 C8DD 18A2 |
112 |
|
113 |
.: An infinite number of monkeys typing into GNU emacs, |
114 |
would never make a good program. (L. Torvalds 1995) :. |