[DRBD-user] DRBD device held open by someone

[Dileep Nayak]

Hi All,

While the issue "device held open by someone" was observed again today, we
found that e2fsck reported "Device or resource busy"

# e2fsck /dev/drbd0
e2fsck 1.39 (29-May-2006)
e2fsck: Device or resource busy while trying to open /dev/drbd0
Filesystem mounted or opened exclusively by another program?


Earlier we did not observe such "Device or resource busy" output from
e2fsck.

Please share your thoughts on the same.

Thanks
Dileep



O  4. Re: DRBD device held open by someone (Dileep Nayak)

>
>
>
>
>
>
> ------------------------------
>
> Message: 4
> Date: Wed, 22 Jun 2011 13:22:47 +0530
> From: Dileep Nayak <tech.disscuss2011 at gmail.com>
> Subject: Re: [DRBD-user] DRBD device held open by someone
> To: drbd-user at lists.linbit.com
> Message-ID: <BANLkTin2_qavGzsoEvxfgOSUCoMi5aDksA at mail.gmail.com>
> Content-Type: text/plain; charset="windows-1252"
>
> Thanks Lars for your reply.
>
> DRBD is used in conjunction with Linux-HA in a High Availability
> configuration to replicate data between the Active and Standby servers.
>
> Our product is running LVM (Logical Volume Manager) on top of DRBD.
>
> We are not using the nfs. The last point is not applicable in our case.
>
> And please can you explain bit more the below mentioned cases by you and
> how
> to detect/verify them when the issue ?Device is held open by someone? is
> occurred.
>
>  Regards,
>
> Dileep Nayak
>
>
> >   6. Re: DRBD device held open by someone (Lars Ellenberg)
> >
> >
> Message: 6
> Date: Wed, 22 Jun 2011 00:01:49 +0200
> From: Lars Ellenberg <lars.ellenberg at linbit.com>
> Subject: Re: [DRBD-user] DRBD device held open by someone
> To: drbd-user at lists.linbit.com
> Message-ID: <20110621220149.GF21892@
> >
> > barkeeper1-xen.linbit>
> > Content-Type: text/plain; charset=iso-8859-1
> >
> > On Tue, Jun 21, 2011 at 10:10:41AM +0530, Dileep Nayak wrote:
> > > TThanks Matt for your reply to the issue "*DRBD device held open by
> > someone*
> > > ".
> > > Today the below problem has been seen again.
> > >
> > >
> > >  State change failed: (-12) Device is held open by someone
> >
> > *Sometimes it is just udev or equivalent doing a race.
> > Sometimes it is a unix domain socket or similar still held open
> > (won't necessary show up in lsof/fuser).
> > Sometimes it is some device mapper targets not yet taken down.
> > Sometimes it is nfs locks not being properly released (in time).
> >
> > What do you use DRBD for, what sits on top of it?*
> >
> > --
> > : Lars Ellenberg
> > : LINBIT | Your Way to High Availability
> > : DRBD/HA support and consulting http://www.linbit.com
> >
> > DRBD? and LINBIT? are registered trademarks of LINBIT, Austria.
> > __
> > please don't Cc me, but send to list   --   I'm subscribed
> >
> >
> > ------------------------------
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://lists.linbit.com/pipermail/drbd-user/attachments/20110622/c42d1f20/attachment.html
> >
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20110630/52bc309d/attachment.htm>