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

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 23273 in the body.
You can then email your comments to 23273 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Dennis J <upumop <at> msn.com>
To: "bug-coreutils <at> gnu.org" <bug-coreutils <at> gnu.org>
Subject: Error using windows 10 bash error 0x53464846 doing a tail -f
Date: Mon, 11 Apr 2016 17:37:59 -0500

[Message part 1 (text/plain, inline)]

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

 		 	   		  

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

Message #8 received at 23273 <at> debbugs.gnu.org (full text, mbox):

From: Pádraig Brady <P <at> draigBrady.com>
To: Dennis J <upumop <at> msn.com>, 23273 <at> debbugs.gnu.org
Subject: Re: bug#23273: Error using windows 10 bash error 0x53464846 doing a
 tail -f
Date: Tue, 12 Apr 2016 00:54:38 +0100

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?

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

thanks
Pádraig

Message #11 received at 23273 <at> debbugs.gnu.org (full text, mbox):

From: Bernhard Voelker <mail <at> bernhard-voelker.de>
To: Pádraig Brady <P <at> draigBrady.com>,
 Dennis J <upumop <at> msn.com>, 23273 <at> debbugs.gnu.org
Subject: Re: bug#23273: Error using windows 10 bash error 0x53464846 doing a
 tail -f
Date: Tue, 12 Apr 2016 10:11:05 +0200

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.

Have a nice day,
Berny

Message #16 received at 23273-done <at> debbugs.gnu.org (full text, mbox):

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: Re: bug#23273: Error using windows 10 bash error 0x53464846 doing a
 tail -f
Date: Thu, 21 Apr 2016 21:57:40 +0100

[Message part 1 (text/plain, inline)]

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.

cheers,
Pádraig

[coreutils-wslfs.patch (text/x-patch, attachment)]

Message #19 received at 23273-done <at> debbugs.gnu.org (full text, mbox):

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: Re: 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

Message #22 received at 23273-done <at> debbugs.gnu.org (full text, mbox):

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

On 04/21/2016 11:15 PM, Pádraig Brady wrote:
> 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

+1

Thanks & have a nice day,
Berny

Message #25 received at 23273 <at> debbugs.gnu.org (full text, mbox):

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

On 22/04/16 18:47, Bernhard Voelker wrote:
> On 04/21/2016 11:15 PM, Pádraig Brady wrote:
>> 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
>
> +1

Heh just after I push this I see reference to VolFS and DriveFS :)

https://blogs.msdn.microsoft.com/wsl/2016/04/22/windows-subsystem-for-linux-overview/

Will update accordingly.

cheers,
Pádraig

Message #28 received at 23273 <at> debbugs.gnu.org (full text, mbox):

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

On 04/23/2016 12:19 PM, Pádraig Brady wrote:
> Heh just after I push this I see reference to VolFS and DriveFS :)
> 
> https://blogs.msdn.microsoft.com/wsl/2016/04/22/windows-subsystem-for-linux-overview/

oh, thanks.
Hmm, I couldn't find any other site than this for more
information - did you manage to find the magic for the other
file system on WSL?  Otherwise, we'll have to wait for someone
to create a bug report (unless it's using an already known
magic number).

Thanks & have a nice day,
Berny

Message #31 received at 23273 <at> debbugs.gnu.org (full text, mbox):

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

On 26/04/16 07:22, Bernhard Voelker wrote:
> On 04/23/2016 12:19 PM, Pádraig Brady wrote:
>> Heh just after I push this I see reference to VolFS and DriveFS :)
>>
>> https://blogs.msdn.microsoft.com/wsl/2016/04/22/windows-subsystem-for-linux-overview/
>
> oh, thanks.
> Hmm, I couldn't find any other site than this for more
> information - did you manage to find the magic for the other
> file system on WSL?  Otherwise, we'll have to wait for someone
> to create a bug report (unless it's using an already known
> magic number).

I'll try and find a windows system/vm to try this out on.

cheers,
Pádraig

Previous Next

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