Date: Thu, 23 Jul 2015 09:41:39 +0300 From: Konstantin Belousov <kostikbel@gmail.com> To: Simon Brugger <simon.brugger@gmail.com> Cc: freebsd-fs@freebsd.org Subject: Re: Need help to understand inodes in FAT implementation Message-ID: <20150723064139.GL2072@kib.kiev.ua> In-Reply-To: <CAOSq-ePjSeWq3HVaRxoGJ8ue_UrxE=vn093ZPS3z4=HhPqsrAg@mail.gmail.com> References: <CAOSq-ePjSeWq3HVaRxoGJ8ue_UrxE=vn093ZPS3z4=HhPqsrAg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jul 22, 2015 at 10:46:01PM -0700, Simon Brugger wrote: > The FAT filesystem is a design from Microsoft and the whole Windows > universe. As you probably know, FAT does not support Inodes like ext3 or > other UNIX/LINUX filesystem. > > The FreeBSD kernel provide a FAT filesystem driver but I've problems to > understand the code and need help for answering the following questions: > > - Inodes must be generated on the fly by file access. When exactly does > this happened? Inodes are not generated. The inode numbers are. Look at the sys/fs/msdosfs/msdosfs_vnops.c:msdosfs_getattr() to see how. The struct vattr va_fileid field is returned from VOP_GETATTR() to userspace as the struct stat st_ino. > - How does FreeBSD generate Inodes? > - How does the kernel FAT driver manage the file descriptors? Kernel FAT driver does not manage file descriptors.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150723064139.GL2072>