GNU bug report logs - #27666
[grep on GPFS filesystem] SEEK_HOLE problem

Previous Next

Package: grep;

Reported by: Moyard John <John.Moyard <at> cnes.fr>

Date: Wed, 12 Jul 2017 11:58:02 UTC

Severity: normal

Done: Paul Eggert <eggert <at> cs.ucla.edu>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Moyard John <John.Moyard <at> cnes.fr>
Subject: bug#27666: closed (Re: bug#27666: [grep on GPFS filesystem]
 SEEK_HOLE problem)
Date: Tue, 31 Dec 2019 19:16:02 +0000
[Message part 1 (text/plain, inline)]
Your bug report

#27666: [grep on GPFS filesystem] SEEK_HOLE problem

which was filed against the grep package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to 27666 <at> debbugs.gnu.org.

-- 
27666: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=27666
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
From: Paul Eggert <eggert <at> cs.ucla.edu>
To: Moyard John <John.Moyard <at> cnes.fr>
Cc: 27666-done <at> debbugs.gnu.org, Eric Blake <eblake <at> redhat.com>
Subject: Re: bug#27666: [grep on GPFS filesystem] SEEK_HOLE problem
Date: Tue, 31 Dec 2019 11:15:30 -0800
The GPFS SEEK_HOLE bug appears to have been fixed by IBM a few years ago, as
reported here:

https://www.spectrumscale.org/pipermail/gpfsug-discuss/2018-February/004595.html
https://www.spectrumscale.org/pipermail/gpfsug-discuss/2018-February/004596.html
https://www-01.ibm.com/support/docview.wss?uid=isg1IV87385

so I am closing the grep bug report.

[Message part 3 (message/rfc822, inline)]
From: Moyard John <John.Moyard <at> cnes.fr>
To: "bug-grep <at> gnu.org" <bug-grep <at> gnu.org>
Subject: [grep on GPFS filesystem] SEEK_HOLE problem
Date: Wed, 12 Jul 2017 09:27:50 +0000
[Message part 4 (text/plain, inline)]
Hi,

I use GPFS file system and I have sometimes an issue using grep command.
When issue occurs with the following message "Binary file <myfile> matches"
But "<myfile>" is an ASCII one, not a binary file.
The problem seems to deals with lseek(SEEK_HOLE) command and a file not completely flushed after close.
It could take several seconds to save the entire file on the disk.

So could grep command have another way to determine if input file is binary/ASCII instead using lseek(SEEK_HOLE) ?

Best regards
john


[Message part 5 (text/html, inline)]

This bug report was last modified 5 years and 195 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.