Ready for production ?
Hi,
One thread with exactly this subject was started 12 months ago. So it would be interested to make the point once again.
I am actually using nilfs2 on a volume where data integrity isn't important and didn't have any problems until now.
So what would the developers say ? Is it ready for production ?
Congratulations for this very good file system, I really like the idea behind it.
Bye,
David Arendt
A message that is not in the archive (sent off-list or not yet received): 48F65636.5050405-/[email protected]
Hi,
Quoted 9 lines · David Arendt
Hi,
One thread with exactly this subject was started 12 months ago. So it would be interested to make the point once again.
I am actually using nilfs2 on a volume where data integrity isn't important and didn't have any problems until now.
So what would the developers say ? Is it ready for production ?
It's up to you. ;)
We aim to apply nilfs to commercial products, and we use it daily for laptops, desktop machines and a shared storage server (samba server).
However, we think still it needs further testing, debugging efforts, performance improvement, enhancement of administrative tools, and so forth. At least for the stability, it was dramatically improved in the past year.
Quoted 2 lines
Congratulations for this very good file system, I really like the idea behind it.
I'm grad you liked it.
Cheers,
Ryusuke Konishi
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 15 lines · Ryusuke Konishi
Hi,
Quoted 9 lines · David Arendt
Hi,
One thread with exactly this subject was started 12 months ago. So it would be interested to make the point once again.
I am actually using nilfs2 on a volume where data integrity isn't important and didn't have any problems until now.
So what would the developers say ? Is it ready for production ?
It's up to you. ;)
Quoted 7 lines
We aim to apply nilfs to commercial products, and we use it daily for laptops, desktop machines and a shared storage server (samba server).
However, we think still it needs further testing, debugging efforts, performance improvement, enhancement of administrative tools, and so forth. At least for the stability, it was dramatically improved in the past year.
I don't think you should hold back from merging with mainline just because of stability problems. If you are mostly working except for some small, hard to find problems, then get it merged, tell everybody about the problems, and let people go hunt for them. That is what the open source process is about.
From what I can see, you are ready to go start the merging process now.
Regards,
Daniel
A message that is not in the archive (sent off-list or not yet received): 200810170415.30644.phillips-sjnr1BIWhQJeoWH0uzbU5w@public.gmane.org
Hi,
Quoted 7 lines · Daniel Phillips
I don't think you should hold back from merging with mainline just because of stability problems. If you are mostly working except for some small, hard to find problems, then get it merged, tell everybody about the problems, and let people go hunt for them. That is what the open source process is about.
From what I can see, you are ready to go start the merging process now.
Thanks for the comment.
I have already submitted kernel patches of the nilfs2 to LKML, and now the nilfs2 is in the Andrew's -mm patch set. Yes, I would like to proceed merging with mainline, and I'm really working on that in parallel. Your point is what I want to do.
The current focus is whether the nilfs2 is accepted by the kernel community or not. I'd like to accelerate activity for the merging, however I cannot work full-time for this. I would be thankful if someone could help me for it. ;)
With regards,
Ryusuke Konishi