[OpenAFS] Invalid cross-device link

Derrick Brashear shadow@gmail.com
Thu, 20 Aug 2009 11:07:04 -0400

On Thu, Aug 20, 2009 at 11:01 AM, Jeff Blaine<jblaine@kickflop.net> wrote:
>> It was determined out of list that the particular error I'm seeing in
>> this case is because I was adding a RO volume on the same server but
>> different partition as the RW volume. =A0While I know it's terrible
>> practice, it did work in previous versions and I was using it for
>> testing purposes. =A0Apparently, this is no longer allowed, and gives th=
>> errors that I'm seeing.
> We experienced the same "surprise!" last week when we tried
> to move all of the volumes on one fileserver to another
> in order to upgrade the former.
> The destination server already had its own replicas... of
> some of the volumes being moved. =A0This had always been allowed
> in the past for us.

The risk comes from serving stale data. The VLDB allows just one
volume of each type per server. The fileserver doesn't communicate
with the VLDB about volumes: it reads the disk. So it has to guess
which copy's the "right" one. What happens if it guesses wrong? You
report a bug because your releases are "losing your data" that's all
still there....you just don't see it.

It was only somewhat allowed in the past, anyway; a cross-device link
error was already returned in some cases. the difference is now the
behavior is consistent.