Numerical argument out of domain: Difference between revisions
Paul.bijnens (talk | contribs) No edit summary |
(→Problem: man links) |
||
(7 intermediate revisions by 3 users not shown) | |||
Line 1: | Line 1: | ||
You have a [[ | {{Troubleshooting Header}} | ||
=Problem= | |||
{{XXX|Dustin|RAIT Device in Device API does not return these errors!}} | |||
You have a [[How To:Set Up RAIT (Redundant Array of Independent Tapes)|RAIT]] setup, and {{man|8|amcheck}} (and many other commands) return an error like: | |||
$ amcheck test | $ amcheck test | ||
Line 5: | Line 8: | ||
amcheck-server: slot 2: reading label: Numerical argument out of domain | amcheck-server: slot 2: reading label: Numerical argument out of domain | ||
=Explanation= | |||
The EDOM error (Numerical argument out of domain) points to an XOR sum mismatch when reading a RAIT set. | 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 read error on the one of the members of the RAIT set | That could result when you have a read error on the one of the members of the RAIT set that was not flagged by the individual tape drive. | ||
that was not flagged by the individual tape drive. | |||
More frequently however you inserted the wrong tape in one of the drives and one | 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. | ||
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 | =Solution= | ||
themselves), you must use | 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. | member tape. Let's suppose you have a RAIT setup with chg-multi, and the contents of slot 2 are: | ||
slot 2 rait:{file:/amandatapes/daily/vtape2,/dev/nst0} | slot 2 rait:{file:/amandatapes/daily/vtape2,/dev/nst0} | ||
Line 39: | Line 40: | ||
In the above example, member 1 (a vtape) has a tape labeled "DAILY-02" in slot 2, | 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 " | while the physical tapedrive has a tape labeled "Test-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 | 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 | resulting the XOR sum mismatch, and the RAIT driver could not rebuild the data from the | ||
other streams. | other streams. |
Latest revision as of 23:11, 30 June 2008
This article is a part of the Troubleshooting collection.
Problem
XXX | User:Dustin: RAIT Device in Device API does not return these errors! |
Other languages: [[::Numerical argument out of domain|English]] {{#ifexist: {{#if: | | {{#if: | :}}Numerical argument out of domain}}/Fr | • {{#if: |français| [[::Numerical argument out of domain/Fr|français]]}}|}}
{{#ifexist: {{#if: | | {{#if: | :}}Numerical argument out of domain}}/Zh-cn | • {{#if: |中文(中国大陆)| [[::Numerical argument out of domain/Zh-cn|中文(中国大陆)]]}}|}}
You have a RAIT setup, and amcheck(8) (and many other commands) return an error like:
$ amcheck test ... amcheck-server: slot 2: reading label: Numerical argument out of domain
Explanation
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 read error on the one of the members of the RAIT set that was not flagged by the individual tape drive.
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.
Solution
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. Let's suppose you have a RAIT setup with chg-multi, and the contents of slot 2 are:
slot 2 rait:{file:/amandatapes/daily/vtape2,/dev/nst0}
Then get the label of each member of the RAIT:
$ 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 "Test-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.