Re: xfsdump Problems
From: noorg (engineer_at_noorg.org)
Date: 08/14/04
- Previous message: <<>>: "Re: windows 2003 on SGI 540..."
- In reply to: Thomas Jahns: "Re: xfsdump Problems"
- Next in thread: Thomas Jahns: "Re: xfsdump Problems"
- Reply: Thomas Jahns: "Re: xfsdump Problems"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Sat, 14 Aug 2004 20:53:12 GMT
Hi Thomas,
> noorg <engineer@noorg.org> writes:
> [xfs_repair reports no errors, /var/lib/xfsdump new, probably no tmp
> problem]
>
> Another thought that crossed my mind is this: xfsdump might fail if the
> tape drive capabilities are entered incorrectly in
> /var/sysgen/master.d/scsi? You have put an entry there, haven't you?
>
> If so could you post your entry, it would correspond to the following
> entry for an HP 1533 drive:
>
> { DATTAPE, TPDAT, 2, 6, "HP", "C1533A", 0, 0, {0, 0, 0, 0},
> MTCAN_BSF|MTCAN_BSR|MTCAN_APPEND|MTCAN_SETMK|MTCAN_PART|MTCAN_PREV|
> MTCAN_SYNC|MTCAN_SPEOD|MTCAN_CHKRDY|MTCAN_VAR|MTCAN_SETSZ|
> MTCAN_SILI|MTCAN_SEEK|MTCAN_CHTYPEANY,
> /* minimum delay on i/o is 4 minutes, because when a retry is
> * performed, the drive retries a number of times, and then
> * rewinds to BOT, repositions, and tries again. */
> 40, 4*60, 4*60, 5*60, 512, 512*512 },
Here is the /var/sysgen/master.d/scsi entry:
{ DATTAPE, TPDAT, 7, 12, "ARCHIVE", "Python 01931" /*DDS2*/, 0, 0, {0},
/* note: this drive uses modeselect page 0xf for compression
control;
* most of the other drives supporting compression use page 0x10 */
MTCAN_BSF|MTCAN_BSR|MTCAN_APPEND|MTCAN_SETMK|MTCAN_PART|MTCAN_PREV|
MTCAN_SYNC|MTCAN_SPEOD|MTCAN_CHKRDY|MTCAN_VAR|MTCAN_SETSZ|
MTCAN_SILI|MTCAN_AUDIO|MTCAN_SEEK|MTCAN_CHTYPEANY|MTCAN_COMPRESS,
/* minimum delay on i/o is 4 minutes, because when a retry is
* performed, the drive retries a number of times, and then
* rewinds to BOT, repositions, and tries again. */
40, 4*60, 4*60, 5*60, 3*3600, 512, 512*512,
tpsc_default_dens_count, tpsc_default_hwg_dens_names,
tpsc_default_alias_dens_names,
{0}, 0, 0, 0,
0, (u_char *)0 },
> and how is your tape drive reported in hinv?
Tape drive: unit 5 on SCSI controller 0: DAT
`mt status` reports:
Device: ARCHIVE: Python 01931-XXX5.63
Thanks,
Josh.
> Thomas Jahns
> --
> "Computers are good at following instructions,
> but not at reading your mind."
> D. E. Knuth, The TeXbook, Addison-Wesley 1984, 1986, 1996, p. 9
-- .------------------------------------------------. | Josh Birnbaum Mail: engineer@noorg.org | | President Internet: www.noorg.org | | Noorg, Inc | | ---------------------------------------------- | | ifchk - host based promiscuous mode detection | | & handling available for download at: | | http://www.noorg.org/ifchk/ | `------------------------------------------------'
- Previous message: <<>>: "Re: windows 2003 on SGI 540..."
- In reply to: Thomas Jahns: "Re: xfsdump Problems"
- Next in thread: Thomas Jahns: "Re: xfsdump Problems"
- Reply: Thomas Jahns: "Re: xfsdump Problems"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|