From: Tomasz Chmielewski <mangoo@wpkg.org>
To: nfs@lists.sourceforge.net
Subject: Re: how to check if file locking is working?
Date: Thu, 26 Apr 2007 14:19:20 +0200 [thread overview]
Message-ID: <463098C8.8010900@wpkg.org> (raw)
In-Reply-To: <46308D00.5040109@wpkg.org>
Tomasz Chmielewski wrote:
> How can I check if file locking is working?
>
> I have a NFS4 server (Linux x86) and a NFS4 client (Linux ARM).
>
>
> NFS4 server exports a Debian-ARM root filesystem (/bin, /etc, /usr... a
> complete OS).
>
> I want to "upgrade" the Debian-ARM root filesystem in a NFS4 chroot, but
> it fails - dpkg claims that:
>
> debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by
> another process
>
> It's not true, as that export is only used by that one client.
>
> So what comes to my mind, is that file locking is somehow broken.
>
> How can I check if NFS4 file locking works properly, or is broken?
I changed the client to use NFSv3 instead of NFSv4, and suddenly, the
things started to work...
Ideas what I might be missing? Why locking works if I use NFSv3 on the
client, but doesn't when I use NFSv4 on the client (other than NFS
version, nothing else changed).
Kernel option on a client or server, export options on the server, mount
options on the client etc.?
--
Tomasz Chmielewski
http://wpkg.org
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2007-04-26 12:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-26 11:29 how to check if file locking is working? Tomasz Chmielewski
2007-04-26 12:19 ` Tomasz Chmielewski [this message]
2007-04-29 21:27 ` Trond Myklebust
2007-05-01 6:24 ` Tomasz Chmielewski
2007-05-01 7:01 ` Trond Myklebust
2007-05-03 13:36 ` Tomasz Chmielewski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=463098C8.8010900@wpkg.org \
--to=mangoo@wpkg.org \
--cc=nfs@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox