On 08/20/2017 08:01 PM, Eric Sandeen wrote:
The difference between my office and the customer is that I use a hardware raid (raid 1) card and the customer uses RSTe ("e" for enterprise) RAID 1, which is a pseudo software raid. Maybe a lot of stuff is floating around in the either (cache) that is not sync'ed to the drive pair and xfsdump is not happy about it.
The underlying storage will not affect this.
I am wonder if it would be possible for xfsdump to can "sync; sync" itself before starting. That would insure a clean slate.
No; that's a guess, not a root cause analysis - we won't be putting hacks like that in based on hunches.
You have a point. It is still in the hunch phase.
If you want to investigate more, find out where in the code the error spits out, and do more error reporting there; find out what error code is actually being returned. actually I suppose strace would work for this as well. Knowing which error code the ioctl fails with would offer a clue about why. -Eric
I have no idea how to do that. :'( -Todd -- To unsubscribe from this list: send the line "unsubscribe linux-xfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
