[DRBD-user] Errors with flock()

Kamran Nisar mkamrannisar at gmail.com
Sat Dec 23 08:46:25 CET 2006

Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.


hi,
when I forced an artifical failure of the primary, then while accesing the
secondary <new primary>, i got the error..
{the take over had been succusfull and the secondary had become primar, and
the device mounted}

flock File_name echo "locked"
flock: No locks available


regards


On 12/23/06, Kamran Nisar <mkamrannisar at gmail.com> wrote:
>
> hi, the nfs options are as below
> /data/export/
> 192.168.0.0/255.255.0.0(rw,no_root_squash,no_all_squash,sync)<http://192.168.0.0/255.255.0.0%28rw,no_root_squash,no_all_squash,sync%29>
>
> regards
>
>
> On 12/22/06, KOZMAN Balint <bkozman at imind.hu> wrote:
> >
> >
> > What are your nfs client mount options? Like soft, nolock, etc.
> >
> >
> > Balint
> >
> >
> > On Thu, 21 Dec 2006, Kamran Nisar wrote:
> >
> > > hi
> > > sorry my bad.. the part where I say mounting it in a different path
> > works,
> > > was bogus. It turned out my admin mounted another share and mistook it
> > for
> > > the same drbd-nfs one...
> > >
> > > so the problem still holds...
> > >
> > > drdb-nfs mounted on a client is giving me Stale handler error while
> > > obtaining lock :(
> > >
> > >
> > > regards
> > >
> > > On 12/20/06, Kamran Nisar <mkamrannisar at gmail.com> wrote:
> > > >
> > > > HI,
> > > > Using Suse with kernel version 2.6.16.
> > > > strangely enough, if i mount the nfs share in a different path, then
> > it
> > > > works fine. I tried restarting all related services on both client
> > and the
> > > > server, system reboot as well, changed files as well.. nuthing fixes
> > in this
> > > > particular directory
> > > >
> > > > definately seems like  some *voodoo* factor associated with a
> > previous
> > > > mount/umount session to the same path  on the client :| how to get
> > rid of
> > > > that :( since directory is being used in all the code everywhere,
> > i'd rather
> > > > fix access through it then create another mount.
> > > >
> > > > thanks
> > > > regards
> > > > Kami
> > > > On 12/20/06, Darren Hoch <darren.hoch at litemail.org> wrote:
> > > > >
> > > > > Kamran,
> > > > >
> > > > > This is purely NFS and not DRBD. What OS and kernel version? There
> > are
> > > > > some flock() issues in RedHat EL 3.x and associated Fedora
> > branches that
> > > > > were fixed between minor releases.
> > > > >
> > > > > Darren
> > > > >
> > > > >
> > > > > Lars Ellenberg wrote:
> > > > >
> > > > > >/ 2006-12-20 17:59:10 +0500
> > > > > >\ Kamran Nisar:
> > > > > >
> > > > > >
> > > > > >>HI,
> > > > > >>I have my primary device mounted on client as an nfs share. an
> > attempt
> > > > > to
> > > > > >>obtain and exclusive lock over a file fails with the following
> > error
> > > > > >>
> > > > > >>nagios-ffm:/data # touch test
> > > > > >>nagios-ffm:/data # flock test echo "itWorks"
> > > > > >>flock: Stale NFS file handle
> > > > > >>
> > > > > >>
> > > > > >
> > > > > >works for me.
> > > > > >so this is not per se a drbd problem.
> > > > > >more likely some nfs woodoo.
> > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > > _______________________________________________
> > > > > drbd-user mailing list
> > > > > drbd-user at lists.linbit.com
> > > > > http://lists.linbit.com/mailman/listinfo/drbd-user
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Regards
> > > > M Kamran Nisar,
> > >
> > >
> > >
> > >
> > > --
> > > Regards
> > > M Kamran Nisar,
> > >
> >
> >
> >
>
>
> --
> Regards
> M Kamran Nisar,




-- 
Regards
M Kamran Nisar,
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20061223/c91fd6e5/attachment.htm>


More information about the drbd-user mailing list