>From: Timothy Shimmin <tes@xxxxxxxxxxxxxxxxxxxxxxx>
>> So if you're on Irix and using an HSM other than DMF on an XFS filesystem th
>en
>> xfsdump is not going to do the right thing.
>>
>So, in other words, we only handle stuff for DMF.
>And this should work in Linux for DMF when we turn it on in
>xfsdump/xfsrestore and finish the necessary porting
>(or so the theory goes :).
Yes, the stuff should just work when we turn it on :)
xfsdump/xfsrestore can be used on filesystems managed by DMF, but they will
not play nicely on filesystems managed by other vendors' HSMs (in their
current state.) I'd mark this up as a consequence of proprietary systems, and
now that we're in the brave new world of free software some of that's bound to
change.
>> I noticed that on the Linux side xfsdump sets it to
>> zero--the Irix xfsdump doesn't touch it. The confusion is not surprising, I
>> guess.
>What bits of the code are you looking at here ?
On Linux it's in dump/content.c:
$ grep dmstate dump/*
dump/content.c: dst->bs_dmstate = (u_int16_t) 0; /* dunno */
Dean
|