[Ocfs2-users] ocfs2 is still eating memory

[Alexei_Roudnev]

Sunil, you DONT UNDERSTAND.

They DONT ASK for the SUPPORT. They ask, "HOW WE CAN REPORT A BUG?"

I had the same problem many times - there IS NOT a simple way to report a
bug to the Novell. Not a surprise that
systems are so buggy. For the beta versions, if you are not signed as a beta
tester, then there is not easy way to report bug, too.

(Signing as a beta tester means many obligations, and what if I am going to
test a few components only?)

For now, I am testing SP1 Beta4 (I have access as a partner so that we can
test new software before it is released). I never asked for suppirt, but I
saw a bugs many many times, and each time when I tried to report it
(possible or absolute bug), it was a headache. Let's take open-iscsi -
it require few small improvements for 100% sure, I can test them in our
case, many other users can test them too, but we CAN;T REPORT them.

(Just to have a list:
- lvm is not called after the iscsi, so it don't see open-iscsi. On the
other hand, having multiport support dropped in new iSCSI means that
you can't use human readable names from disk/by-path but must use multipath
disk ID's, so the only way to do it is lvm - but lvm is
not called after iSCSI;
- documentation have numerous bugs and don't explain how to mount iSCSI
disks (SuSe dropped netfs and did not add anything instead);
- few actions require timeouts; for example, you should wait 5 - 10 seconds
after discovery and before conenction.

)

They have the same problem. tested version, something don't work, call
support _We see a problem_ , and got response _you have not premium support
so we wil not talk_ (next time when I see your home burning, I call you and
you say _dont telemarket me, hang on_ instead of _what's the matter? OI,
it's serious. let's look together).

The sad story is that many of these bugs are easy to fix, and that system
itself is excellent... but quality is far from production grade, and the
futher the worst.


----- Original Message ----- 
From: "Sunil Mushran" <Sunil.Mushran at oracle.com>
To: "John Lange" <john.lange at open-it.ca>
Cc: "ocfs2-users" <ocfs2-users at oss.oracle.com>; "Lars Marowsky-Bree"
<lmb at suse.de>
Sent: Thursday, March 08, 2007 4:37 PM
Subject: Re: [Ocfs2-users] ocfs2 is still eating memory


> If you are running a prod shop, you should looking into buying support.
>
> John Lange wrote:
> > On Mon, 2007-03-05 at 13:46 -0800, Sunil Mushran wrote:
> >
> >> Well, kswapd is supposed to flush the caches. As in, the vm
> >> controls the lifetime of the inodes in the inode_cache not ocfs2.
> >>
> >> All ocfs2 can do is free the memory associated with the inode when
> >> asked to. And it does that when you manually flush the cache. Qs is
> >> why the vm is not doing it on its own. (fwiw, you are on a beta
kernel.)
> >>
> >
> > We are using beta kernels in an attempt to solve this problem. As
> > everyone knows, the most recent official SUSE kernel (2.6.16.21-0.25 i
> > believe?) completely broke ocfs2. Downgrading to 2.6.16.21-0.15 solves
> > that problem but the memory issue remains.
> >
> > So as far as I am aware, there is no SUSE kernel that works with ocfs2
> > which is where we find ourselves today.
> >
> > I just upgraded to the latest KOTD:
> >
> > 2.6.16.42-SLES10_SP1_BRANCH_20070307114604-smp
> >
> > And still, when running ocfs2, all ram gets consumed.
> >
> > Right now Novell is playing the "you don't have premium support" game so
> > where should I report this bug?
> >
> > Regards,
> >
> > John Lange
> >
> >
> >
>
> _______________________________________________
> Ocfs2-users mailing list
> Ocfs2-users at oss.oracle.com
> http://oss.oracle.com/mailman/listinfo/ocfs2-users
>