From: Alistair John Strachan <alistair@devzero.co.uk>
To: Nathan Scott <nathans@sgi.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Copying huge amount of data on ReiserFS, XFS and Silicon Image 3112 cause oops.
Date: Tue, 14 Sep 2004 11:59:54 +0100 [thread overview]
Message-ID: <200409141159.54889.alistair@devzero.co.uk> (raw)
In-Reply-To: <20040914081440.GC5083@frodo>
On Tuesday 14 September 2004 09:14, you wrote:
> On Tue, Sep 14, 2004 at 12:44:25AM +0200, Marcin Garski wrote:
> > [Please CC me on replies, I am not subscribed to the list, thanks]
> >
> > Hello,
> >
> > I bought a new HDD Maxtor 6Y160M0 and connected it as hdg to Sil 3112
> > (CONFIG_BLK_DEV_SIIMAGE) on Abit NF7-S V2.0. I also have ST380013AS
> > (with Fedora Core 2 on hde2 and 2.6.5 kernel) as hde.
>
> Possible hardware problems? Have you run memtest there?
>
> Was 4KSTACKS enabled in those kernels (I think so)? - XFS
> has one known problem with that option when running low on
> space (patch fixing that is being tested atm) and I think
> the reiserfs folks had some 4k stack issues as well at one
> point, so that might be another explanation.
>
Just out of interest, how low is "low space"? I've got a few machines I can't
reboot running XFS+4K stacks; no problems so far but I'd like to sidestep
them if possible.
--
Cheers,
Alistair.
personal: alistair()devzero!co!uk
university: s0348365()sms!ed!ac!uk
student: CS/AI Undergraduate
contact: 1F2 55 South Clerk Street,
Edinburgh. EH8 9PP.
next prev parent reply other threads:[~2004-09-14 11:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-13 22:44 Copying huge amount of data on ReiserFS, XFS and Silicon Image 3112 cause oops Marcin Garski
2004-09-14 8:14 ` Nathan Scott
2004-09-14 10:59 ` Alistair John Strachan [this message]
2004-09-14 14:12 ` Steve Lord
2004-09-14 15:01 ` Alistair John Strachan
-- strict thread matches above, loose matches on Subject: below --
2004-09-14 15:42 Marcin Garski
2004-09-14 19:04 Christian Guggenberger
2004-09-18 21:18 Marcin Garski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200409141159.54889.alistair@devzero.co.uk \
--to=alistair@devzero.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=nathans@sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox