Steven Whitehouse <swhiteho@xxxxxxxxxx> writes:
> That looks like it is trying to free a block that is already marked as
> being free. fsck should fix that. What version of gfs2-utils are you
> using?
Hello,
We are using 3.1.6-0ubuntu1.
Running an fsck is quite expensive for us, 4 hours with the shared FS
unusable.
I forgot to say that it stores qcow2 images, so there should not be
concurrency on the file system except on some directories to
create/access sub directories:
<GFS2 mount point>/<DIRECTORY OF RUNNING VMs>/<VM ID>/<QCOW2 images>
Only the <DIRECTORY OF RUNNING VMs> should have concurrent write
accesses, everything under <VM ID> is accessed only by one node at a
time, except for monitoring which is read only.
So “looks like it is trying to free a block that is already marked as
being free” looks strange.
Regards.
--
Daniel Dehennin
Récupérer ma clef GPG: gpg --recv-keys 0xCC1E9E5B7A6FE2DF
Fingerprint: 3E69 014E 5C23 50E8 9ED6 2AAD CC1E 9E5B 7A6F E2DF
Attachment:
signature.asc
Description: PGP signature
-- Linux-cluster mailing list Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
