Messages in this thread | | | From | (H. Peter Anvin) | Subject | Re: [RFC] What should we do with FAT inode numbers? | Date | 16 Jan 1999 21:54:13 GMT |
| |
Followup to: <199901161629.NAA06169@sleipnir.valparaiso.cl> By author: Horst von Brand <vonbrand@sleipnir.valparaiso.cl> In newsgroup: linux.dev.kernel > > Alexander Viro <viro@math.psu.edu> said: > > [...] > > > FAT-derived filesystems use directory entry location as inode > > number. Fine, except that we have to take care of unlinked-but-opened > > inodes (avoid reusing the same number). Thus we may have to declare a > > directory busy even if all files are unlinked (otherwise we might reuse > > the same block and thus inode numbers later) [not done; race in msdos and > > umsdos]. Thus we have to do all sorts of ugly stuff in link creation. > > 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.
-hpa -- PGP: 2047/2A960705 BA 03 D3 2C 14 A8 A8 BD 1E DF FE 69 EE 35 BD 74 See http://www.zytor.com/~hpa/ for web page and full PGP public key I am Bahá'í -- ask me about it or see http://www.bahai.org/ "To love another person is to see the face of God." -- Les Misérables
- 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/
| |