Bug#987177: lockfile-progs: lockfile creation failing on cifs mounts

2021-09-06 Thread Nils
dotlock / dotlock -u work fine without error messages

Bug#987177: lockfile-progs: lockfile creation failing on cifs mounts

2021-09-06 Thread Nils
I can verify that it still exists on Buster: nils@smidge:/mnt/nas/backup/scripts/smidge$ mkdir tmp_locktest nils@smidge:/mnt/nas/backup/scripts/smidge$ cd tmp_locktest/ nils@smidge:/mnt/nas/backup/scripts/smidge/tmp_locktest$ lockfile-create testlock lockfile creation failed: Value too large for

Bug#987177: lockfile-progs: lockfile creation failing on cifs mounts

2021-09-06 Thread Nils
Also exists on Bullseye: nils@smidge:/mnt/nas/backup/scripts/smidge/tmp_locktest$ lockfile-create testlock lockfile creation failed: Value too large for defined data type nils@smidge:/mnt/nas/backup/scripts/smidge/tmp_locktest$ ll total 1 drwxr-xr-x 2 nils nils 0 SepĀ  6 12:51 ./ drwxr-xr-x

Bug#987177: lockfile-progs: lockfile creation failing on cifs mounts

2021-09-03 Thread Rob Browning
Nils writes: > lockfile creation fails on a cifs mounted drive with "lockfile > creation failed: Value too large for defined data type" Hmm, lockfile-create is really a very simple wrapper around a call to lockfile_create(1), and offhand, I don't see any obvious way the arguments being passed

Bug#987177: lockfile-progs: lockfile creation failing on cifs mounts

2021-04-19 Thread Nils
Package: lockfile-progs Version: 0.1.18 Severity: important Dear Maintainer, lockfile creation fails on a cifs mounted drive with "lockfile creation failed: Value too large for defined data type" The problem was seen on the running kernel 5.10.0 and also on linux-image-4.19.0-16-686-pae The