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
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
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
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
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 10
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
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
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
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 to
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
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 --- there
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
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
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.
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
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
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. My
18 matches
Mail list logo
