bug#27666: closed ([grep on GPFS filesystem] SEEK_HOLE problem)

[GNU bug Tracking System]

Your message dated Tue, 31 Dec 2019 11:15:30 -0800
with message-id <address@hidden>
and subject line Re: bug#27666: [grep on GPFS filesystem] SEEK_HOLE problem
has caused the debbugs.gnu.org bug report #27666,
regarding [grep on GPFS filesystem] SEEK_HOLE problem
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden.)


-- 
27666: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=27666
GNU Bug Tracking System
Contact address@hidden with problems

--- Begin Message --- Subject: [grep on GPFS filesystem] SEEK_HOLE problem Date: Wed, 12 Jul 2017 09:27:50 +0000

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

 

 

--- End Message ---

> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#27666: [grep on GPFS filesystem] SEEK_HOLE problem
>
>
>
>
> Date: 
>
> Tue, 31 Dec 2019 11:15:30 -0800
>
>
>
>
> User-agent: 
>
> Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.2.2
>
>
>
>
> 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.
>
>
> --- End Message ---