Your message dated Tue, 3 Oct 2017 20:21:29 +0200
with message-id <[email protected]>
and subject line Re: Bug#875925: hdf5: interaction with nfs changed between 
jessie and stretch
has caused the Debian Bug report #875925,
regarding hdf5: interaction with nfs changed between jessie and stretch
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
875925: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875925
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: hdf5
Version: 1.10.0-patch1+docs-3
Severity: important

Dear Maintainer,

after upgrading my system from jessie to stretch, I could not read anymore my 
hdf5 files located on
our nfs filesystem.

I have an error like this 

Can not flock ...

looking at the nfs documentation, I could find flock in the local_lock options 
which is set to
"none" on my system.

Since I red that some of these options can create conflict between lock 
mechanism.
And because I am not the only one accessing these files (other system are 
CentOS 5, 6).
I would like your opinion on the best way to solve this issue.

thanks for your help

Frédéric

-- System Information:
Debian Release: 9.1
  APT prefers stable
  APT policy: (500, 'stable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 4.9.0-3-686-pae (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

--- End Message ---
--- Begin Message ---
Hi,

Gilles Filippini a écrit le 16/09/2017 à 17:58 :
> Hi Frédéric,
> 
> [email protected] a écrit le 16/09/2017 à 07:25 :
>> Source: hdf5
>> Version: 1.10.0-patch1+docs-3
>> Severity: important
>>
>> Dear Maintainer,
>>
>> after upgrading my system from jessie to stretch, I could not read anymore 
>> my hdf5 files located on
>> our nfs filesystem.
>>
>> I have an error like this 
>>
>> Can not flock ...
>>
>> looking at the nfs documentation, I could find flock in the local_lock 
>> options which is set to
>> "none" on my system.
>>
>> Since I red that some of these options can create conflict between lock 
>> mechanism.
>> And because I am not the only one accessing these files (other system are 
>> CentOS 5, 6).
>> I would like your opinion on the best way to solve this issue.
> 
> Well, honestly I'm not at ease at all with file locking over NFS. Would
> you mind forwarding this question to upstream [1]?
> 
> [1] [email protected]
> 
> As I understand it, you should experience the very same problem using
> flock(1) shell command on these files. Is that correct?

I've had more info from Frédéric. He found out that the current version
of their NFS doesn't support file locking actually. Thus we've agreed on
closing this bug.

Thanks,

_g.

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---
_______________________________________________
Pkg-grass-devel mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel

Reply via email to