Supporting for Windows about xattr HOT 11 CLOSED

@advancedwebdeveloper

@billziss-gh , could you tell whether your support of file systems (I see that you are dealing with few Golang packages, which has something to do with file systems) allow to improve QA part?

I am not sure I understand what you mean by "improve QA part".

To answer the original question: Windows does have Extended Attribute (EA) support. NTFS and I believe some versions of FAT support them. There is however a caveat: there is no Win32 API to access them and the NT API that exists is not documented.

The NT API consists of the functions NtQueryEaFile and NtSetEaFile and you can find information about them by searching online. I have example implementations of xattr functions using the NT API in the following places:

• In my port of fsx to Windows, which I use to test file systems.
• In a simple POSIX layer that is included with one of the WinFsp file systems: winposix.c. Please note that this EA code is not regularly tested.

I also note that Cygwin has a Linux-like implementation of xattr that uses the same NT API. You may want to have a look there as well.

One final note: you will find out that NTFS likes to uppercase extended attribute names (so that myxattr will become MYXATTR upon retrieval). Some POSIX layers deal with this by forcing all extended attribute names to be lowercase.

from xattr.

CC @asw101 @arschles @devigned

from xattr.

Might want to update this with a bit more information...

Seems NTFS has two ways to set attributes. Extended attributes can be added to the MFT (master file table) however they have limited size. This approach is also supported by FAT I believe. Alternative data streams is only supported by NTFS but allows unlimited data to be stored alongside the main file.

http://ntfs.com/ntfs_basics.htm

I doubt please would run into the size limitation of extended attributes, we only need to store 64 byte.

from xattr.

@AaLl86 , please explain about NTFS's capabilities/functionality
@craigbarkhouse , please share your vision
CC @brymat-msft

from xattr.

@billziss-gh , could you tell whether your support of file systems (I see that you are dealing with few Golang packages, which has something to do with file systems) allow to improve QA part?

from xattr.

@advancedwebdeveloper

@billziss-gh , could you tell whether your support of file systems (I see that you are dealing with few Golang packages, which has something to do with file systems) allow to improve QA part?

I am not sure I understand what you mean by "improve QA part".

To answer the original question: Windows does have Extended Attribute (EA) support. NTFS and I believe some versions of FAT support them. There is however a caveat: there is no Win32 API to access them and the NT API that exists is not documented.

The NT API consists of the functions NtQueryEaFile and NtSetEaFile and you can find information about them by searching online. I have example implementations of xattr functions using the NT API in the following places:

• In my port of fsx to WIndows, which I use to test file systems.
• In a simple POSIX layer that is included with one of the WinFsp file systems: winposix.c. Please note that this EA code is not regularly tested.

I also note that Cygwin has a Linux-like implementation of xattr that uses the same NT API. You may want to have a look there as well.

One final note: you will find out that NTFS likes to uppercase extended attribute names (so that myxattr will become MYXATTR upon retrieval). Some POSIX layers deal with this by forcing all extended attribute names to be lowercase.

I think uppercase can be resolved by things like base64 or hex encode

from xattr.

from xattr.

So, any progress here?

from xattr.