> > The problem was solved by using my own kernel, 2.6.18. > > Well, that means you've cathed this (git commit): > b2ea401bac39e75ebb64038609ed22efbc799905 > > > Maybe it's worth to ask to be in next 2.6.17-stable ? Yes, it will make sense to me. Problem is, that I cannot make any test, becouse it is pretty hard to make a image of 1.1T filesystem ;-) cheers dan