I’ve been recently trying unsuccessfully to find an explanation of how hard
links and quotas coexist in Unix in a non-brain-damaged manner, which (given
the new Win2K facilities in these areas) raises the same question there. In
particular, my impression is that in Unix when a file’s owner rm’s the file
(Unix has no explicit Delete file function), if other links still exist then
the owner remains charged for the file’s space use and can’t really do
anything about it (save try to get someone with appropriate privilege to
track down the links and remove them). And there appear to be other
non-intuitive quirks in the implementation as well.
Could anyone point me to a detailed explanation of how hard links function
in such areas in Win2K, and how their existence affects quota management?
Thanks,
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
A pointer to information that might help you. The book “Understanding Linux
kernel, by Daniel P. Bovet and Marco Cesti” quite deeply covers topics
regarding description of VFS and implementation of Ext2. wbr Primoz
-----Original Message-----
From: Bill Todd [mailto:xxxxx@foo.mv.com]
Sent: Thursday, March 01, 2001 9:32 PM
To: File Systems Developers
Subject: [ntfsd] hard links and quotas in Win2K
I’ve been recently trying unsuccessfully to find an explanation of how hard
links and quotas coexist in Unix in a non-brain-damaged manner, which (given
the new Win2K facilities in these areas) raises the same question there. In
particular, my impression is that in Unix when a file’s owner rm’s the file
(Unix has no explicit Delete file function), if other links still exist then
the owner remains charged for the file’s space use and can’t really do
anything about it (save try to get someone with appropriate privilege to
track down the links and remove them). And there appear to be other
non-intuitive quirks in the implementation as well.
Could anyone point me to a detailed explanation of how hard links function
in such areas in Win2K, and how their existence affects quota management?
Thanks,
You are currently subscribed to ntfsd as: xxxxx@hermes.si
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
Thanks, but my question relates to exactly how Win2K implements these
features (and in particular how it handles the kind of dubious interaction
between them that I described) - I think I already understand Unix’s
behavior fairly well.
----- Original Message -----
From: Primoz Beltram
To: File Systems Developers
Sent: Friday, March 02, 2001 4:01 AM
Subject: [ntfsd] RE: hard links and quotas in Win2K
> A pointer to information that might help you. The book “Understanding
Linux
> kernel, by Daniel P. Bovet and Marco Cesti” quite deeply covers topics
> regarding description of VFS and implementation of Ext2. wbr Primoz
>
>
> -----Original Message-----
> From: Bill Todd [mailto:xxxxx@foo.mv.com]
> Sent: Thursday, March 01, 2001 9:32 PM
> To: File Systems Developers
> Subject: [ntfsd] hard links and quotas in Win2K
>
> I’ve been recently trying unsuccessfully to find an explanation of how
hard
> links and quotas coexist in Unix in a non-brain-damaged manner, which
(given
> the new Win2K facilities in these areas) raises the same question there.
In
> particular, my impression is that in Unix when a file’s owner rm’s the
file
> (Unix has no explicit Delete file function), if other links still exist
then
> the owner remains charged for the file’s space use and can’t really do
> anything about it (save try to get someone with appropriate privilege to
> track down the links and remove them). And there appear to be other
> non-intuitive quirks in the implementation as well.
>
> Could anyone point me to a detailed explanation of how hard links function
> in such areas in Win2K, and how their existence affects quota management?
>
> Thanks,
>
> - bill
>
>
> —
> You are currently subscribed to ntfsd as: xxxxx@hermes.si
> To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com
>
> —
> You are currently subscribed to ntfsd as: xxxxx@foo.mv.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
When you make hard links in UNIX they all refer to the same inode
number and hence the same owner. The uid, gid is stored in the inode
structure and I doubt whether you can have different owners. When you
removed a link it only removes only the directory entry for files with
more than 1 links and no quota is subtracted.
–naja
— Bill Todd wrote:
> Thanks, but my question relates to exactly how Win2K implements these
> features (and in particular how it handles the kind of dubious
> interaction
> between them that I described) - I think I already understand Unix’s
> behavior fairly well.
>
> - bil
>
> ----- Original Message -----
> From: Primoz Beltram
> To: File Systems Developers
> Sent: Friday, March 02, 2001 4:01 AM
> Subject: [ntfsd] RE: hard links and quotas in Win2K
>
>
> > A pointer to information that might help you. The book
> “Understanding
> Linux
> > kernel, by Daniel P. Bovet and Marco Cesti” quite deeply covers
> topics
> > regarding description of VFS and implementation of Ext2. wbr Primoz
> >
> >
> > -----Original Message-----
> > From: Bill Todd [mailto:xxxxx@foo.mv.com]
> > Sent: Thursday, March 01, 2001 9:32 PM
> > To: File Systems Developers
> > Subject: [ntfsd] hard links and quotas in Win2K
> >
> > I’ve been recently trying unsuccessfully to find an explanation of
> how
> hard
> > links and quotas coexist in Unix in a non-brain-damaged manner,
> which
> (given
> > the new Win2K facilities in these areas) raises the same question
> there.
> In
> > particular, my impression is that in Unix when a file’s owner rm’s
> the
> file
> > (Unix has no explicit Delete file function), if other links still
> exist
> then
> > the owner remains charged for the file’s space use and can’t really
> do
> > anything about it (save try to get someone with appropriate
> privilege to
> > track down the links and remove them). And there appear to be
> other
> > non-intuitive quirks in the implementation as well.
> >
> > Could anyone point me to a detailed explanation of how hard links
> function
> > in such areas in Win2K, and how their existence affects quota
> management?
> >
> > Thanks,
> >
> > - bill
> >
> >
> > —
> > You are currently subscribed to ntfsd as: xxxxx@hermes.si
> > To unsubscribe send a blank email to
> leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com
> >
> > —
> > You are currently subscribed to ntfsd as: xxxxx@foo.mv.com
> > To unsubscribe send a blank email to
> leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com
> >
>
>
> —
> You are currently subscribed to ntfsd as: xxxxx@yahoo.com
> To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com
__________________________________________________
Do You Yahoo!?
Get email at your own domain with Yahoo! Mail.
http://personal.mail.yahoo.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
Once again, thanks, but my question is about Win2K, not Unix.
----- Original Message -----
From: naja
To: File Systems Developers
Sent: Monday, March 05, 2001 1:40 PM
Subject: [ntfsd] RE: hard links and quotas in Win2K
> When you make hard links in UNIX they all refer to the same inode
> number and hence the same owner. The uid, gid is stored in the inode
> structure and I doubt whether you can have different owners. When you
> removed a link it only removes only the directory entry for files with
> more than 1 links and no quota is subtracted.
>
> --naja
>
> — Bill Todd wrote:
> > Thanks, but my question relates to exactly how Win2K implements these
> > features (and in particular how it handles the kind of dubious
> > interaction
> > between them that I described) - I think I already understand Unix’s
> > behavior fairly well.
> >
> > - bil
> >
> > ----- Original Message -----
> > From: Primoz Beltram
> > To: File Systems Developers
> > Sent: Friday, March 02, 2001 4:01 AM
> > Subject: [ntfsd] RE: hard links and quotas in Win2K
> >
> >
> > > A pointer to information that might help you. The book
> > “Understanding
> > Linux
> > > kernel, by Daniel P. Bovet and Marco Cesti” quite deeply covers
> > topics
> > > regarding description of VFS and implementation of Ext2. wbr Primoz
> > >
> > >
> > > -----Original Message-----
> > > From: Bill Todd [mailto:xxxxx@foo.mv.com]
> > > Sent: Thursday, March 01, 2001 9:32 PM
> > > To: File Systems Developers
> > > Subject: [ntfsd] hard links and quotas in Win2K
> > >
> > > I’ve been recently trying unsuccessfully to find an explanation of
> > how
> > hard
> > > links and quotas coexist in Unix in a non-brain-damaged manner,
> > which
> > (given
> > > the new Win2K facilities in these areas) raises the same question
> > there.
> > In
> > > particular, my impression is that in Unix when a file’s owner rm’s
> > the
> > file
> > > (Unix has no explicit Delete file function), if other links still
> > exist
> > then
> > > the owner remains charged for the file’s space use and can’t really
> > do
> > > anything about it (save try to get someone with appropriate
> > privilege to
> > > track down the links and remove them). And there appear to be
> > other
> > > non-intuitive quirks in the implementation as well.
> > >
> > > Could anyone point me to a detailed explanation of how hard links
> > function
> > > in such areas in Win2K, and how their existence affects quota
> > management?
> > >
> > > Thanks,
> > >
> > > - bill
> > >
> > >
> > > —
> > > You are currently subscribed to ntfsd as: xxxxx@hermes.si
> > > To unsubscribe send a blank email to
> > leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com
> > >
> > > —
> > > You are currently subscribed to ntfsd as: xxxxx@foo.mv.com
> > > To unsubscribe send a blank email to
> > leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com
> > >
> >
> >
> > —
> > You are currently subscribed to ntfsd as: xxxxx@yahoo.com
> > To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com
>
>
> __________________________________________________
> Do You Yahoo!?
> Get email at your own domain with Yahoo! Mail.
> http://personal.mail.yahoo.com/
>
> —
> You are currently subscribed to ntfsd as: xxxxx@foo.mv.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