Date: Tue, 12 Jun 2001 08:58:24 -0600 (MDT)
From: Russel Ingram <ringram@gargoylecc.com>
To: Ivan Rayner <ivanr@melbourne.sgi.com>
cc: <linux-xfs@oss.sgi.com>
Subject: Re: xfsdump, paride tape, and -m option
In-Reply-To: <Pine.SGI.4.32.0106121105330.209911-100000@omen.melbourne.sgi.com>
Message-ID: <Pine.LNX.4.33.0106111936010.2414-100000@localhost.localdomain>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-linux-xfs@oss.sgi.com
Precedence: bulk

On Tue, 12 Jun 2001, Ivan Rayner wrote:

> On Sun, 10 Jun 2001, Russel Ingram wrote:
>
> > > The argument to -b should be bytes, so 16k would be 16384 not 16.
> > >
> > > If this doesn't fix your problem, could you use -v5 to get verbose output.
> > > (This might produce alot of output, so you should redirect it to a file.)
> > >
> > > Ivan
> > >
> > Ok, I ran it again with the right sysntax on the -b option.  Here's the
> > command I gave it:
> >
> > xfsdump -v5 -m -b 32k -o -F -E -l0 -M"gumby" -L"tmp" -f /dev/tape -s tmp /
>
> The argument to -b should be bytes, so 32k would be '32768' not '32k'.
>
> Let me know if this helps.
>
> Ivan
I am still having trouble getting the drive itself to work right so it's
becoming more and more likely that this is a hardware problem rather than
an xfsdump problem, but even with the correct syntax on the -b otion it
still core dumps.  Thanx for all your help so far. Here's the command I
gave it this time:

xfsdump -m -b 32768 -o -F -E -l0 -M"gumby" -L"tmp" -f /dev/tape -s tmp /


Russ
-- 
Russ Ingram
Gargoyle Computer Consulting
(307)742-1361
www.gargoylecc.com