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?
--
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 - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
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 - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
On Thu, 2007-04-26 at 14:19 +0200, Tomasz Chmielewski wrote:
> 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.?
nfsroot does not support NFSv4 at this time.
Trond
-------------------------------------------------------------------------
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 - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
Trond Myklebust schrieb:
>>>> Kernel option on a client or server, export options on the server, mount
>>>> options on the client etc.?
>>> nfsroot does not support NFSv4 at this time.
>> Hmm, I didn't say anything about nfsroot, did I?
>>
>> I merely did a chroot over NFSv4, and some apps don't work well then.
>
> Sorry. I misread your mail. The easiest way to check basic locking would
> be to run the connectathon suite. See
> http://www.connectathon.org/#technologies
It looks like it's not working when I mount an export as NVSv4.
What can be wrong?
--
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 - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
Trond Myklebust schrieb:
> On Thu, 2007-04-26 at 14:19 +0200, Tomasz Chmielewski wrote:
>> 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.?
>
> nfsroot does not support NFSv4 at this time.
Hmm, I didn't say anything about nfsroot, did I?
I merely did a chroot over NFSv4, and some apps don't work well then.
--
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 - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
On Tue, 2007-05-01 at 08:24 +0200, Tomasz Chmielewski wrote:
> Trond Myklebust schrieb:
> > On Thu, 2007-04-26 at 14:19 +0200, Tomasz Chmielewski wrote:
> >> 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.?
> >
> > nfsroot does not support NFSv4 at this time.
>
> Hmm, I didn't say anything about nfsroot, did I?
>
> I merely did a chroot over NFSv4, and some apps don't work well then.
Sorry. I misread your mail. The easiest way to check basic locking would
be to run the connectathon suite. See
http://www.connectathon.org/#technologies
Trond
-------------------------------------------------------------------------
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 - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs