Hello,
We've experienced a weird data "rollback" on our NFS servers.
We have two NFS servers. Both running 8.3-RELEASE-p3. We've
setup HAST for one partition between both of them. To be able
to switch fast we configured gjournal on top of HAST. At the
time there was no UFS+J.
Yesterday one of the servers crashed and CARP changed the
slave to master. During that operation we got the following error:
GEOM_JOURNAL: Journal 2180207123: hast/shared contains data.
GEOM_JOURNAL: Journal 2180207123: hast/shared contains journal.
GEOM_JOURNAL: Cannot decode journal header from hast/shared.
GEOM_JOURNAL: Journal on hast/shared is broken/corrupted. Initializing.
GEOM_JOURNAL: clean=1 flags=0x40
GEOM_JOURNAL: File system hast/shared marked as dirty.
Did a full fsck and no errors were detected. The filesystem was working
again.
After looking at the data we saw that all the files in the last days
were missing. Like if both servers were disconnected, but that didn't
happen.
Even more: after our first NFS server was up again, no split-brain condition
was detected.
We're sure the first NFS server was working because all of the data is on
the backup servers. So it's not like the data never got written.
What could explain that data rollback? If gjournal's journal is lost
it's
possible to lose the data of a few days ago? Is not recommended to use gjournal
with HAST?
Thanks a lot.
Regards.
Victor.
hast.conf:
replication fullsync
#compression lzf
#checksum sha256
on nfs01 {
listen 192.168.23.81
}
on nfs02 {
listen 192.168.23.82
}
resource shared {
name shared
local /dev/mirror/oss1g
on nfs01 {
remote 192.168.23.82
}
on nfs02 {
remote 192.168.23.81
}
}
--
La prueba m?s fehaciente de que existe vida inteligente en otros
planetas, es que no han intentado contactar con nosotros.