On Fri, 22 Sep 2006 13:08:34 +0000 (UTC) "Peter" <[EMAIL PROTECTED]> wrote:
> On Fri, 22 Sep 2006 14:49:30 +0200, Thomas Kuther wrote: > > snip... > > > > > Yes, that was me :) > > As i seemed to be the only person hitting that bug, i didn't > > mention it here on the list nor on LKML. I just warned the users in > > the -beyond and -no sources threads some releases > > ago ... .17-beyond1 thread IIRC... and stopped using fcache patched > > kernels, because i like my /usr/portage flying on a reiser4 > > partition ;) > > > > Regards > > Tom > > I passed this along to the beyond maintainer fwiw. Still a very > disturbing problem. And, it appears, you're not alone. Well, not too > alone anyway! > > -- > Peter Looking at the patchlist, Con dropped fcache in 2.6.18-ck1, so if Iphitus doesn't explicitly add it, future -beyond kernels should be fine. But lets clean out this issue somehow. Vladimir, you asked if Peter runs Gentoo, so seems there is something gentoo vs. reiser4-specific known, which somewhat explains why it always only busted my /usr partition. So, if I got that right, reiser4 needs to be fixed for fcache in -mm so it can deal with portage. No idea if, why and how this is related, portage on reiser4 with a kernel w/o fcache works like a charme, so it did the last 2 years here. And fcache has to be fixed, because if I disable something in the kernel config, it shouldn't be able to cause such trouble! This fact is even more annoying than the fact that fcache, portage and reiser4 don't play well toghether IMHO. But that's OT on this list. Regards, Tom
signature.asc
Description: PGP signature