On Thu, Mar 02, 2000 at 06:26:57PM -0600, Oleg Krivosheev wrote:
> On Thu, 2 Mar 2000 kmself@ix.netcom.com wrote:
>
> > > > Files and directories are identified under most Linux-like fileystems
> > > > (e2fs, minix fs, UFS, etc., but *not* msdos, vfat), by inodes. An inode
> > > > is essentially a database entry in a table giving storage location,
> > > > name, and values of several attributes (read/write/execute/suid), etc.
> > > ^^^^^^
> > >
> > > name? Files are nameless in UNIX. Read about hard links for example
> > > And from inode you should get storage, attirbutes, times (creation,
> > > access) and reference counter.
> >
> > lost+found inode is 11 for ext2fs. Do:
> >
> > ls -id /lost+found
>
> hmm...
>
> i thought there is no special inode for /lost+found. Any reason
> the inode should be special?
Presumably so that it can be located when the directory entries are
hosed.
[...]
> ah.. see? /lost+found is first free inode, nothing special. So you could
> just recreate it anytime you want
mklost+found pre-allocates disk blocks to the lost+found
directory so that when e2fsck(8) is being run to recover a
filesystem, it does not need to allocate blocks in the
filesystem to store a large number of unlinked files.
This ensures that e2fsck will not have to allocate data
blocks in the filesystem during recovery.
> i believe in ext3 (==ext+jounaling) journal inode would be special but too
> lazy to check
--
Karsten M. Self (kmself@ix.netcom.com)
What part of "Gestalt" don't you understand?
Scope out Scoop: http://scoop.kuro5hin.org/
Nothin' rusty about Kuro5hin: http://www.kuro5hin.org/
