Mods to FileName during Create

NTFSD
1

My IFS is for a Unix-like file system, so case insensitive and short name
lookups are more expensive than case sensitive long names. Does anyone see
a benefit to “fixing up” the FO’s FileName during create to match the actual
file name? The point would be to make future lookup operations that are
somehow derived from the FO’s FileName more efficient.

Is changing FileName even allowed?

Can I allocate a larger buffer for FileName and substitute it for the one
holding the original name? If yes, are there any special rules for
alloc/dealloc? If no, how is a reparse situation handle where the new path
is longer than the original?

Thanks in advance,
Demyn

You are currently subscribed to ntfsd as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com

2

JFFS?

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Demyn Plantenberg
Sent: Thursday, December 06, 2001 2:01 PM
To: File Systems Developers
Subject: [ntfsd] Mods to FileName during Create

My IFS is for a Unix-like file system, so case insensitive and short
name lookups are more expensive than case sensitive long names. Does
anyone see a benefit to “fixing up” the FO’s FileName during create to
match the actual file name? The point would be to make future lookup
operations that are somehow derived from the FO’s FileName more
efficient.

Is changing FileName even allowed?

Can I allocate a larger buffer for FileName and substitute it for the
one holding the original name? If yes, are there any special rules for
alloc/dealloc? If no, how is a reparse situation handle where the new
path is longer than the original?

Thanks in advance,
Demyn

You are currently subscribed to ntfsd as: xxxxx@storagecraft.com To
unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com

You are currently subscribed to ntfsd as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com

3

STFS – Storage Tank File System – a distributed/heterogeneous/SAN-base
file system. There’s a blurb on it here:
http://www.research.ibm.com/compsci/brochure2001/Storage.pdf

“Jamey Kirby” wrote in message news:xxxxx@ntfsd…
>
> JFFS?
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of Demyn Plantenberg
> Sent: Thursday, December 06, 2001 2:01 PM
> To: File Systems Developers
> Subject: [ntfsd] Mods to FileName during Create
>
>
> My IFS is for a Unix-like file system, so case insensitive and short
> name lookups are more expensive than case sensitive long names. Does
> anyone see a benefit to “fixing up” the FO’s FileName during create to
> match the actual file name? The point would be to make future lookup
> operations that are somehow derived from the FO’s FileName more
> efficient.
>
> Is changing FileName even allowed?
>
> Can I allocate a larger buffer for FileName and substitute it for the
> one holding the original name? If yes, are there any special rules for
> alloc/dealloc? If no, how is a reparse situation handle where the new
> path is longer than the original?
>
>
> Thanks in advance,
> Demyn
>
>
>
>
> —
> You are currently subscribed to ntfsd as: xxxxx@storagecraft.com To
> unsubscribe send a blank email to
leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com
>
>
> —
> You are currently subscribed to ntfsd as: $subst(‘Recip.EmailAddr’)
> To unsubscribe send a blank email to
leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com
>
>

—
You are currently subscribed to ntfsd as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com