could you give an estimate when fhgfs for kernel version 3.2 will be available?
ciao
Christian
On 01/16/2012 01:50 PM, Christian Salzmann wrote:
> Dear developers,
>
> could you give an estimate when fhgfs for kernel version 3.2 will be
> available?
our development branch already has support for linux-3.2 and within the
next weeks there will be a new major release of fhgfs, based on this
branch. Yesterday we detected an infiniband RDMA problem with linux-3.2
and we are just debugging this issue now. Once this is done we could
back port support for linux-3.1 and linux-3.2 to our stable 2011.04
branch and make another release for that.
So our question to you and other supported customers is: How import is
linux-3.1 and linux-3.2 support for you? Or in other words, do you need
it urgently or can you still wait a few weeks?
Thanks,
Bernd
Dear Bernd,
we are currently building a new cluster and evaluate fhgfs on Debian testing (aka "wheezy"). As "wheezy" will be released with linux-3.2 (http://lists.debian.org/debian-devel-announce/2012/01/msg00012.html) we would like to test the targeted linux version as soon as possible.
So no, there is no special urgence; "a few weeks" is soon enough for us ;-).
Thank you very much for consideration.
ciao
Christian
Christian Salzmann wrote on 01/31/2012 05:48 PM:
>>> could you give an estimate when fhgfs for kernel version 3.2 will be
>>> available?
the new fhgfs version 2011.04-r15, which is available now, adds support
for Linux 3.2.
If you're using Infiniband, please be aware that early 3.2 kernels
contain a critical bug in the Infiniband drivers, which will crash the
machine. We reported the problem and it has been fixed in recent 3.2
kernels:
http://www.mail-archive.com/sta...@vger.kernel.org/msg00867.html
Best regards,
Sven
> the new fhgfs version 2011.04-r15, which is available now, adds support for Linux 3.2.
That's great news!
>
> If you're using Infiniband, please be aware that early 3.2 kernels contain a critical bug in the Infiniband drivers, which will crash the machine. We reported the problem and it has been fixed in recent 3.2 kernels:
> http://www.mail-archive.com/sta...@vger.kernel.org/msg00867.html
Thanks for the hint!
Luckily, your bugfix was released with stable kernel 3.2.6 (http://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.2.6) which entered Debian wheezy about one week ago.
ciao
Christian