<div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">I already send this message along with tons of others, but particularly for this one, can anyone explain why the error message says that the volume file got modified? How can this happen? How can this be prevented or be worked around?<br>
</blockquote><div><br>There is an option in GlusterFS where the client can pull a volume file from server (so the management of volumefile becomes easier). Assume you have 5 clients, which are already mounted with '-s' option and now, you modify the client's volume file on server, and now mount another client. This can cause a confusion in the filesystem in most of the cases as client volumefiles can be different. (Assume a case where first 5 client uses 'cluster/stripe' and the newer client uses 'cluster/replicate'). This timestamp check of volume file is present to prevent this behavior. <br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
[server-protocol.c:6553:_volfile_update_checksum] foo-server: the volume<br>
file got modified between earlier access and now, this may lead to<br>
inconsistency between clients, advised to remount client<br>
</blockquote><div> <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
The error clearly advises to remount the client, but why?<br>
<br>
</blockquote><div><br>Remount the connected clients. That means, the volume file used by those clients are no more valid, and when every client fetches new volumefile from server, things work fine.<br><br><br>If you want to disable the volumefile checksum on server, you can provide <br>
<br> "option verify-volfile-checksum off" <br><br>in server protocol volume.<br><br>Regards,<br><br></div></div>-- <br>Amar Tumballi<br><br>