Copying files... care about EA/streams?

NTFSD
1

Hi!

I worry about a copy mechanism I’ve written… though it works fine for
visible data. It’s just a open/read/write/close, copying until an EOF is
returned. What can/should I do not to lose other streams and EAs of the
source file. Should I copy all the allocation size of the file and
afterwards adjust the EOF, or should I open and copy one stream after
another - if so, how to find out what the streams are.

Regards, T.

2

You can find out about and read/write streams using the Backup api - see
BackupRead/BackupWrite. You can also find out about the alternate data
streams using native api NtQueryInformationFile, and you can read/write
the alternate data streams just using like open/read/write/close. Watch
out for reparse points! What about the security descriptor?

3

The security descriptor can be read using GetFileSecurity and written using SetFileSecurity WIN32 APIs. The descriptor can be handled in self-relative format which allows you to store it, transfer it, etc. as a binary blob.
/TomH

-----Original Message-----
From: Lyndon J. Clarke [mailto:xxxxx@gcplc.com]
Sent: Monday, October 28, 2002 10:45 AM
To: File Systems Developers
Subject: [ntfsd] Re: Copying files… care about EA/streams?

You can find out about and read/write streams using the Backup api - see
BackupRead/BackupWrite. You can also find out about the alternate data
streams using native api NtQueryInformationFile, and you can read/write
the alternate data streams just using like open/read/write/close. Watch
out for reparse points! What about the security descriptor?

You are currently subscribed to ntfsd as: xxxxx@inflectionsystems.com
To unsubscribe send a blank email to %%email.unsub%%