Stephen C. Tweedie wrote:
Hi,
On Fri, 2005-01-28 at 20:15, Jeffrey E. Hundstad wrote:
Does linux-2.6.11-rc2 have both the linux-2.6.10-ac10 fix and the xattr
problem fixed?
Not sure about how much of -ac went in, but it has the xattr fix.
I've had my machine that would cra
Hi,
On Fri, 2005-01-28 at 20:15, Jeffrey E. Hundstad wrote:
> >>Does linux-2.6.11-rc2 have both the linux-2.6.10-ac10 fix and the xattr
> >>problem fixed?
> >Not sure about how much of -ac went in, but it has the xattr fix.
> I've had my machine that would crash daily if not hourly stay up for
Stephen C. Tweedie wrote:
Hi,
On Tue, 2005-01-25 at 15:09, Jeffrey Hundstad wrote:
Bad things happening to journaled filesystem machines
Oops in kjournald
I wonder if there are several problems. Alan Cox claimed that there was
a fix in linux-2.6.10-ac10 that might alleviate the pro
Hi,
On Tue, 2005-01-25 at 15:09, Jeffrey Hundstad wrote:
> >> Bad things happening to journaled filesystem machines
> >> Oops in kjournald
> I wonder if there are several problems. Alan Cox claimed that there was
> a fix in linux-2.6.10-ac10 that might alleviate the problem.
I'm not sure --
Stephen C. Tweedie wrote:
Hi,
On Mon, 2005-01-17 at 21:31, Jeffrey Hundstad wrote:
For more of this look up subjects:
Bad things happening to journaled filesystem machines
Oops in kjournald
That seems to have been due to the xattr problems recently fixed in
Linus's tree. The xattr race w
Hi,
On Mon, 2005-01-17 at 21:31, Jeffrey Hundstad wrote:
> For more of this look up subjects:
> Bad things happening to journaled filesystem machines
> Oops in kjournald
That seems to have been due to the xattr problems recently fixed in
Linus's tree. The xattr race was allowing one process
Jeffrey Hundstad wrote:
For more of this look up subjects:
Bad things happening to journaled filesystem machines
Oops in kjournald
and from author:
Anders Saaby
I also can't keep a recent 2.6 or 2.6*-ac* kernel up more than a few
hours on a machine under real load. Perhaps us folks with the
Christoph Hellwig wrote:
: I have a better patch than the one I gave you (attached below). If you
: send me a mail with steps to reproduce your remaining problems I'll put
: this very high on my TODO list after christmas. Btw, any chance you could
: try XFS CVS (which is at 2.6.9) + the patch bel
On Llu, 2005-01-17 at 21:31, Jeffrey Hundstad wrote:
> I also can't keep a recent 2.6 or 2.6*-ac* kernel up more than a few
> hours on a machine under real load. Perhaps us folks with the problem
> need to talk to the powers who be to come up with a strategy to make a
> report they can use. M
For more of this look up subjects:
Bad things happening to journaled filesystem machines
Oops in kjournald
and from author:
Anders Saaby
I also can't keep a recent 2.6 or 2.6*-ac* kernel up more than a few
hours on a machine under real load. Perhaps us folks with the problem
need to talk to
Hi,
On Monday 17 January 2005 12:55, Jan-Frode Myklebust wrote:
>
> Guess we've been struggeling with much of the same problems..
Seems like it. :)
> > ---
> > Scenario 2: Mailservers:
> > Running XFS on mailqueue:
>
> The 2.6.10-1.737_FC3 + 's/posix_lock_file/posix_lock_file_wait/' on
> f
On Mon, Jan 17, 2005 at 11:07:46AM +0100, Jakob Oestergaard wrote:
>
> Where should I begin? ;)
Guess we've been struggeling with much of the same problems..
> ---
> Scenario 2: Mailservers:
> Running XFS on mailqueue:
The 2.6.10-1.737_FC3 + 's/posix_lock_file/posix_lock_file_wait/' on
f
On Sun, Jan 16, 2005 at 01:51:12PM +, Christoph Hellwig wrote:
> On Fri, Jan 14, 2005 at 07:23:09PM +0100, Jakob Oestergaard wrote:
> > So apart from the general well known instability problems that will
> > occur when you actually start *using* the system, there should be no
>
> What known in
On Sat, Jan 15, 2005 at 01:09:08PM +1100, Nathan Scott wrote:
...
> > AFAIK the best you can do is to get the most recent XFS kernel from
> > SGI's CVS (this one is based on 2.6.10).
>
> The -mm tree also has these fixes; we'll get them merged into
> mainline soon.
Okeydokey - good
>
> > If you
On Fri, Jan 14, 2005 at 07:23:09PM +0100, Jakob Oestergaard wrote:
> So apart from the general well known instability problems that will
> occur when you actually start *using* the system, there should be no
What known instabilities?
-
To unsubscribe from this list: send the line "unsubscribe lin
15 matches
Mail list logo
