GNU bug report logs - #23273
Error using windows 10 bash error 0x53464846 doing a tail -f

Previous Next

Full log

View this message in rfc822 format

From: Pádraig Brady <P <at> draigBrady.com>
To: Bernhard Voelker <mail <at> bernhard-voelker.de>, Dennis J <upumop <at> msn.com>, 23273-done <at> debbugs.gnu.org
Subject: bug#23273: Error using windows 10 bash error 0x53464846 doing a tail -f
Date: Thu, 21 Apr 2016 22:15:45 +0100

On 21/04/16 21:57, Pádraig Brady wrote:
> On 12/04/16 09:11, Bernhard Voelker wrote:
>> On 04/12/2016 01:54 AM, Pádraig Brady wrote:
>>> On 11/04/16 23:37, Dennis J wrote:
>>>> I'm getting this error when doing a tail -f on a simple text file.
>>>> tail: unrecognized file system type 0x53464846 for ‘kn.txt’. please report this to bug-coreutils <at> gnu.org. reverting to polling
>>>
>>> Interesting. What do we call this win_bashfs or something?
>>
>> There's not much technical information available, but shouldn't
>> that "Windows Subsystem for Linux" (WSL) just pass on some NTFS?
>> It's not clear to me whether the entry point is a modified bash,
>> library or whatever, so bash may not always be involved here.
>> Therefore, I'd say "wsl_fs" or "wsl_ntfs" may be a valid name.
>>
>>> Since there is just a single kernel involved, I'm guessing
>>> that we don't need to tag this as a "remote" file system,
>>> and that inotify calls will fail/succeed as appropriate.
>>> That could be confirmed using the inotifywait command as detailed at:
>>> http://bugs.gnu.org/23143#11
>>
>> WSL is in early beta, so I wouldn't expect inotify to work.
>
> Should be no harm trying though I expect.
> I went with "wslfs" as underscores are the exception in names.
>
> I'll push the attached later.

bike-shedding, I notice the ASCII of the ID backwards is FHFS.
Perhaps that means File Handle FS?
Searching shows nothing. I'll stay with WSLFS for now

Previous Next

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