public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: "James A. Pattie" <james@pcxperience.com>, linux-kernel@vger.kernel.org
Subject: Re: Reiserfs, 3 Raid1 arrays, 2.4.1 machine locks up
Date: Thu, 22 Feb 2001 21:36:33 +0100	[thread overview]
Message-ID: <20010222213633.A14395@bug.ucw.cz> (raw)
In-Reply-To: <3A91A6E7.1CB805C1@pcxperience.com>
In-Reply-To: <3A91A6E7.1CB805C1@pcxperience.com>; from James A. Pattie on Mon, Feb 19, 2001 at 05:06:15PM -0600

Hi!

> I partitioned the 2 drives (on 1st and 2nd controller, both 1.3 GB each)
> into 4 total partitions.  1st is swap and then the next 3, 1 primary, 2
> extended are for raid 1 arrays.  I've given 20 MB to /boot (md0), 650MB
> to / (md1) and the rest (400+MB) to /var (md2).  I format md0 as ext2
> and md1 and md2 as reiserfs.  When I go to untar the image on the cd to
> /mnt/slash (which has md1 mounted on it), the system extracts about 30MB
> of data and then just stops responding.  No kernel output, etc.  I can
> change to the other virtual consoles, but no other keyboard input is
> accepted.  After resetting the machine, the raid arrays rebuild ok, and
> reiserfs gives me no problems other than it usually replays 2 or 3
> transactions.  If I tell tar to pickup on the last directory I saw
> extracted, it gets about another 30MB of data and stops again.  I've
> waited for the raid syncing to be finished or just started after the
> arrays are available and it doesn't matter.

Try running sync; sync; sync; ... while untarring.
								Pavel
-- 
I'm pavel@ucw.cz. "In my country we have almost anarchy and I don't care."
Panos Katsaloulis describing me w.r.t. patents at discuss@linmodems.org

  parent reply	other threads:[~2001-02-23  9:00 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-19 23:06 Reiserfs, 3 Raid1 arrays, 2.4.1 machine locks up James A. Pattie
     [not found] ` <96s93d$hh6$1@lennie.clouddancer.com>
     [not found]   ` <20010220135326.013DF682A@mail.clouddancer.com>
2001-02-20 17:32     ` James A. Pattie
2001-02-20 18:18       ` Colonel
2001-02-20 19:43         ` Tom Sightler
2001-02-20 19:56           ` James A. Pattie
2001-02-20 20:09             ` Tom Sightler
2001-02-20 21:06               ` James A. Pattie
2001-02-20 21:21           ` Colonel
2001-02-20 23:53             ` Roger Larsson
2001-02-21  3:49               ` Colonel
2001-02-21 14:45                 ` James A. Pattie
     [not found]                   ` <20010221161948.1FFD1682A@mail.clouddancer.com>
2001-02-21 16:43                     ` James A. Pattie
2001-02-21 20:26           ` Colonel
2001-02-22 20:36 ` Pavel Machek [this message]
2001-02-23 20:00 ` Jasmeet Sidhu

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=20010222213633.A14395@bug.ucw.cz \
    --to=pavel@suse.cz \
    --cc=james@pcxperience.com \
    --cc=linux-kernel@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