On a similar topic, what do directory sizes mean? I can't seem to see any direct connection between the size of a directory in an ls -l and it's contents, or the size of it's contents.
On Wed, Jul 01, 1998 at 07:04:26PM -0400, Bob Hilliard wrote: > I'd like to piggy-back on this discussion - Oliver is the first > person I have heard talk knowledgeably lost+found. > > I have never found any files in lost+found, but ls-l and du > always show it as 12kb, even in a brand new file system. What is > occupying those 12k? > > Bob > -- > > "Oliver Elphick" <olly@lfix.co.uk> writes: > > > > > "Jieyao" wrote: > > Part of the disk damage can be that file pointers in directories can get > > destroyed, leaving the inode used but not pointed to by anything. If the > > orphaned file is empty it will be removed; if it is not empty, it will be > > reconnected into the directory lost+found, which should exist at the top > > level of the file system - there is one of these directories for each > > file system. Since the orphaned file's name will have been lost, it is > > simply given its inode number as a name. To recover it, identify it by its > > contents and mv it to its proper location. > > > -- > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null > -- ______________________________________________________________ | ian eure, network admin, freelance security consultant, and | | manically depressed paranoid schizophrenic, at your service. | ; <[EMAIL PROTECTED]> - http://minion.org ; : raw speed = 105.6 wpm with 4.5% errors : . . . . . . . . . . . . . . . . . . . . . . -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
