-
From: Mark Woolfson [mailto:i...@woolfcomputing.com]
Sent: Thursday, March 14, 2013 7:12 PM
To: Satyajit Paul
Subject: RE: [DRBD-user] State change failed: Device is held open by someone
Satyajit,
Send me a copy of your actual haresources file and I will see if I can find
anything that seems out
e required ?
Thanks in anticipation.
Regards,
Satyajit Paul
Software Engineer
India
-Original Message-
From: [hidden email] [mailto:[hidden email]] On Behalf Of mwoolfso
Sent: Tuesday, March 12, 2013 10:05 PM
To: [hidden email]
Subject: Re: [DRBD-user] State change failed: Devic
Ellenberg; drbd-user@lists.linbit.com
Subject: Re: [DRBD-user] State change failed: Device is held open by someone
Hello Mwoolfso,
>From your email "The solution to my particular problem was an improperly
>formatted haresources file for Heartbeat. Heartbeat was commanding DRBD to
>un
d in
yellow above. Please provide some thoughts.
Cheers!!
Satyajit Paul
India
-Original Message-
From: Felix Frank [mailto:f...@mpexnet.de]
Sent: Wednesday, March 13, 2013 3:00 PM
To: Satyajit Paul
Cc: drbd-user@lists.linbit.com
Subject: Re: [DRBD-user] State change failed: Device is held o
On Wed, Mar 13, 2013 at 10:30:02AM +0100, Felix Frank wrote:
> Hi Satyajit,
>
> this is an instace of thread confusion. The haresources answer was not
> actually directed to you, but instead belongs to an old thread that
> happens to have the same subject.
>
> The proposed solutions applies to se
Hi Satyajit,
this is an instace of thread confusion. The haresources answer was not
actually directed to you, but instead belongs to an old thread that
happens to have the same subject.
The proposed solutions applies to setups with the obsolete heartbeat
cluster stack, which you are (hopefully) n
n Behalf Of mwoolfso
Sent: Tuesday, March 12, 2013 10:05 PM
To: drbd-user@lists.linbit.com
Subject: Re: [DRBD-user] State change failed: Device is held open by someone
The solution to my particular problem was an improperly formatted haresources
file for Heartbeat.
Heartbeat was commanding DRBD
The solution to my particular problem was an improperly formatted haresources
file for Heartbeat.
Heartbeat was commanding DRBD to unmount/detach a filesystem when a key
service was not yet shut down. Once I cleared that up not only did the
messages go away but failover occurs within 2-3 second
.com]
On Behalf Of Lars Ellenberg [lars.ellenb...@linbit.com]
Sent: Monday, March 11, 2013 3:22 PM
To: drbd-user@lists.linbit.com
Subject: Re: [DRBD-user] State change failed: Device is held open by someone
On Sat, Mar 09, 2013 at 08:55:42PM +0530, Satyajit Paul wrote:
> Hello Lars,
>
> Thanks
On Sat, Mar 09, 2013 at 08:55:42PM +0530, Satyajit Paul wrote:
> Hello Lars,
>
> Thanks for the reply.
>
> Can you please share some thoughts, in case of drbd_open() function,
> locking/unlocking is explicitly invoked and incase of drbd_close()
> function, it is not invoked explicitly ?
>>
>> Th
7091
From: drbd-user-boun...@lists.linbit.com [drbd-user-boun...@lists.linbit.com]
On Behalf Of Lars Ellenberg [lars.ellenb...@linbit.com]
Sent: Friday, March 08, 2013 7:54 PM
To: drbd-user@lists.linbit.com
Subject: Re: [DRBD-user] State change failed: Device is held
On Fri, Mar 08, 2013 at 05:07:23PM +0530, Satyajit Paul wrote:
> Hello,
>
> When I wanted to change the state of DRBD from primary to secondary,
> sometimes I get the "Device is held open by someone" issue.
> I looked into the code drbd_main.c (DRBD Release 8.0.11) and found that the
> error is
Hello,
When I wanted to change the state of DRBD from primary to secondary, sometimes
I get the "Device is held open by someone" issue.
I looked into the code drbd_main.c (DRBD Release 8.0.11) and found that the
error is set from the below code.
else if( ns.role == Secondary && mdev->open_c
> View this message in context:
> http://drbd.10923.n7.nabble.com/State-change-failed-Device-is-held-open-by-someone-tp11250p17357.html
Great. This ugly thing. I've found that it encourages list members to
refrain from quoting earlier messages, which I personally find
distasteful because I must c
Peter,
Did you ever find a resolution to this problem? I started having this
problem after 2 weeks of putting a NAS into production with 8.3.11. I
upgraded to 8.4.3 and still have the same issue.
--
View this message in context:
http://drbd.10923.n7.nabble.com/State-change-failed-Device-is-h
15 matches
Mail list logo
