HAST role failure

[Mike Barnard]

Thanks Freddie,

For some reason, I still get the same error even after destroying the
journal.

hastctl create shared
[ERROR] [shared] Unable to open /dev/da0s1g: Operation not permitted.

When I check the status on the primary, I get this:

shared:
  role: init
  provname: shared
  localpath: /dev/da0s1g
  extentsize: 0
  keepdirty: 0
  remoteaddr: tcp4://172.19.254.15
  replication: memsync
  dirty: 0 bytes

I get the same log entry in var/log/messages:

Dec 13 16:24:53 hastA hastd[2325]: [shared] (primary) Unable to open
/dev/da0s1g: Operation not permitted.
Dec 13 16:24:58 hastA hastd[2319]: [shared] (primary) Worker process exited
ungracefully (pid=2325, exitcode=66).


Is there a way I can destroy a hast resource once created?


Regards,

Mike

On Fri, Dec 10, 2010 at 6:39 PM, Freddie Cash <fjwcash at gmail.com> wrote:

> On Fri, Dec 10, 2010 at 5:05 AM, Mike Barnard <mike.barnardq at gmail.com>
> wrote:
> > I have setup HAST on 2 FreeBSD 8.1-STABLE, hastA being primary and hastB
> > secondary.
> >
> > hastctl create mirror works with no problem on hastA, but when I run
> hastctl
> > role primary shared on the primary, it gives an error and fails:
> >
> > Dec 10 15:47:24 hastA hastd[9911]: [shared] (primary) Unable to open
> > /dev/da0s1g.journal: Operation not permitted.
> > Dec 10 15:47:29 hastA hastd[9888]: [shared] (primary) Worker process
> exited
> > ungracefully (pid=9911, exitcode=66).
>
> Create hast on the bare partition.
>
> Then create the gjournal device on top of the /dev/hast device.
>
> Then use the gjournal device for your filesystem.
>
> HAST really should be the lowest level in the storage chain.
>
> --
> Freddie Cash
> fjwcash at gmail.com
>



-- 
Mike

Of course, you might discount this possibility, but remember that one in
a million chances happen 99% of the time.
------------------------------------------------------------