On Mon, Aug 07, 2000 at 08:47:47AM -0700, Gregory Leblanc wrote:
> > -Original Message-
> > From: James Manning [mailto:[EMAIL PROTECTED]]
> > Sent: Saturday, August 05, 2000 6:08 AM
> > To: Linux Raid list (E-mail)
> > Subject: Re: FAQ update
> >
>
> -Original Message-
> From: James Manning [mailto:[EMAIL PROTECTED]]
> Sent: Saturday, August 05, 2000 6:08 AM
> To: Linux Raid list (E-mail)
> Subject: Re: FAQ update
>
> [Luca Berra]
> > >The patches for 2.2.14 and later kernels are at
> > >
Here's one more update of the FAQ. Assuming not too many objections, I'll
send it to Jacob, and see if I can contact the list owner and get a footer
onto this list.
Greg
Linux-RAID FAQ
Gregory Leblanc
gleblanc (at) cu-portland.edu
Revision History
Revision v0
Yo Luca!
On Sat, 5 Aug 2000, Edward Schernau wrote:
> > i'd add: dont use netscape to fetch patches from mingo's site, it hurts
> > use lynx/wget/curl/lftp
>
> Works fine for me.
We are not worried about you. We are worried about mingos FTP
server. If you access an FPT server with Netscape
[Luca Berra]
> >The patches for 2.2.14 and later kernels are at
> >http://people.redhat.com/mingo/raid-patches/. Use the right patch for
> >your kernel, these patches haven't worked on other kernel revisions
> >yet.
>
> i'd add: dont use netscape to fetch patches from mingo's site
Luca Berra wrote:
> i'd add: dont use netscape to fetch patches from mingo's site, it hurts
> use lynx/wget/curl/lftp
Works fine for me.
--
Edward Schernau,mailto:[EMAIL PROTECTED]
Network Architect http://www.schernau.com
RC5-64#: 243249 e-gold ac
On Fri, Aug 04, 2000 at 01:47:23PM -0700, Gregory Leblanc wrote:
> Here's a new version, with a couple of changes. What other questions get
> asked all the time?
> Greg
>The patches for 2.2.14 and later kernels are at
>http://people.redhat.com/mingo/raid-patches/. Use the right patc
Tim Walberg wrote:
>
> On 08/04/2000 09:54 -0400, Theo Van Dinter wrote:
> >> The usual suggestion is:
> >>
> >> bzip2 -dc | tar -xf -
> >>
>
> or use bzcat, which is exactly the same as bzip2 -dc...
most versions of tar now support either I or y for (un)compress
--
Mathieu Arnold
On 08/04/2000 09:54 -0400, Theo Van Dinter wrote:
>> The usual suggestion is:
>>
>> bzip2 -dc | tar -xf -
>>
or use bzcat, which is exactly the same as bzip2 -dc...
--
+--+--+
| Tim Walberg | [EMAIL PROTECT
How about just putting something in like:
"Uncompressing the patch is beyond the scope of this document."
--
Edward Schernau,mailto:[EMAIL PROTECTED]
Network Architect http://www.schernau.com
RC5-64#: 243249 e-gold acct #:131897
On Fri, Aug 04, 2000 at 09:48:18AM +0530, Abhishek Khaitan wrote:
> Can;t we use bunzip2 instead of playing with tar? And after bunzip2, try tar
> -x kernel-2.2.16.tar ?
The usual suggestion is:
bzip2 -dc | tar -xf -
s/bzip2/gzip/ or s/bzip2/uncompress/ as necessary
--
Randomly Generated Ta
Can;t we use bunzip2 instead of playing with tar? And after bunzip2, try tar
-x kernel-2.2.16.tar ?
> -Original Message-
> From: James Manning [SMTP:[EMAIL PROTECTED]]
> Sent: Thursday, August 03, 2000 10:35 AM
> To: [EMAIL PROTECTED]
> Subject: Re: FAQ
> -Original Message-
> From: James Manning [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, August 03, 2000 10:35 AM
> To: [EMAIL PROTECTED]
> Subject: Re: FAQ
>
> [Marc Mutz]
> > >2.4. How do I apply the patch to a kernel that I just
> downlo
[Luca Berra]
> from the info page from gnu tar 1.13.17:
>
> `--bzip2'
> `-I'
> This option tells `tar' to read or write archives through `bzip2'.
As mentioned previously, this is a distro-specific hack. I have it in
my tar as well, but trusting it to be part of core GNU tar just because
it
On Thu, Aug 03, 2000 at 01:34:33PM -0400, James Manning wrote:
> there is no bzip2 standard in gnu tar, so let's be intelligent and avoid
> the issue by going with the .gz tarball as a recommendation. -z is
> standard.
>
from the info page from gnu tar 1.13.17:
`--bzip2'
`-I'
This option
[Marc Mutz]
> >2.4. How do I apply the patch to a kernel that I just downloaded from
> >ftp.kernel.org?
> >
> >Put the downloaded kernel in /usr/src. Change to this directory, and
> >move any directory called linux to something else. Then, type tar
> >-Ixvf kernel-2.2.16.tar.b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Marc ,
On Thu, 3 Aug 2000, Marc Mutz wrote:
> Gregory Leblanc wrote:
>
> >2.4. How do I apply the patch to a kernel that I just downloaded from
> >ftp.kernel.org?
> >Put the downloaded kernel in /usr/src. Change to this di
Marc Mutz wrote:
> My tar cannot use bz2-compressed unless used with
> --use-compress-program=bzip2. so that line sould probably read "bzcat
> kernel-2.2.16.tar.bz2 | tar xf -". Also the only tar I saw that knows
> bzip2 is slackware's and it uses the '-y' switch for that. I never saw
> the '-I'
Gregory Leblanc wrote:
>
>2.4. How do I apply the patch to a kernel that I just downloaded from
>ftp.kernel.org?
>
>Put the downloaded kernel in /usr/src. Change to this directory, and
>move any directory called linux to something else. Then, type tar
>-Ixvf kernel-2.2.16.ta
Can we get the list administrator to add a footer to each
message that has the URL of one of the archives?
It will cut down on the questions like "...where is the
FAQ?"
-ilia
Gregory Leblanc wrote:
Here's a quickie FAQ, it's very incomplete, but I
wanted to get some
feedback on what I've got righ
On Fri, 14 Jan 2000, D. Lance Robinson wrote:
>Ingo,
>
>I can fairly regularly generate corruption (data or ext2 filesystem) on a busy
>RAID-5 by adding a spare drive to a degraded array and letting it build the
>parity. Could the problem be from the bad (illegal) buffer interactions you
>mention
Hi,
Chris Wedgwood writes:
> > This may affect data which was not being written at the time of the
> > crash. Only raid 5 is affected.
>
> Long term -- if you journal to something outside the RAID5 array (ie.
> to raid-1 protected log disks) then you should be safe against this
> type of
Hi,
Benno Senoner writes:
> wow, really good idea to journal to a RAID1 array !
>
> do you think it is possible to to the following:
>
> - N disks holding a soft RAID5 array.
> - reserve a small partition on at least 2 disks of the array to hold a RAID1
> array.
> - keep the journal o
Ingo,
I can fairly regularly generate corruption (data or ext2 filesystem) on a busy
RAID-5 by adding a spare drive to a degraded array and letting it build the
parity. Could the problem be from the bad (illegal) buffer interactions you
mentioned, or are there other areas that need fixing as well
Chris Wedgwood wrote:
> > In the power+disk failure case, there is a very narrow window in which
> > parity may be incorrect, so loss of the disk may result in inability to
> > correctly restore the lost data.
>
> For some people, this very narrow window may still be a problem.
> Especially when
Hi,
On Wed, 12 Jan 2000 22:09:35 +0100, Benno Senoner <[EMAIL PROTECTED]>
said:
> Sorry for my ignorance I got a little confused by this post:
> Ingo said we are 100% journal-safe, you said the contrary,
Raid resync is safe in the presence of journaling. Journaling is not
safe in the presence
Hi,
On Wed, 12 Jan 2000 11:28:28 MET-1, "Petr Vandrovec"
<[EMAIL PROTECTED]> said:
> I did not follow this thread (on -fsdevel) too close (and I never
> looked into RAID code, so I should shut up), but... can you
> confirm that after buffer with data is finally marked dirty, parity
> is recomp
Hi,
On Wed, 12 Jan 2000 07:21:17 -0500 (EST), Ingo Molnar <[EMAIL PROTECTED]>
said:
> On Wed, 12 Jan 2000, Gadi Oxman wrote:
>> As far as I know, we took care not to poke into the buffer cache to
>> find clean buffers -- in raid5.c, the only code which does a find_buffer()
>> is:
> yep, this i
Hi,
On Tue, 11 Jan 2000 16:41:55 -0600, "Mark Ferrell"
<[EMAIL PROTECTED]> said:
> Perhaps I am confused. How is it that a power outage while attached
> to the UPS becomes "unpredictable"?
One of the most common ways to get an outage while on a UPS is somebody
tripping over, or otherwise r
"Stephen C. Tweedie" wrote:
> Ideally, what I'd like to see the reconstruction code do is to:
>
> * lock a stripe
> * read a new copy of that stripe locally
> * recalc parity and write back whatever disks are necessary for the stripe
> * unlock the stripe
>
> so that the data never goes through t
On Wed, 12 Jan 2000, Gadi Oxman wrote:
> As far as I know, we took care not to poke into the buffer cache to
> find clean buffers -- in raid5.c, the only code which does a find_buffer()
> is:
yep, this is still the case. (Sorry Stephen, my bad.) We will have these
problems once we try to elimin
On 11 Jan 00 at 22:24, Stephen C. Tweedie wrote:
> The race I'm concerned about could occur when the raid driver wants to
> compute parity for a stripe and finds some of the blocks are present,
> and clean, in the buffer cache. Raid assumes that those buffers
> represent what is on disk, naturall
James Manning wrote:
> [ Tuesday, January 11, 2000 ] Benno Senoner wrote:
> > The problem is that power outages are unpredictable even in presence
> > of UPSes therefore it is important to have some protection against
> > power losses.
>
> I gotta ask dying power supply? cord getting ripped o
Perhaps I am confused. How is it that a power outage while attached
to the UPS becomes "unpredictable"?
We run a Dell PowerEdge 2300/400 using Linux software raid and the
system monitors it's own UPS. When power failure occures the system
will bring itself down to a minimal state (runleve
- Original Message -
From: "Benno Senoner" <[EMAIL PROTECTED]>
To: "Stephen C. Tweedie" <[EMAIL PROTECTED]>
Cc: "Linux RAID" <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>; "Ingo Molnar" <[EMAIL PROTECTED]>
Sent: Tues
Hi,
On Wed, 12 Jan 2000 00:12:55 +0200 (IST), Gadi Oxman
<[EMAIL PROTECTED]> said:
> Stephen, I'm afraid that there are some misconceptions about the
> RAID-5 code.
I don't think so --- I've been through this with Ingo --- but I
appreciate your feedback since I'm getting inconsistent advise her
"Stephen C. Tweedie" wrote:
>
> Hi,
>
> On Tue, 11 Jan 2000 15:03:03 +0100, mauelsha
> <[EMAIL PROTECTED]> said:
>
> >> THIS IS EXPECTED. RAID-5 isn't proof against multiple failures, and the
> >> only way you can get bitten by this failure mode is to have a system
> >> failure and a disk fail
Hi,
On Tue, 11 Jan 2000 15:03:03 +0100, mauelsha
<[EMAIL PROTECTED]> said:
>> THIS IS EXPECTED. RAID-5 isn't proof against multiple failures, and the
>> only way you can get bitten by this failure mode is to have a system
>> failure and a disk failure at the same time.
> To try to avoid this k
"Stephen C. Tweedie" wrote:
>
> Hi,
>
> This is a FAQ: I've answered it several times, but in different places,
> THIS IS EXPECTED. RAID-5 isn't proof against multiple failures, and the
> only way you can get bitten by this failure mode is to have a system
> failure and a disk failure at the
Hi,
On Tue, 11 Jan 2000 20:17:22 +0100, Benno Senoner <[EMAIL PROTECTED]>
said:
> Assume all RAID code - FS interaction problems get fixed, since a
> linux soft-RAID5 box has no battery backup, does this mean that we
> will loose data ONLY if there is a power failure AND successive disk
> failur
"Stephen C. Tweedie" wrote:
(...)
>
> 3) The soft-raid backround rebuild code reads and writes through the
>buffer cache with no synchronisation at all with other fs activity.
>After a crash, this background rebuild code will kill the
>write-ordering attempts of any journalling files
> Is there a mailing list archive available? How about an FAQ?
While many archives are available, I use
http://www.mail-archive.com/linux-raid@vger.rutgers.edu/
Since it's a searchable archive, I tend to use that instead of
looking at any FAQ's as documentation appears to be lagging
devel
These questions are from the point of view of 0.90 or higher
(i.e. RH 6.0).
- How do you recover a RAID1 or a RAID5 with a bad disk when
you have no spares, i.e. how do you hotremove and hotadd? Please
go through it step by step because many paths seem to lead to
hangs.
- How do you recover a RAID
On Fri, 9 Jul 1999, Marc Mutz wrote:
> Bruno Prior wrote:
> >
> > It strikes me that this list desperately needs a FAQ. I'm off on holiday for the
> > next two weeks, but unless someone else wants to volunteer, I'm willing to put
> > one together when I get back. If people would like me to do thi
Bruno Prior wrote:
>
> It strikes me that this list desperately needs a FAQ. I'm off on holiday for the
> next two weeks, but unless someone else wants to volunteer, I'm willing to put
> one together when I get back. If people would like me to do this, I would
> welcome suggestions for questions
45 matches
Mail list logo
