lkml.org 
[lkml]   [1999]   [Jan]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [RFC] What should we do with FAT inode numbers?
Date
From

> > How about using the number of the first cluster in the file as the inode
> > number? As far as I understand, on FATish filesystems that is the way you
> > get at the real file data, so it can't change under you, whatever else is
> > going on. Or am I missing something here?
> >
>
> Slight problem: it doesn't work for zero-length files (no clusters
> allocated.) Otherwise it would work quite well.

How about always allocate one cluster for FAT files, even if they are
zero length? A waste, but not a big one.
If msdos or some such created a zero-length FAT-file - allocate the
cluster when the attempt is made to get the inode number.

This won't work with a read-only mounted filesystem shared with msdos
though. Linus idea with a counter may be useful in that case, just
restrict the range so where it won't overlap with real inode numbers.

Helge Hafting








-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:49    [W:0.037 / U:1.000 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site