Numerical argument out of domain: Difference between revisions

From wiki.zmanda.com
Jump to navigation Jump to search
No edit summary
 
No edit summary
Line 5: Line 5:
  amcheck-server: slot 2: reading label: Numerical argument out of domain
  amcheck-server: slot 2: reading label: Numerical argument out of domain


The EDOM error (Numerical argument out of domain) points to an XOR sum mismatch when reading a RAIT set.


This means that one of the members of the RAIT does not have the correct label, matching the other members.
That could result when you have a uncorrectable read error on the RAIT set.
More frequently however you inserted the wrong tape in one of the drives and one
of the members of the RAIT does not have the correct label, matching the other members.


To find out which member (apart from looking on the handwritten labels on the physical tapes
To find out which member (apart from looking on the handwritten labels on the physical tapes
Line 31: Line 34:
while the physical tapedrive has a tape labeled "Text-03".
while the physical tapedrive has a tape labeled "Text-03".
You need to find the physical tape labeled "DAILY-02" and insert that in the drive.
You need to find the physical tape labeled "DAILY-02" and insert that in the drive.
If both claim to be same tape, then you could have a hardware fault in one of the drives
resulting the XOR sum mismatch, and the RAIT driver could not rebuild the data from the
other streams.

Revision as of 23:09, 21 January 2006

You have a RAIT setup, and amcheck (and many other commands) return an error like:

$ amcheck test
...
amcheck-server: slot 2: reading label: Numerical argument out of domain

The EDOM error (Numerical argument out of domain) points to an XOR sum mismatch when reading a RAIT set.

That could result when you have a uncorrectable read error on the RAIT set. More frequently however you inserted the wrong tape in one of the drives and one of the members of the RAIT does not have the correct label, matching the other members.

To find out which member (apart from looking on the handwritten labels on the physical tapes themselves), you must use ammt and amdd to extract the first file from each member tape:

$ ammt -t file:/amandatapes/daily/vtape2 rewind
$ amdd  if=file:/amandatapes/daily/vtape2 bs=32k count=1
AMANDA: TAPESTART DATE X TAPE DAILY-02

1+0 in
1+0 out
$ ammt -t file:/amandatapes/daily/vtape2 rewind
$ ammt -t /dev/nst0 rewind
$ amdd  if=/dev/nst0 bs=32k count=1
AMANDA: TAPESTART DATE X TAPE Test-03

1+0 in
1+0 out
$ ammt -t /dev/nst0 rewind

In the above example, member 1 (a vtape) has a tape labeled "DAILY-02" in slot 2, while the physical tapedrive has a tape labeled "Text-03". You need to find the physical tape labeled "DAILY-02" and insert that in the drive.


If both claim to be same tape, then you could have a hardware fault in one of the drives resulting the XOR sum mismatch, and the RAIT driver could not rebuild the data from the other streams.