Peter,
I did not want to flood my first email with details and make it 3 pages
long. i gladly will provide more details. first I'd like to ask that you be
less condescending. You have no idea the journey I took toward using ocfs2
in this environment, and also the requirements I needed to meet.
you were amazed and astonished by my question, and I was amazed and
astonished by your answer.
let's start over:
if ocfs2 isnt the right solution for what I'm doing I can admit that, and
move off of it.
if OpenStack and perhaps newer kernels do not necessarily work with ocfs2 I
can admit that too, and move off of it.
I had high hopes it was the right solution, and at first it did the job.
I have a healthy HP MSA 2040 storage appliance connected to via fiber
channel. It has a 7TB storage volume on a fiber channel LUN. From what I
know I need a shared storage filesystem so each of my client systems, also
on the fiber channel network, can access this storage simultaneously with
corrupting data (I need file locking). This HP MSA is healthy and stable.
This isn't exactly local storage I know, but each client system sees this
MSA storage volume as a local drive, ie: /dev/sdb
what could cause a "lost" wakeup from the OCFS2 lock manager?
Ubuntu has ocfs2 packages in it's repos. So I hope it has some level of
support in it's OSs and distributed kernels...
I am not well versed in storage concepts but i'll surprise you, and today
my employer (who signs my paycheck) asks me, and tasks me, with making this
storage solution work better.
please let me know if I can provide more details. please let me know any
further comments
thanks!
-- Jim
On Wed, Dec 27, 2017 at 1:16 PM, Peter Grandi <pg at ocfs.list.sabi.co.uk>
wrote:
> > I have a ocfs2 filesystem setup as a shared filesystem between
> > 12 openstack compute nodes which are Ubuntu 16.04.3.
>
> I am amazed by how unconstrained are the imaginations of some
> other people. That is a truly astonishing setup.
>
> > I have a very big concern of stability. A month ago I lost a
> > good deal of files, I don't know the real reason, but things
> > seemed to point to the ofcs2 cluster.
>
> That also seems to me unconstrained by concern about mere
> details.
>
> > Last week I found many of my compute nodes with the nova
> > service down. The node which went down first has a "stuck"
> > file/directory in the ocfs2 filesystem [ ... ]
>
> The stack trace seems to point at a "lost" wakeup from the OCFS2
> lock manager.
>
> > I have other openstack compute nodes that are identical except
> > they use local storage and do not use ocfs2 and these have
> > always been stable.
>
> But OCFS2 is meant to work with local physical storage on a
> local phyical machine. What's your current setup?
>
> > maybe ocfs2 just isn't stable on Ubuntu 16.04.3? I am using
> > version 1.6.4-3.1
>
> OCFS2 has been extremely stable for many years on very high load
> share-disk clusters for many users. OpenStack and perhaps newer
> kernels not necessarily so.
>
> Also OCSF2 requires a storage subsystem with specific features
> and a high degree of reliable operation. It is astonishing but
> fairly typical that this reports contains no mention of the
> setup or of the state of the storage subsystem.
>
> _______________________________________________
> Ocfs2-users mailing list
> Ocfs2-users at oss.oracle.com
> https://oss.oracle.com/mailman/listinfo/ocfs2-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://oss.oracle.com/pipermail/ocfs2-users/attachments/20171227/cd94a28f/attachment-0001.html