From: Nathan Dietsch <njd@ndietsch.com>
To: Guy <bugzilla@watkins-home.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: RAID5 crash and burn
Date: Mon, 01 Nov 2004 20:01:37 +1100 [thread overview]
Message-ID: <4185FB71.6040900@ndietsch.com> (raw)
In-Reply-To: <200411010701.iA171QN31414@www.watkins-home.com>
Hello Guy,
Guy wrote:
>Back to swapping. I can't think how swapping could be better than having
>enough memory.
>
>
Now here is a guy[0] that knows what I am talking about.
Mark: This is exactly what I was getting at.
Regards,
Nathan
[0] Pun intended
next prev parent reply other threads:[~2004-11-01 9:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-31 4:59 RAID5 crash and burn coreyfro
2004-10-31 5:18 ` Guy
2004-10-31 9:59 ` coreyfro
2004-10-31 11:26 ` Robin Bowes
2004-10-31 17:19 ` coreyfro
2004-10-31 13:15 ` Guy
2004-10-31 13:54 ` Nathan Dietsch
2004-10-31 19:41 ` Mark Hahn
2004-11-01 4:26 ` Nathan Dietsch
2004-11-01 5:29 ` Mark Hahn
2004-11-01 6:05 ` Nathan Dietsch
2004-11-01 6:32 ` Mark Hahn
2004-11-01 7:01 ` Guy
2004-11-01 9:01 ` Nathan Dietsch [this message]
2004-11-01 8:58 ` Nathan Dietsch
2004-10-31 19:05 ` Michael Robinton
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=4185FB71.6040900@ndietsch.com \
--to=njd@ndietsch.com \
--cc=bugzilla@watkins-home.com \
--cc=linux-raid@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).